This article provides an overview of the second stage of a typical waterfall project methodology.
The purpose of this phase is to define all the needs for the change. It ensures that a holistic approach to requirements gathering is undertaken and all elements of the change are addressed, such as the change itself, management systems/tools, technology/products, processes, people, measurement methods/metrics, partners/suppliers and implementation/governance strategies. Once the functional requirements, management and operational requirements and usability requirements have been produced they should be reviewed by key stakeholders (users, management, operations etc.), so that they are fully understood and approved prior to progressing to the design phase.
Entry criteria include:
- Business case/high level requirements.
- Request (CP1) Checkpoint approval from the PMO.
Exit criteria include:
- Completed requirements.
- Requirements (CP2) Checkpoint approval from the PMO.
Typical outputs include:
- Updated charter.
- Management strategies.
- CP2 pitch.
Typical PMO questions include:
- Have the requirements been approved by the users, sponsor, organisation etc?
- Has the problem statement been addressed?
- Do all key stakeholders understand and agree with requirements?
- Are there any changes in the schedule? Have they been mitigated/approved?
- Are there any changes in the cost benefit analysis? Have they received approval?
- Does the schedule still meet the customer expectations?
- Is the project resourced appropriately?
- Is there anything identified that could negatively impact cost or delivery?
- Have you identified all of the configuration items that will be impacted?
- Have constraints to design, transition and operations been identified and mitigated?
- Has a full risk assessment been carried and key risks addressed?
For more information please contact Morland-Austin at firstname.lastname@example.org.