How this project runs
Waterfall with phase gates
Sequential phases, a written gate at the end of each, a locked baseline and the full PMBOK document set. What the charter says it is, rather than what a tool would prefer it to be.
Breakdown
The levels work is decomposed into
- 1PhaseScheduled
- 2DeliverableScheduled
- 3Work packageEarns valueScheduledOn the boardEstimated
- 4TaskOn the boardEstimated
Consequences
What this turns on
- 9 sections in the navigation
- Approval gates between phases
- Delivery in timeboxes (off)
- Work-in-progress limits (off)
- A critical path and float
- Earned value and forecasting
- A locked baseline, so scope changes need approval
- 33 documents in the set
- 9 measures computed
Document set
33 documents
- Project charterPMBOK6:4.1
- Project management planPMBOK6:4.2
- Assumption and constraint logPMBOK6:4.1
- Change management planPMBOK6:4.6
- Lessons learned registerPMBOK6:4.4
- Project closeout reportPMBOK6:4.7
- Scope management planPMBOK6:5.1
- Requirements documentationPMBOK6:5.2
- Requirements traceability matrixPMBOK6:5.2
- Project scope statementPMBOK6:5.3
- Work breakdown structurePMBOK6:5.4
- WBS dictionaryPMBOK6:5.4
- Schedule management planPMBOK6:6.1
- Schedule baselinePMBOK6:6.5
- Milestone listPMBOK6:6.2
- Schedule network diagramPMBOK6:6.3
- Cost management planPMBOK6:7.1
- Cost baselinePMBOK6:7.3
- Project funding requirementsPMBOK6:7.3
- Quality management planPMBOK6:8.1
- Quality metricsPMBOK6:8.1
- Resource management planPMBOK6:9.1
- Responsibility assignment matrixPMBOK6:9.1
- Team charterPMBOK6:9.1
- Communications management planPMBOK6:10.1
- Status reportPMBOK6:10.2
- Risk management planPMBOK6:11.1
- Risk registerPMBOK6:11.2
- Risk reportPMBOK6:11.2
- Procurement management planPMBOK6:12.1
- Stakeholder registerPMBOK6:13.1
- Stakeholder engagement planPMBOK6:13.2
- Stakeholder engagement assessment matrixPMBOK6:13.2