0% found this document useful (0 votes)
36 views5 pages

Project Requirement

The document outlines the project requirements for Project Orion, detailing the requirement ID, description, requester, category, priority, acceptance criteria, complexity, scope, testing, and release phase. It serves as a template for organizing and analyzing project requirements to ensure successful delivery. Additionally, it includes links to various project management resources and templates.

Uploaded by

Anantha Jiwaji
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as XLS, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
36 views5 pages

Project Requirement

The document outlines the project requirements for Project Orion, detailing the requirement ID, description, requester, category, priority, acceptance criteria, complexity, scope, testing, and release phase. It serves as a template for organizing and analyzing project requirements to ensure successful delivery. Additionally, it includes links to various project management resources and templates.

Uploaded by

Anantha Jiwaji
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as XLS, PDF, TXT or read online on Scribd
You are on page 1/ 5

PROJECT REQUIREMENTS

PROJECT MA-015-02 FULL PROJECT NAME: Project Orion


No:

DATE: PROJECT MANAGER:

REQUIREMENT LIST

ID REQUIREMENT DESCRIPTION REQUESTED BY CATEGORY PRIORITY ACCEPTANCE CRITERIA

The category or grouping of the The priority of the requirement


Give each The feature, function, condition or The stakeholder who The criteria that the requirement
requirement for example: for example: P1, P2, P3 or
requirement capability that is required from the requested the must have for it to be accepted by
functional, technical, operational, MoSCoW (Must have, should
a unique ID. project, product, service or result. requirement. the project stakeholders.
KPI (result metric), transitional. have, could have, won't have).

Page 1 of 5
REQUIREMENTS ANALYSIS

PHASE OR
COMPLEXITY IN SCOPE? TEST OR VERIFICATION RELEASE

An indication of how complex it will Whether the requirement is going to The project phase or
How the requirement will be
be to deliver the requirement. For be in the scope of the project. This will product release
checked and tested. For
example, High, Medium, Low or Very be agreed by the project number when the
example, passes building
Simple, Simple, hard, not possible, sponsor/project board following requirement will be
regulations check.
not possible now… requirements analysis. delivered.

Page 2 of 5
ACTION ITEMS LIST - INSTRUCTIONS

DEFINITIONS
PROJECT No.

The project number is assigned by the PMO (Project Management Office) once the project is approved for funding.
This Link Takes You to Project No. in the Template
PROJECT MANAGER

The person responsible for the successful delivery of the project to time costs and quality constraints.
This Link Takes You to Project Manager in the Template
FULL PROJECT NAME

The name or title of the project.


This Link Takes you to the Full Project Name in the Template
REQUIREMENT ID

Give each requirement a unique ID.


This Takes You to Requirement ID in the Template
REQUIREMENT DESCRIPTION

The feature, function, condition or capability that is required from the project, product, service or result.
This Link Takes You to Requirement Description in the Template
REQUESTED BY

The stakeholder who requested the requirement.


This Link Takes You to Requested By in the Template
CATEGORY

The category or grouping of the requirement for example: functional, technical, operational, KPI (result metric), transitional.
This Link Takes You to Category in the Template
PRIORITY

The priority of the requirement for example: P1, P2, P3 or MoSCoW (Must have, should have, could have, won't have).

Page 3 of 5
ACTION ITEMS LIST - INSTRUCTIONS

This Link Takes You to Priority in the Template


ACCEPTANCE CRITERIA

The criteria that the requirement must have for it to be accepted by the project stakeholders.
This Link Takes You to Acceptance Criteria in the Template
COMPLEXITY

An indication of how complex it will be to deliver the requirement. For example, High, Medium, Low or Very Simple, Simple, hard, not possible, not possible now…
This Link Takes You to Complexity in the Template
IN SCOPE

Whether the requirement is going to be in the scope of the project. This will be agreed by the project sponsor/project board following requirements analysis.
This Link Takes You to In Scope in the Template
TEST OR VERIFICATION

How the requirement will be checked and tested. For example, passes building regulations check.
This Link Takes You to Test of Verification in the Template
PHASE OR RELEASE

The project phase or product release number when the requirement will be delivered.
This Link Takes You to Phase or Release in the Template

This template was provided by


https://www.stakeholdermap.com/

Page 4 of 5
Project Management resources

Project Management Templates

The Top 50 Business Risks (and how to manage them)!

Issue Log Template [free download]

End Project Report Template

Risk Register Template

Stakeholder Management Templates

Work Breakdown Structure (WBS) template in Excel

You might also like