In this quick post, I’d like to define the term “Requirements Management Plan”.
Simply put, “Requirements Management Plan” refers to:
A document (or set of documents) that define how the requirements for a software project will be managed.
Requirement management plan outlines the guidelines for creating requirements documents, types and attributes of requirements to be included in such documents, as well as the processes for change control and requirements traceability.
Here’s some more info about requirements management plans.
Notes on Requirements Management Plan:
- A formal requirements management plan is usually created for large projects that follow traditional waterfall methodologies.
- Agile projects seldom create a formal requirement management plan.
- Hybrid projects (i.e. some combination of Agile and waterfall methodologies) may or may not create a formal requirement management plan.
- Even when a formal requirements management plan is not created, it is still a good idea to create and share the corresponding information across the project team. At the minimum, this information should include:
- How requirements will be documented
- Who is responsible for requirements
- How changes will be handled
Benefits of Requirements Management Plan:
Requirements management plans help the entire project team to be on the same page on requirements related matters. As a result, they can help ensure:
- Better communication and teamwork on requirements.
- This can increase the odds of project success – including meeting customer needs well, and achieving faster time-to-market.
- These benefits are especially true for large projects that involve multiple, globally distributed functional units.