PCG believes that requirements definition is the most crucial part of the project. Incorrect, inaccurate, or excessive definition of requirements often result in schedule delays, wasted resources, or customer dissatisfaction.
The requirements analysis should begin with business or organizational requirements and translate those into project requirements. If meeting stated requirements would be unreasonably costly, or take too long, the project requirements may have to be negotiated down, down-scoped or downsized, through discussions with customers or sponsors.
PCG uses several techniques such as Joint Requirements Planning (JRP) for eliciting and defining requirements. While the methods may differ between projects, the principles remain the same across all types and sizes of projects. The requirements analysis should cover the whole scope of the project. It must be comprehensive and thorough. It must consider the views and needs of all the project stakeholders.
A requirements analysis should document what is in the scope of the project and what is not. The analysis should provide the necessary clarity or detail thereby making the requirements definition ambiguous. The completed requirements analysis should be reviewed and approved by the customer or project sponsor before work continues. On large projects, the first formal design review is actually a requirements review.
For more information about PCG Technology Consulting's Requirements Definition services please contact us at email@example.com or 1-800-210-6113.