Requirements 101: Not A Waste of Time
It is not uncommon to hear deadline-stressed project managers and team members rationalize about why requirements management is not necessary. But short-changing business analysis activities is one of the leading causes of rework and delays.
This is the first in a four-part series on the crucial relationship between the disciplines of requirements management and project management.
For those of us who have been given imposed deadlines that often seem arbitrary and unreasonable, managing requirements is one of the last things we want to do on a project. We worry about getting the product built and tested as best as we can. And we feel fortunate to gather any requirements at all. However the lack of a well-managed requirements process can lead to common project issues, such as scope creep, cost overruns, and products that are not used. Yet many project professionals skim over this important part of the project and rush to design and build the end product.
It is not uncommon to hear project professionals and team members rationalize about why requirements management is not necessary. We commonly hear these types of statements:
“I don’t have time to manage their requirements. I’m feeling enough pressure to get the project done by the deadline, which has already been dictated. My team is needs to get going quickly
Please log in or sign up below to read the rest of the article.