Project Management Foundations and Value Delivery · Lesson 3

Life Cycles and Delivery Approaches: Predictive, Agile and Hybrid

6 min read

Lesson objectives

Select an initial approach using uncertainty and delivery constraints.
Distinguish iteration from incremental delivery in an example.
Explain an interface between components using different delivery approaches.

Stages are not one universal checklist

A project life cycle organizes the high-level stages that turn an idea into reality. Stages can interact sequentially, iteratively or through a context-specific combination. No arrangement suits every project. Distinguish “Where are we in the journey?” from “How will we build the solution and learn?” The first concerns stage; the second concerns delivery approach.

For learning purposes, think of the case as understanding the need, defining a solution, delivering it and moving it into operation. These are not prescribed stage names from a standard. Need-finding may recur when testing reveals users struggling with booking. Revisiting an earlier question does not itself mean loss of control; what matters is intentional learning with understood decisions and consequences.

Predictive and adaptive: responding to what is known

Predictive delivery relies more heavily on early planning when requirements are relatively clear and stable. Adaptive delivery uses shorter learning and adjustment cycles when uncertainty is higher. Hybrid delivery combines elements of both. Predictive work can still change and adaptive work still plans; the difference concerns when decisions become detailed and how feedback informs them.

Iteration and increments are different

Use this original example to separate the terms: the team revises a booking-screen prototype three times before live use; that is iteration to reduce uncertainty and improve the solution. It then releases general-course booking before workshop booking; that is incremental delivery of usable parts. Both can coexist, with each addition refined before release. A prototype is not automatically an accepted operational output, and a time period is not automatically a valuable increment.

The Agile Manifesto’s principles, originally expressed for software development, emphasize early and frequent delivery, collaboration, responsiveness and regular reflection on working methods. Applying them to training services or another sector requires contextual adaptation; it is not evidence that every software practice transfers unchanged.

Choose an approach for stated reasons

The official overview of the Agile Practice Guide, Second Edition describes framework-neutral guidance, contextual choice, distributed work and value. It supports the general orientation here, not a claim that every chapter of the book has been examined. The decision aids, situations and examples in this lesson were developed for this program.

Design the interfaces in hybrid delivery

Example

Fictional worked example: reception installation follows a stable plan while the booking form evolves through learning cycles. A one-branch trial requires four conditions: a working device, tested connectivity, a release that passed a functional booking test in the system team’s environment, and an employee who knows the support procedure. Installation evidences the first, support the second, the system team the third, and operations the fourth; the project manager checks the evidence one day before the agreed trial. If the device, release and training are ready but connectivity fails, the conclusion is “not ready for the integrated trial,” not “three-quarters ready.” Under the assumed delegation, the manager postpones the trial and assigns connection repair and retesting to support. Local screen refinement can continue, but is not a successful end-to-end booking test. This makes the hybrid interface an operational agreement rather than two disconnected completion reports.

Do not assume adaptive and agile are identical labels in every source. Adaptation describes responding to learning and change; agility also involves values, principles and practices for collaboration and value delivery. Some guides use the terms closely, so define the intended meaning. Holding a periodic review alone does not establish agile practice. For a hybrid approach, identify what is planned in advance, what evolves iteratively and how the parts connect, rather than using hybrid as a vague label for any mixture.

Exercise

Exercise 1 — ten minutes: choose an initial approach for two work packages in a service-launch project: delivering a specified edition of an operating guide with verified stable content and acceptance criteria; and designing a booking service with unexplained user difficulties. Give two reasons for each and one fact that could change your choice. A label such as “traditional” or “agile” alone is insufficient. Ongoing routine reprinting may be operations; here the question concerns delivery of defined project work.

Check your answer

Self-check: stable guide content and clear acceptance criteria support advance planning, although a significant error could require a review cycle. Uncertainty in booking supports a short experiment and user learning, provided users and testing are available. Neither approach is universally superior; justify the choice using facts and constraints.

Exercise

Exercise 2 — ten minutes: design an interface between the installation and system teams, or two teams in your work or an organization you know; the fictional case is sufficient. Write four readiness conditions, an owner for each, the trial decision-maker and an action if a condition fails. Use general roles without personal or confidential data. Could a new employee tell when the trial proceeds or pauses?

Check your answer

Possible response: installation owns device readiness; support owns connectivity tests; the system team supplies evidence of passed functional tests; operations owns employee readiness. The project manager authorizes the trial under the case rules. A missing condition is recorded with its consequences and recheck arrangements rather than hidden behind an unsupported readiness declaration.

Lesson summary

A life cycle organizes high-level stages; the delivery approach governs planning, production and learning within them. No approach is best everywhere. Iteration refines a solution, increments add usable parts, and hybrid work requires explicit boundaries, authority and integration.