Statement of requirements—Template
Project Name:
Branch:
National Project Management System
Business Projects-Information Technology-Enabled - definition phase
On this page
- Purpose
- Background
- Problem/Opportunity Definition
- Risk Considerations
- PSPC Approvals Sought
- Risk(s) of NOT Proceeding
- Approval Authority
- Financials
List of Tables
Instructions
This document is your template for producing the National Project Management System (NPMS) Business Project-IT-Enabled Statement of Requirement document.
Document Purpose
A Statement of Requirement document is a proposal to an authority, stating a business problem or an opportunity and seeking funding and approval to conduct project identification stage activities. The intent of this stage is to produce a Business Case and a project charterwhich will support a decision whether or not to proceed to the Delivery Stage at the National Project Management System (NPMS) preliminary project approval (PPA) gate.
Using this Template
To create a Statement of Requirement document from this template, simply do the following:
- Replace the title on the cover page with "the name of your project, and the document type: Statement of Requirement" and delete the brackets
- Save your document with a file name that is in accordance with current branch document naming standards
- Update the file name in the document footer by right-clicking and selecting Update Field
- Complete the entire template. Each section contains brief instructions, shown in italics, which can be removed once your document is finalized
- Update the table of contents by right-clicking and selecting Update Field, then update entire table
- Upon completing the Draft Template, delete this page
Revision History
Note: This table is only for example and contains no data.
Version Number | Description | Date Modified | Author |
---|---|---|---|
1.0 | |||
Authority Signatures
- Prepared by:
- (Public Services and Procurement Canada (PSPC)) / Signature
- Please print:
- Name:
- Position:
- Date:
- Prepared by:
- (PSPC) / Signature
- Please print:
- Name:
- Project Analyst:
- Date:
- Recommended by:
- (PSPC) / Signature
- Please print:
- Name:
- Title:
- Date:
- Approved by:
- (PSPC) / Signature
- Please print:
- Name:
- Title:
- Date:
1. Purpose
The purpose of this Statement of Requirement document is to request seed funding for <an initiative related to… line of business.>
Insert the problem or opportunity statement here. The statement outlines the business problem or opportunity that will be addressed. This statement will be re-used in later documents so the statement needs to be clear and concise.
2. Background
Provide background information related to the problem or opportunity. This background may include references to the business or value drivers. The background information you provide may relate to external policy, legislative or regulatory changes, transformative changes within the relevant industry and/or relate to internal drivers for example, the need to leverage process efficiencies that can reduce costs, speed up services, improve quality, etc.
3. Problem/Opportunity Definition
This section provides a brief, high-level description of the nature of the problem/opportunity identified in the Purpose section. This section can also provide overall timing and any special considerations and identify initial constraints or assumptions, such as whether the initiative is client specific, a shared service or corporate initiative, whether focusing on infrastructure, application or system or some combination.
4. Risk Considerations
High-level risks related to this initiative could include:
- A
- B
5. Public Services and Procurement Canada Approvals Sought
This Statement of approval document seeks:
- Approval of the statement of requirements
- Approval to initiate the documentation related to the development of this project to preliminary project approval (PPA)
- Spending Authority in the amount of $K seed funding (total estimated $K) to prepare a PPA, to undertake feasibility studies and to finalize the Business Case until approval. See section 7
6. Risk(s) of NOT Proceeding
By maintaining the status quo, PSPC will risk ….
7. Approval Authority
Refer to Annex A of the NPMS Business Projects-IT-Enabled Procedure to determine the appropriate approval authority.
8. Financials
Note: This table is only for example and contains no data.
# | Source | FY1 | FY2 |
---|---|---|---|
1 | |||
2 | |||
Note: This table is only for example and contains no data.
# | Spending Breakdown | $K |
---|---|---|
1 | ||
2 | ||
Total: |
- Date modified: