HKSM

Key Points

• Defines the sequence of phases, major deliverables, and decision gates for the project.
• States the development approach: predictive, iterative, incremental, adaptive, or hybrid.
• Specifies entry and exit criteria for each phase to support governance and quality.
• Describes delivery cadence, such as iterations, releases, milestones, and integration points.
• Tailored to the project context and updated as new information emerges.
• Enables realistic planning for scope, schedule, cost, risks, and resources.

Purpose of Analysis

This analysis clarifies how work will flow through the project, how decisions will be made, and when value will be delivered. It aligns stakeholders on the big picture of delivery and governance before detailed plans are developed.

Method Steps

• Select the development approach and explain why it fits the level of uncertainty and constraints.
• List phases and their sequence, noting any overlap or iterative loops.
• Define each phase's objectives, key deliverables, and entry/exit criteria.
• Identify decision gates, required approvals, and governance roles and cadence.
• Map delivery cadence: iterations, releases, demos, pilots, handoffs, and integration events.
• Document tailoring rules and how changes to the life cycle will be controlled.
• Review with stakeholders, refine, then communicate and baseline as appropriate.

Inputs Needed

• Project charter and business case.
• Organizational standards, life cycle models, and governance policies.
• Product roadmap or vision and key delivery constraints.
• Stakeholder expectations and compliance or regulatory requirements.
• Risk profile, uncertainty level, and technical or architectural context.

Outputs Produced

• Documented project life cycle description (concise text and/or simple diagram).
• Phase definitions with objectives and entry/exit criteria.
• Governance model with decision gates, roles, and approval timing.
• Delivery cadence plan covering iterations, releases, and key milestones.
• Tailoring guidelines, assumptions, and approach rationale.
• Linkages to plan components, such as schedule structure and estimating approach.

Interpretation Tips

• Treat it as a framework for planning and control, not a detailed schedule.
• In agile or hybrid work, emphasize cadence, feedback loops, and release criteria.
• Align phases and gates with procurement, security, and regulatory checkpoints.
• Update the description when key risks, constraints, or assumptions change.
• Use clear, consistent terms that match organizational standards.
• Keep the diagram simple so stakeholders can quickly grasp the flow.

Example

A hybrid life cycle for a new service: Phase 1 Discovery (4 weeks) with a gate to approve build; Phase 2 Iterative Build (three 4-week iterations) with demos each iteration; Phase 3 Pilot Release (4 weeks) with a go/no-go gate; Phase 4 Rollout and Transition (4 weeks) with training and handover. Governance reviews occur at each gate, and release readiness criteria are defined up front.

Pitfalls

• Confusing the life cycle description with the detailed schedule or WBS.
• Choosing a rigid approach that does not match uncertainty or stakeholder needs.
• Omitting entry/exit criteria, causing unclear quality and approval expectations.
• Ignoring compliance or procurement checkpoints in the phase and gate design.
• Failing to update the description when context or risks evolve.
• Using jargon-heavy diagrams that stakeholders cannot easily interpret.

PMP Example Question

A sponsor asks for a concise view of how the project will progress, including phases, decision gates, and delivery cadence. Which artifact best satisfies this request?

1. Work breakdown structure.
2. Project life cycle description.
3. Schedule baseline.
4. Release burn-up chart.

Correct Answer: B — Project life cycle description

Explanation: The life cycle description outlines phases, governance gates, and delivery cadence at a high level. A WBS and schedule baseline are more detailed planning artifacts and do not convey governance flow as clearly.