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
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:
"Mind-boggling." That's one way to describe the pace of change in today's business environment. To succeed, businesses have to be willing to change, innovate and take educated risks. And the old adage "opportunity rarely knocks twice" is still around, simply because it happens to be true.
