Requirements Practices Every Project Manager Must Know
Frederick Brooks wrote in his famous “No Silver Bullet” essay (1987):
“The hardest single part of building a software system is deciding precisely what to build. No other part of the conceptual work is as difficult as establishing the detailed technical requirements, including all the interfaces to people, to machines, and to other software systems. No other part of the work so cripples the resulting system if done wrong. No other part is more difficult to rectify later.”
Requirements management is all about deciding precisely what to build, and how to build it. I see few shops and fewer PMs who have effectively embraced the discipline of requirements engineering and management. However, the requirements-aware PM can deliver high-impact results to a project’s triple constraints by applying just a handful of best practices.
Poor requirements definition and control leads to rework and missed work. The costs in dollars and schedule increase dramatically the later in the project they are discovered. Problems that cause a 5 percent cost bump when found in design, cost 20 percent discovered during testing and 100 percent (and more) after implementation. Researchers have documented that 30 to 50 percent of total development cost can be attributed to rework…and requirements deficiencies account for more than 70 percent of
Please log in or sign up below to read the rest of the article.