This presentation highlights the important components of the requirements management process, the key features that a requirements package needs to have, the need to collect metrics and use tools to manage requirements during the lifecycle of a project.

2. Introduction:
• Requirements Management process is treated as a documentation activity and is sometimes
seen as a supportive role to project execution.
• The requirements management process can be made structured and robust by ensuring that the
key components of the process are in place, the requirements package has the necessary
elements, standard tools are used and metrics are collected and acted upon.
• According appropriate importance to the requirements process will ensure higher likelihood of
project success.
• This paper highlights the important components of the requirements management process, the
key features that a requirements package needs to have, the need to collect metrics and use tools
to manage requirements during the lifecycle of a project.

3. Key Components of Requirements Management Process :
At the time of project kick off, organizations need to ensure that they have the following
components in place:

4. Key Components of Requirements Management Process :

5. Key Components of Requirements Management Process :

6. Key Components of Requirements Management Process :

7. Elements in a Requirements Package:
There are various elements that are a part of a Requirements Package. A robust Requirements
Package should contain the following details at the minimum:

8. Elements in a Requirements Package:

9. Elements in a Requirements Package:

10. Importance of using Standard Tools:
• Various requirements elicitation techniques include structured workshops and interviews; joint
application development sessions, storyboarding and surveys.
• The outcome of these workshops are typically captured as meeting minutes or notes and
published to key stakeholders and project participants. These notes serve as input for requirements
analysis.
• While the standard office productivity tools are good for capturing information pertaining to
project requirements, they are not meant to be collaborative tools. Word processing
software, spreadsheets and presentation tools facilitate information capture and sharing. These
cannot be used to track changes to requirements’ features and the approvals to these changes.
• This traceability is essential during the execution of a project and the standard office productivity
tools do not support this important function. It is on this dimension that tools like Requisite Pro
score positively. These tools allow requirements capture in a structured manner and facilitate
maintaining them dynamically, i.e., they permit tracking changes to the requirements and approvals
with traceability.

11. Importance of using Standard Tools:
• This is quite crucial during the life cycle of project execution. Other collaborative tools like
SharePoint can be used during engagement execution to facilitate central storage, publishing and
retrieval of documents.
• Requirements management tools should support important features like traceability, integration
with office productivity tools, support baseline creation and versioning besides being able to
accommodate all the features of the requirements management package detailed earlier

12. Collection of Metrics:
• There are several metrics that need to be collected during the requirements management
process.
• These metrics can be collected from requirement management tools, configuration management
systems and testing tools.
• Organizations should have the mechanism and discipline to capture, track and report metrics and
take corrective action where required.
• The various metrics that can be collected and analyzed during the requirements management
process are covered in detail in Maveric’s Point Of View titled “Vital Metrics for Requirements
Management”.

13. Conclusion:
This presentation has highlighted the critical components of a requirements package, the
importance of using standard tools and techniques and the elements that should be present in a
requirements package. Adopting these recommendations will help organizations improve their
maturity level of requirements management process and help avoid the pitfalls associated with
unstable / immature requirements management processes. According appropriate importance to
the requirements process will ensure higher likelihood of project success.