Projectmanagement.comPlan

5Plan

Requirements Management PlanIdentifying, managing, and verifying requirements for [Project Name]OverviewThis plan will guide us through the following aspects of requirements management: Collection- gathering the basic needs of stakeholders Categorization categorizing those needs Prioritization prioritizing those needs and identifying must haves Tracing tracking how those needs are addressed throughout the life of the project Change Management the process by which we will change our requirements as needs change Verification how we will verify that requirements have been metThis document is to be used a tool for communications, giving all stakeholders a view on how this process is managed for [Project Name].

Requirements Collection

During this phase, the emphasis is on capturing as many perceived requirements as possible from all valid stakeholders. Not all of the needs we identify here will end up as actual requirements, but they will be identified and understood.[Collection Method 1]

[How it will be used, with which groups, and why]You may wish to pull text for this section from gantthead on:

Brainstorming Voice of the Customer Customer Needs AnalysisAlso consider using surveys and interviews of different types (people at different levels, in different roles, people deeply involved in the business process you are addressing, sponsors, executives, etc.).[Collection Method 2]

[How it will be used, with which groups, and why][Collection Method 3]

[How it will be used, with which groups, and why]As we identify each requirement, we will document the: Requirement name

Requirement description The stakeholder to whom it is important

Some measure of criticality (how important it is based on a quantified view of having it versus NOT having it)

Acceptance Criteria (a quantified way of understanding the specifics of the requirement. In other words, how will we know its been fulfilled?)

Requirements Categorization

During this phase, we will logically group requirements. Requirements will be grouped into the following categories:[Requirement Category 1]

[Why this category is important and makes sense]Categories often include:

Functional Requirements Technical Requirements

Training Requirements

Quality Requirements

Performance Requirements

Support Requirements

Maintenance Requirements

[Requirement Category 2]

[Why this category is important and makes sense][Requirement Category 3]

[Why this category is important and makes sense]Requirements Prioritization

Our approach to prioritizing requirements will be to [describe approach]Often this is a matter of working with the project sponsors to make some decisions.The following gantthead techniques can be helpful and some of the text from the site can be used in this document as well.

Decision-making techniquesOne important aspect of prioritization is the relationship between requirements. Sometimes you have to do one thing if you do another. Sometimes the best way to do this is to conduct a Customer Satisfier Analysis, and look at things more broadly than you would if you are just eyeing individual requirements. Requirements Traceability

Certain requirement attributes need to be tracked across the project life cycle so that you can relate them back to what you are actually doing on the project. We will track those attributes and maintain a consistent understanding of how they are being addressed during the course of the project.

Beginning on [date] we will track all requirements, their source, the project objective they support, the part of the WBS where it is addressed, when it is verified and validated. We will use [requirements management system X or requirements traceability matrix Y] to manage data on each requirement.

[Team Member] will be responsible for the tracking of requirements. He/she will report any impacts to project requirements based on current performance to [Project Manager] within 24 hours of a status change.[Further describe the tools and methods used to trace requirements here]Requirements Traceability Matrix

RequirementPriorityCategorySourceRelated WBS Code

Change Management Our projects requirements will change over time and those changes must be managed in order to ensure a successful outcome.[Describe the process for making changes and supporting materials.]Here are examples of change request policies and systems that could be a part of this description.

Change Management Policy and Process Change Management StandardsRequirements Verification [Describe methods and metrics used to verify requirements, how their achievement will be measured, tested, etc.]Requirements Verification Matrix

RequirementWhat will be measured?(metric)When it will be measured?(date)Who will measure it?Acheived?

projectmanagement.com

11911 Freedom Drive #900Reston, VA 20091