There are a few good resources out there that cover project management from A to Z. Rapid Development by Steve McConnell always comes to mind when someone asks me to recommend one book on software project management.
Unfortunately (or should I say "realistically"), not everyone has time to read a 647-page book before embarking on a new project. Some managers barely have time to learn the ABCs, let alone D-Z. Whether you're new to project management or simply want a refresher, read on to learn seven of the most common mistakes that people make when they try to develop software rapidly.
Weak Team
Various resources claim that there is as much as a 10-to-1 efficiency ratio between a great software developer and a mediocre one. If you pick your team from the bottom of the barrel, then you can be guaranteed that your project will fail. Second-rate developers contribute to project failures in many ways. They deliver features late, implement functionality that doesn't meet requirements or build so many defects into their code that the product lacks the level of quality deemed acceptable by your client. Select your team members carefully. At the end of the day, even the best project manager can't succeed with a weak team.
Overly Optimistic Schedule
As discussed in previous articles, project schedules must be aggressive, yet realistic. Publishing an overly optimistic