Project Life Cycles and Delivery Approaches
❦
The Project Life Cycle
Every project passes through broadly similar phases: it is started, planned, carried out, monitored and controlled, and closed. These match the focus areas of the PMBOK Guide's eighth edition (BrainBOK, n.d.) and the processes of PRINCE2. How these phases are arranged, and how much is planned up front, depends on the delivery approach.
Delivery Approaches
| Approach | How it works | Best when | Risk |
| Predictive (waterfall) | Plan fully, then execute in sequence (Royce, 1970) | Requirements are stable and well understood, such as construction or a standard laboratory protocol | Late discovery of problems; changes are costly |
| Iterative | Repeat cycles that refine the product | The solution must be refined through feedback | Scope can drift without limits |
| Incremental | Deliver the product in usable pieces | Early value matters | Integration of pieces can be hard |
| Agile | Short cycles with continuous feedback and adaptation (Beck et al., 2001) | Requirements are uncertain or evolving | Weak documentation or governance if misapplied |
| Hybrid | Combine predictive structure with agile execution | Large projects with fixed milestones but uncertain details | Confusion if the rules are not agreed |
Stage-Gate Processes
In research and development and in product innovation, projects are often divided into stages separated by gates, which are decision points at which a review panel decides whether to continue, stop, or redirect (Cooper, 2008). A doctoral program has the same structure in practice: the proposal defense, the annual review, the upgrade or candidacy exam, and the final defense are gates.
Choosing an Approach: The Diamond and Other Aids
Shenhar and Dvir (2007) suggested that projects can be classified along four dimensions: novelty, technology, complexity, and pace. A project with high novelty and uncertain technology needs more iteration and flexibility, while a project with a fixed deadline and mature technology needs more upfront planning. As a rule of thumb:
If you know exactly what you need and how to make it, plan it in detail.
If you know the goal but not the route, work iteratively with short cycles and frequent reviews.
If you have fixed constraints and unknown details, use a hybrid: a firm overall timeline with flexible work inside each phase.
Academic Projects Are Usually Hybrid
A thesis has fixed deadlines (a submission date, ethics approval windows, committee meetings), but the research itself is exploratory: the literature may change the question, the pilot may change the method, and the data may surprise you. A sensible approach is to fix milestones and deliverables, then manage the work between them in short cycles (see Chapter 16).
CHAPTER 4