XYZ Website Redesign

Project Management

Team Hub

Two Way Write Up

Portfolio Website

Leave FEEDBACK Here

RMP

Explore

RMP

This requirements management plan is a component of the project management plan. It describes how the project requirements will be analyzed, documented and managed.

There are no rows in this table

⁠

Contents

⁠

Collect Requirements 2⁠

⁠

Requirements Tracking 3⁠

⁠

Structure of Requirements Traceability Matrix 3⁠

⁠

Reporting 3⁠

⁠

Requirements Approval 3⁠

⁠

Requirements Analysis 4⁠

⁠

Categories 4⁠

⁠

Prioritization 4⁠

⁠

Quantifying 4⁠

⁠

Requirements Validation 5⁠

⁠

Configuration Management 5⁠

⁠

Monitoring 5⁠

⁠

Integrated Change Control Procedures 5⁠

⁠

Plan Approval 6⁠

⁠

Attachments 6⁠

⁠

A. Documentation From Collect Requirements Process 6⁠

⁠

B. Requirements Register 6⁠

⁠

C. Requirements Traceability Matrix 6⁠

⁠

Requirements Management Plan

Collect Requirements

Sources

Development of initial project requirements will begin with an examination of the following sources:

Project Charter:

Project Charter Link⁠

⁠

Business Case:

Business Case Link⁠

Stakeholder Interviews: {data not provided}

Customer documented requirements: {see below}

Stakeholder Workshops: {data not provided}

Collect Project Requirements

The following tools and techniques will be used to further develop the project requirements.

(Below, leave the appropriate tools and techniques in place and provide detail regarding each tool that will be used. Delete from this list any tool that will not be used.)

Focus Groups: we can learn from current customers plus those who aren't customers

Questionnaires and Surveys: we can use the current site to collect data.

Benchmarking: we should compare ourselves with the industry best.

Documentation will be generated during the collect requirements process. All of the documents generated from this process are or will be included below as Attachment A.1, A.2, A.3 and so forth.

Requirements Tracking

All project requirements identified to date are logged on the requirements register, included below as Attachment B. Requirements listed there will be analyzed, categorized, prioritized, and quantified. Those that survive analysis and receive approval will be added to the requirements' traceability matrix included as Attachment C and traced through to project completion. The person or persons with authority to approve project requirements are listed above in the Management Approach section.

Structure of Requirements Traceability Matrix

A requirements' traceability matrix is a document that demonstrates the relationship between requirements and other artifacts. It's used to prove that requirements have been fulfilled, and identify changes in scope. And it typically documents requirements, tests, test results, and issues. The RTM will include the following:

ID Number

Date Received/Recorded

Source

Name and description

Work breakdown structure

Team member assignee

Team member who test requirement and date performed

Documented acceptance criteria

Who from the customer side is accepting requirement

Reporting

What

Project status providing cost performance, schedule performance, issues, and risks.

How

Copy of reports/dashboards will be emailed

Who

Seagram Kern, PM will be reporting to Tom Kane, PS

When

Weekly

Requirements Approval

Approved Requirements

Requirements shall be approved by Tom Kane, PS via requirements approval documents sent by Seagram Kern, PM.

Rejected Requirements

Tom Kane has the right to reject requirements and must indicate the reason for rejection on the requirements' approval document.

Requirements Analysis

Requirements analysis will be performed by the Seagram Kern, PM. Seagram will ensure that all requirements are clearly written and properly logged and categorized.

Prioritization

Requirements will be prioritized by High, Moderate, and Low. The PM will hold a focus group with the PS and project team members to determine the prioritization of requirements. Requirements of high priority will be completed first, while those of low priority will be completed last.

Quantifying

The Project Manager is responsible for quantifying requirements. The Project Sponsor and Project Manager work in a joint effort to define the acceptance criteria. The Project Sponsor must make the final approval on acceptance criteria.

Requirements Validation

The Project Manager will review the deliverables to ensure they meet acceptance criteria before presenting the deliverables to the Project Sponsor for final acceptance. Acceptance or rejection must be obtained in writing. In the event of rejection, the Project Manager must revisit the deliverable with the project team to make any adjustments necessary to ensure that it meets the acceptance criteria.

Configuration Management

Every identified project requirement is set forth on the requirements register. Only those approved requirements will be carried forward for project work. The approved requirements are listed in the requirements' traceability matrix.

Monitoring

The Project Manager is responsible for monitoring and tracking the project requirements. Any changes in progress will be updated on the Requirements Traceability Matrix and reported in the bi-weekly status reports sent to the Project Sponsor.

Integrated Change Control Procedures

Changes to the project requirements will follow the same change control procedures as those set forth in the change management plan. All requests for changes must be submitted in writing, on the approved change request form.

Plan Approval

By signing below, I, _______Tom Kane______________, in my capacity as Project Sponsor, approve of this requirements' management plan.

Name: Tom Kane

Title: Project Sponsor

____________Tom Kane_________________ _____01.28.21_____

Signature Date Approved

Attachments

Documentation From Collect Requirements Process

A.1 Data not provided

A.2 Data not provided

A.3 Data not provided

Requirements Register

⁠

Requirements Register⁠

⁠

Requirements Traceability Matrix

⁠

Traceability Matrix⁠

⁠

Product Backlog

⁠

Product Backlog⁠

⁠

Structure of Requirements Traceability Matrix

Reporting

Requirements Approval