Building Detailed Project Requirements Not Optional

One of the first steps in any project is to gather requirements from stakeholders, understand them and then verify them with the same stakeholders. Once verified, requirements can be given to developers and they can go on their merry way. But there are some who don’t see the value in documenting requirements.

Joe Kornik | November 03, 2013

BY Kristine Slaboszewski

Business Consulting One of the first steps in any project is to gather requirements from stakeholders, understand them and then verify them with the same stakeholders. Once verified, requirements can be given to developers and they can go on their merry way. But there are some who don't see the value in documenting requirements.

FOR THOSE WHO MAY NOT SEE THE VALUE IN DOCUMENTING REQUIREMENTS, I OFFER THE FOLLOWING REASONS FOR ENGAGING IN THIS CRITICAL STEP:

To continue reading, become an ALM digital reader

Benefits include:

  • Authoritative and broad coverage of the business of consulting
  • Industry-leading awards programs like Best Firms to Work For, Global Leades and Rising Stars
  • An informative newsletter that goes into the trends shaping the industry
  • Critical coverage of the employee benefits and financial advisory markets on our other ALM sites, BenefitsPRO and ThinkAdvisor