Search Results

For the specific project there's not much you can do until you find out what the client wants. However, there are some things you can do now so your team is ready to go. … Have the group work on a very simple project to test all of this out either in a required language or pick one familiar to the team. …

Can they afford to delay the entire project? Get them to commit to an increased testing/approval schedule. You may have to repeat the tests on completed areas of the project. …

If the project is really small then it's not even in company's VCS. This is the first problem. No such thing as being too small for source control. Get away from email. …

See if you can work on a piece of the project and then put together a better estimate if needed. …

I worked for a small software company during the time where they released new versions to handle Y2K. To me the biggest differences involve the control and consistency of the users and their environme …

Test documentation just like a usability test. Give the document to a user with no explanation and watch over their shoulder to see if they get any value out of it. Hopefully it meets your objective.

There are excuses for the incomplete project, but the client pays anyway or now they're able to delay it? Something doesn't add up or the client has a loose interpretation of what urgent means. … A huge discrepancy in project estimates means something is very wrong. Take the project into smaller parts and give estimates for those. …

Even if you truly think you can completely write out all of the specifications for a complex project, don't do it if it is going to take a long period of time. … They spent so much time writing specs, they didn't have time for the much bally-hooed pseudo-code phase of the project. OK, maybe taking to much time to write specs can be a good thing. …

Since your manager knows it will probably fail, you're better off than most. I would consider working with the manager and see if there are any parts/features of the app that can be excluded. Too of …

How hard is it to break up any project or application into some reasonable pieces to build and get some feedback before you build another piece? … Do clients really love the fact that the programmers are out of their hair for 6-12 months while they develop during some waterfall project? Would you hire someone to build a house this way? …

This makes it easier to cover back at the office, have enough time to complete the project and not burden everyone by being away for a week. … Of course the second team gets final say in the project, so that may be a benefit. They could just redo everything. Spend the last day with both teams together and debrief/fight it out. …