SkarpChapter 3 of 11
From Idea to Delivery: The Project Life Cycle Explained
Walk through a project’s journey from initial concept to final handover, seeing how breaking work into phases reduces risk and makes control possible.
1. Orienting Yourself: Why the Life Cycle Matters
Why the Life Cycle Matters
The project life cycle describes how a project moves from first idea to final closure. It connects what a project is, why it is approved, and how success is judged over time.
Projects vs Operations
- Operations = keep the engine running.
- Project = design, build and hand over a new engine.
- Life cycle = the route map from sketching to handover and learning.
Generic Four-Phase Model
A common PFQ-aligned life cycle has four phases: 1) Concept, 2) Definition, 3) Development, 4) Handover and closure.
Different Labels, Same Logic
Organisations may say "initiation" or "execution", but the underlying logic is the same: move from idea, to detailed plan, to building, to handover and learning.
How This Fits Previous Modules
The business case is born in concept and refined later. Success is ultimately judged when benefits are realised, usually after handover.
2. The Generic Project Life Cycle Sketch
Visualising the Life Cycle
Picture a horizontal line with four blocks: Concept → Definition → Development → Handover & Closure. It runs from first idea to transition into business-as-usual.
Simple Text Sketch
```text
Idea → [ Concept ] → [ Definition ] → [ Development ] → [ Handover & Closure ] → BAU
```
What Each Block Represents
Concept = "Should we do this?". Definition = "How will we do it?". Development = "Do the work". Handover & closure = "Deliver, transition, learn".
Decision Gates
Between phases sit gates where governance bodies decide to go, hold, change, or stop. This is where the business case is checked and updated.
Organisation Methodologies
Organisations may brand their own frameworks, but PFQ focuses on the generic logic of moving from idea to delivery and closure.
3. Example Walkthrough: Student App Project
Student App Scenario
A university wants a mobile app to help students find free study spaces and book rooms. We will follow this project through the four life cycle phases.
Concept Phase in the Scenario
Problem identified, options explored, rough costs and benefits estimated, feasibility checked, and a high-level business case taken to a digital committee for approval.
Definition Phase in the Scenario
Detailed requirements gathered, scope clarified, plans for schedule, cost, risk, quality and communication created, and the business case refined for a funding decision.
Development Phase in the Scenario
App is designed, coded and tested; sensors installed; progress monitored; risks, issues and changes managed; project board receives regular status reports.
Handover and Closure in the Scenario
App released, training provided, support handed to IT operations, benefits review plan agreed, lessons learned captured, and the project formally closed.
4. Concept Phase: From Idea to Viable Proposal
Purpose of Concept Phase
The concept phase turns a raw idea into a viable proposal. It answers: "Is this worth exploring further compared to other opportunities?"
Typical Concept Activities
Clarify the problem, identify key stakeholders, explore options, and prepare an outline business case with high-level costs, benefits and risks.
Key Outputs
Outputs include an outline business case, an initial scope statement, and a high-level view of risks and stakeholders.
Governance at Concept
Decision makers use concept-phase information to make a go/no-go choice on whether to invest in detailed planning.
Link to Strategy
Projects that align well with organisational strategy and the external environment are more likely to pass the concept gate.
5. Definition Phase: Planning for Control
Purpose of Definition Phase
The definition phase turns an approved idea into a clear, controlled plan that can be executed and monitored.
Key Planning Activities
Gather detailed requirements, define scope, break down work, build the schedule, estimate costs, and plan risk, quality, communication and resources.
Main Outputs
Outputs include a project management plan, detailed schedule and budget, and baselines for scope, time, cost and quality.
Governance at Definition
Decision makers review the refined business case and plan to decide whether to commit full resources and authorise development.
Planning and Risk Reduction
Investing in planning reduces uncertainty and makes control possible. You can only manage what you have defined and measured.
6. Thought Exercise: Why Phases Help Governance
Use this short exercise to connect phases to governance and control.
- Imagine you are on the university's digital committee from the student app example. You meet three times: end of concept, end of definition, and mid-development.
- For each meeting, jot down (in your own notes) two questions you would ask before agreeing to continue.
- End of concept: you have an outline business case.
- End of definition: you have a detailed plan and refined business case.
- Mid-development: you have progress reports and updated forecasts.
- Compare your questions with the prompts below:
- End of concept (go/no-go?):
- Does this project still align with our strategy and external environment?
- Are the expected benefits likely to justify the high-level costs and risks?
- End of definition (authorise full funding?):
- Is the plan realistic and resourced? Are the estimates credible?
- Are governance, risk and quality controls clearly defined?
- Mid-development (continue/adjust/stop?):
- Are we on track against time, cost and scope baselines?
- Have any new risks or external changes undermined the business case?
- Reflect: Which of your questions changed between meetings? This shows how each phase provides different information to support better decisions.
If you like, quickly sketch a table in your notes with columns for Phase, Decision, Key Questions. This will help you remember how phases and gates support governance for the PFQ exam.
7. Development Phase: Execution, Monitoring and Control
Purpose of Development Phase
The development phase is where the planned work is executed to create the project outputs, guided by the plans from the definition phase.
Key Execution Activities
Coordinate work and resources, monitor progress against baselines, manage risks and issues, control changes, and communicate with stakeholders.
Main Outputs
Outputs include completed deliverables, progress reports, updated forecasts, and refreshed risk, issue and change logs.
Governance in Development
Monitoring and control information allows sponsors and boards to decide whether to continue, adjust, or in rare cases stop the project.
Link to Business Case
Control is about more than schedule: it is about ensuring the project still supports the evolving business case as conditions change.
8. Handover and Closure: Beyond "Done"
Purpose of Handover & Closure
Handover and closure move the organisation from project mode to business-as-usual, ensuring outputs are accepted, supported and learned from.
Handover Activities
Verify deliverables, gain formal acceptance, transfer ownership to BAU teams, provide training and documentation, and confirm support arrangements.
Closure Activities
Finish admin and contracts, update the business case, conduct or plan benefits reviews, capture lessons learned, and produce a closure report.
Why It Matters
This phase checks that promises were delivered, supports organisational learning, and ensures that benefits are tracked and owned after the project ends.
Current Professional Focus
Since the mid‑2010s, standards have stressed benefits realisation and lessons learned; as of 2026 these remain core expectations for good governance.
9. Mini-Practice: Mapping Activities to Phases
Test your understanding by mapping activities to life cycle phases. In your notes, draw four columns: Concept, Definition, Development, Handover & Closure.
For each activity below, decide which column it belongs in:
- Run a workshop to agree detailed user requirements.
- Decide whether the project still aligns with new organisational strategy after a major policy change.
- Install new hardware and configure software.
- Prepare a high-level estimate of costs and benefits to support an initial decision.
- Capture what went well and what should change next time.
- Create a detailed risk management plan.
- Provide training sessions for end users.
Once you have placed them, compare with this suggested mapping:
- Concept: 2 (if it is about initial alignment), 4.
- Definition: 1, 6.
- Development: 3, 2 (if it is a mid-project strategy check).
- Handover & closure: 5, 7.
Notice that some activities (like checking strategic alignment) can appear in more than one phase, but the main emphasis is different:
- Early on, you check if the idea is aligned enough to explore.
- Later, you check if the project still deserves investment given new information.
For PFQ-style questions, focus on the primary phase where an activity is most strongly associated, and be ready to justify your reasoning.
10. Quick Check: Life Cycle and Governance
Answer this PFQ-style question to check your understanding.
Why do organisations structure projects into phases with decision gates between them?
- To make projects longer so that more people can be employed on them
- To enable staged investment and control, so decisions can be reviewed as more information becomes available
- To ensure that planning is only done at the start and never revisited later
Show Answer
Answer: B) To enable staged investment and control, so decisions can be reviewed as more information becomes available
Phases with decision gates support **governance and control** by allowing staged investment and review. As the project progresses and information improves, decision makers can choose to continue, change or stop. The other options contradict professional practice and PFQ principles.
11. Flashcards: Key Life Cycle Terms
Use these cards to review core terms from this module.
- Project life cycle
- The series of phases a project passes through from initial concept to final handover and closure, used to structure work, manage risk and support governance.
- Concept phase
- Early phase where the problem or opportunity is clarified, options are explored and an outline business case is created to support an initial go/no-go decision.
- Definition phase
- Phase where detailed requirements are gathered and a project management plan is developed, including scope, schedule, cost and risk plans, enabling controlled execution.
- Development phase
- Execution phase where the planned work is carried out to create project outputs, while monitoring progress and managing risks, issues and changes.
- Handover and closure
- Final phase where deliverables are accepted and transferred to business-as-usual, contracts and admin are closed, benefits are reviewed and lessons learned are captured.
- Decision gate
- A governance point between phases where senior stakeholders review progress, the business case and risks, and decide whether to continue, change or stop the project.
- Business case
- A document that explains the justification for a project, describing benefits, costs, risks and strategic alignment; it is developed in concept and refined through later phases.
- Benefits review
- An assessment of whether the expected benefits of a project are being realised, often conducted after handover as part of benefits management.
- Lessons learned
- Insights about what worked well and what did not, captured during and at the end of a project to improve performance on future projects.
Key Terms
- Business case
- The justification for undertaking a project, describing expected benefits, costs, risks and strategic alignment; it is maintained throughout the life cycle.
- Concept phase
- The early phase where the problem or opportunity is clarified, options are explored and an outline business case is produced for an initial decision.
- Decision gate
- A formal review point between phases where governance bodies decide whether a project should proceed, change or stop based on updated information.
- Benefits review
- A review to determine whether the benefits defined in the business case are being or have been realised after project outputs are handed over.
- Lessons learned
- Documented experiences, both positive and negative, from a project, intended to improve performance on future projects.
- Definition phase
- The planning-focused phase where detailed requirements are gathered and a comprehensive project management plan is created.
- Development phase
- The execution phase where the project work is carried out, monitored and controlled to deliver the agreed outputs.
- Project life cycle
- The sequence of phases a project goes through from initial concept to final handover and closure, used to structure work and support governance.
- Handover and closure
- The final phase where outputs are accepted and transferred to business-as-usual, and closure, benefits review and lessons learned activities are completed.
- Business-as-usual (BAU)
- The normal operational activities of an organisation, into which project outputs are handed over for ongoing use and support.