Unauthorized use and/or duplication of this material without express and written permission from this blog’s author and/or owner is strictly prohibited. Excerpts and links may be used, provided that full and clear credit is given to John D Carmack and Random Acts of IT Project Management with appropriate and specific direction to the original content.

That is a sobering statistic, but it only tells part of the story. When you remember that a $1 mistake early on in the project easily balloons into a $40 fix later on, you begin to see why it is so important to do requirements correctly. However, even good requirements have flaws. Therefore, it is vital to pull together your team and do a thorough walk-thru of the requirements, project plan and statement of work. It is important that these documents undergo a peer review by a fellow project manager as well as the technical project team.

Moustafaev makes several good points about pitfalls and things to look for in walk-thrus and reveiws. A worthwhile read!