1. Have your project group use the source code management tool?
Should be used. VSS, CVS, PVCS, ClearCase, CCC / Harvest, Firefly can. My choice is VSS.
2. Is your project group use the defect management system?
Should be used. ClearQuest is too complicated, my recommendation is bugzilla.
3. Is your test group still write test cases with Word?
Do not use Word write test cases. You should use a specialized system, you can be Test Manager, or you can develop a small website of ASP.NET. The main purpose is TRACK and BROWSE.
4. Does your project group have a portal?
There is a portal, used to place Contact Info, Baselined Schedule, News, and so on. Recommended SharePoint Portal Server 2003 to achieve, 15 minutes. Can't afford SPS 2003 to use WSS (Windows SharePoint Service).
5. Do you have the best tool you can buy?
It should be used to work with as much as possible. For example, you should write C # with vs.net instead of notepad. Most of the NOTEPAD write programs is just a kind of show. But also take into account funds, so say "you can buy the best."
6. Is your programmer working in a quiet environment?
Need a quiet environment. This is extremely important, and it is necessary to ensure that each person's space is greater than a certain area.
7. Does your employees have a phone call?
Need a phone call. Moreover, the phone is preferably with message function. Of course, such a set of message telephone system overhead is not small. However, at least one phone call must have, don't do anyone standing up and shout: "a phone call". "People" is strongly condemned this approach.
8. Everyone knows who you should find out?
should know. Any feature should at least have an Owner. Of course, Owner can continue dispatch to others.
9. You have encountered someone say "I thought ..."?
To eliminate "I thought". Never associan.
10. Are all people in your project group sitting together?
need. I oppose Virtual Team, also opposed DEV in the United States, Test in China. It is best to sit together, and it will be more beneficial.
11. Does your progress table reflect the latest developments?
Should be reflected. However, you should use the Baseline method to manage schedule: maintain a stable Schedule, and then maintain a latest change. The method of Baseline should also be used for other SPECs. Baseline is an important means in the management of the change management.
12. Is your workload to be estimated by everyone?
Everyone should be estimated. To estimate the workload from the bottom, not from top to bottom. Unless other reasons, such as the policy of the political task.
13. Do your developers work overtime from the beginning of the project?
do not do that. Don't make a fatigue war at the beginning. Overtime work from the beginning of the project, only the project progress is unreasonable. Of course, some of the day software outsourcing must work overtime every day, and that belongs to exploitation.
14. Is the buffer time in your project plan? Is it behind every small task?
Don't. Buffer Time is added to each of the small tasks, it is easy to be easily consumed. Buffer Time The whole section is added to a MILESTONE or CheckPoint.
15. It is worth more to spend more time, from 95% to 100% good
It is worth it. Especially when the project is buddy, it is necessary to persist. This will bring quality difference to the product.
