How predictive, agile, and hybrid delivery approaches fit project conditions, and how formal change control protects approved baselines.
Delivery methods should fit the work, constraints, and decision environment.
| Condition | Typical fit |
|---|---|
| Stable scope, formal approvals, contract commitments | Predictive delivery with planned sequencing and baselines |
| Evolving requirements and frequent feedback | Agile delivery with short iterations |
| Fixed and uncertain workstreams in the same initiative | Hybrid delivery with explicit controls for each stream |
Change control evaluates a request before it alters an approved scope, schedule, cost, quality target, or risk position.
1Request → impact analysis → decision by the appropriate authority
2→ update approved records and communicate → implement and validate
Impact analysis should identify affected deliverables, dependencies, time, cost, quality, risk, owner, and rollback or contingency needs. Stakeholder importance does not replace the authority required to approve a baseline change.