keymodels
Program Requirements Document
How can program requirements document improve people, teams, or organisational effectiveness?
Public preview
What this template contains.
Purpose. Use this document to define how high-level programme requirements will be developed, analysed, reviewed, validated and verified so the programme can deliver its expected benefits. It establishes programme outcomes and specifications that component teams can decompose into component and technical requirements. Application. Prepare it after programme goals and objectives are defined, using the business case, scope statement and roadmap as primary inputs. Programme requirements should be detailed enough to di
Use context
Purpose, application, discipline.
Purpose
Use this document to define how high-level programme requirements will be developed, analysed, reviewed, validated and verified so the programme can deliver its expected benefits. It establishes programme outcomes and specifications that component teams can decompose into component and technical requirements.
Application
Prepare it after programme goals and objectives are defined, using the business case, scope statement and roadmap as primary inputs. Programme requirements should be detailed enough to direct and constrain components without prematurely prescribing every component solution. Maintain traceability from strategic need and benefit through programme requirement, component requirement, deliverable and acceptance evidence.
Completion discipline
Complete the document from current evidence, name its owner and approving authority, and link the plans, registers or decisions that support it. Retain approved versions and review the document whenever a material assumption, dependency, requirement or governance decision changes.
Field summary
Structured sections without protected files.
Document control
Program name, Program manager, Program sponsor, Actual start date
A. Purpose
Purpose
B. Requirements-management process
Requirements-management process
C. Requirements-gathering tools
Requirements-gathering tools
D. Requirements-analysis process
Requirements-analysis process
E. Requirements-review process
Requirements-review process
F. Requirements validation and verification
Requirements validation and verification
G. Approvals
Program manager, Program sponsor, Program management office director, Governance Board chairperson
Protected resources
Included resource formats.
Related models
Use these before or alongside the template.
OperationsTemplate / formChecklists for ChangeHow can checklists for change improve people, teams, or organisational effectiveness?
Organisational behaviourProcess / methodEight phases of change (Kotter)How can eight phases of change (kotter) improve people, teams, or organisational effectiveness?
Organisational behaviourTemplate / formThe Deming cycle: plan–do–check–actHow can the deming cycle: plan–do–check–act improve people, teams, or organisational effectiveness?