Identify Requirements, Project Manager

Description

The project requirements are identified and agreed These requirements should clearly identify what is required in the clients terms and why it is important to meet these requirements.

 

  • Analyse needs including impacts and benefits.
  • Identify project requirements
  • Review and agree these with the project sponsor.
  • Identify any statutory or regulatory requirements if necessary

 

For small projects, the proposal document may be sufficient to define the project requirements (See proposal section 1.0). If this is sufficient, no additional requirements specification is required.  For small projects, the Project Brief and Project Approach may also replace this document if the proposal information is not sufficient.

Audit Criteria

  • Project Requirements have been reviewed and approved by Project Executive.
  •  

Document Templates

Forms

Process Details

  • Customer Driven Solutions Contract Management Process: Proposal Template (Small project), Section 5.1
  • Requirements Specification Contents (larger project)

References

Software Engineering

  • Reference 1
  •  

Additional Details

Requirements Specification Contents

 

The requirements specification contains the following information:

 

Sections

Description

1.0 Introduction

A brief description of the need for a solution. Provide background information about the client.

2.0 Business Objectives

State the business need and goals and measurements

3.0 Solution Requirements

Describe the requirements for a solution

4.0 Solution Measurements

Describe the measurements for the objectives.

5.0 Solution Implementation Strategies

Describe the implementation strategies for meeting the requirements

Further information concerning the requirements specification can be found in the template,

SDLC_TPL001 Requirements Specification.