This PMBOK template sets out how project requirements will be managed. Use this template to capture all of the key information you need. It is related to the Scope Management Plan and can be combined with it on small projects. stakeholdermap.com
The document is created with inputs from the Project Charter, development approach and the Quality Management Plan. It forms part of the Project Management Plan and aligns with change management, scope management, the release and iteration plan, development approach and the requirements backlog.
The completed plan drives the Requirements log and Traceability Matrix, and is and input to the risk register and Quality Management Plan.
Use this FREE template to document how requirements will be managed on your project . This template includes all of the areas you need to cover, with includes useful hints and tips to help you complete each section.
This is a FREE Requirements Management Plan Template in Word and PDF. The template is fully editable with Microsoft Word and can be converted or changed to suit your project requirements.
Check out the contents below or Grab the template now!
Set out how the requirements will be collected. This might be via user workshops, interviews, brainstorming, or review of enhancement requests or product reviews.
Explain how the impact and usefulness of each requirement will be analyzed, so that a priority, and category can be determined.
A good test is to try to map out the connection between the requirement and the objective. For example, will this requirement lead to a reduction in handling time?
This path looks very tenuous, which suggests that the requirement should be dropped or be categorised as 'nice to have' or 'cosmetic'.
In comparison a requirement for a knowledge base that provides service desk agents with template responses to common questions would have a direct contribution to reducing average call handling time.
Describe how the requirements will be documented including the format and fields that will be used. Often requirements are gathered using a simple Excel spreadsheet, or Word document although specialist software also exists. Some examples:
Example of an Agile method format
| As a/an | I want to. | So that. |
|---|---|---|
| Type | Business Function/Category | Requirement | Priority |
|---|---|---|---|
Describe the way that requirements will be prioritised. Some will be mandatory to meet with regulations, security, company policy or the forecast ROI. Others will be ‘nice to have’, but not essential to meet the business objectives.
For example, MoSCoW could be used. In this case requirements would be grouped as:
Must have – mandatory requirement
Should have – functionality or feature that should be available.
Could have – desirable or nice to have
Won’t or would have – not required but might be a future release.
You might also use a numerical scale – 1 to 10 or a simply high, medium, low.
Describe the metrics that will be used to measure requirements. For example, 99.9% availability, withstand x psi, near-real time etc.
Explain how progress will be tracked. For example, through requirement checkpoints or progress meetings.
Document what reporting is needed on the requirements, including report purpose, format, frequency and audience.
Explain the methods that will be used to validate the delivery of the requirements. For example, testing, audits, inspection, demonstration, proof of concept, beta version etc.
Describe how you will manage requirements changes. Including, new and changes to existing approved requirements. Set out the information that will be captured for each change, how the impact will the analyzed and how changes will be reviewed and approved.
