Skip to main content
CBE NEXUS · GLOBAL HIGHER EDUCATION

Chapter 11: Agile, Hybrid and Adaptive Project Delivery

Bachelor of Project Management · Year 3 · Comprehensive undergraduate textbook notes

Chapter overview

Comprehensive undergraduate Project Management chapter on agile, hybrid and adaptive project delivery, with detailed explanations, applied frameworks, case study, revision questions and print-ready notes. The chapter develops conceptual understanding, applied analytical skill and professional judgement. Students should connect the methods to project context, organisational strategy, stakeholder needs and sustainable outcomes rather than treating techniques as isolated procedures.

Learning outcomes: explain the major concepts; interpret frameworks and evidence; apply methods to realistic projects; evaluate assumptions and limitations; consider ethical and legal responsibilities; and communicate justified recommendations.

Study approach: read the sections, create a glossary, reproduce the diagram, work through the integrated application, attempt the case study and answer the assessment questions independently before reviewing the model guidance.

Chapter learning model

DefinePurposeAnalyseEvidencePlanResourcesDeliverCoordinateEvaluateOutcomesImproveLearn

This learning model links specialist techniques to a continuous cycle of accountable project decisions. Adapt the steps to the chapter's subject and the project's governance requirements.

Chapter contents

1. Origins and principles of agile delivery2. Predictive, iterative, incremental and adaptive life cycles3. Agile values and principles in practice4. Scrum roles and accountabilities5. Product vision, goals and roadmaps6. Product backlog and prioritisation7. User stories, acceptance criteria and refinement8. Sprint planning and forecasting9. Daily coordination and impediment removal10. Sprint review and stakeholder feedback11. Retrospectives and continuous improvement12. Kanban and flow-based management13. Lean thinking and waste reduction14. Estimation and planning in agile teams15. Definition of Done and technical quality16. Agile governance, contracts and compliance17. Hybrid project delivery models18. Scaling agile across teams19. Agile metrics and evidence-based improvement20. Case study: digital public service redesign21. Release management, adoption and operational transitionIntegrated applicationExtended case studyAssessment questions

1. Origins and principles of agile delivery

Agile delivery emerged in response to complex work where requirements evolve and early feedback is valuable. Rather than treating a detailed initial plan as permanently fixed, agile approaches organise work into manageable increments, encourage collaboration and use frequent inspection and adaptation. Agile does not mean absence of planning, documentation or accountability. It changes the timing and granularity of decisions so that teams can learn from working outputs and stakeholder feedback. The approach is most useful when uncertainty is material and the product can be developed and reviewed progressively.

Practical application: In applying this topic, begin by stating the project context and the decision to be made. Identify the people who hold relevant knowledge, authority or exposure to the consequences. Gather evidence from approved plans, actual delivery records, specialist advice and stakeholder experience. Separate verified facts from estimates and assumptions. Compare realistic options against agreed objectives, legal and policy obligations, resource capacity and the full life-cycle effects. Record the rationale, decision owner, required action, due date and evidence that will show whether the action worked.

Critical evaluation: A critical analysis also considers limitations. A framework is a guide rather than an automatic answer: its usefulness depends on context, data quality, competence and the consequences of error. Ask whose interests may be overlooked, what could change the conclusion, whether the proposed response creates new risks and how uncertainty will be communicated. Where evidence is incomplete, state the gap and propose a proportionate way to learn more. Review the result after implementation and preserve lessons that can improve future projects.

Study checkpoint: For assessment, define the concept, explain its purpose, describe the steps or components, apply it to a realistic example and evaluate at least one limitation. Support recommendations with evidence and identify how performance or compliance will be checked.

2. Predictive, iterative, incremental and adaptive life cycles

A predictive life cycle defines much of the scope and sequence early, then controls delivery against an approved plan. Iterative development revisits and improves a solution through repeated cycles. Incremental delivery releases usable portions of a product over time. Adaptive approaches use short feedback loops to respond to changing needs. These models are not mutually exclusive: a project may use predictive governance for funding and regulatory approvals while iterating the design and releasing software in increments. Select the life cycle according to uncertainty, risk, dependencies and the ability to obtain feedback.

Practical application: In applying this topic, begin by stating the project context and the decision to be made. Identify the people who hold relevant knowledge, authority or exposure to the consequences. Gather evidence from approved plans, actual delivery records, specialist advice and stakeholder experience. Separate verified facts from estimates and assumptions. Compare realistic options against agreed objectives, legal and policy obligations, resource capacity and the full life-cycle effects. Record the rationale, decision owner, required action, due date and evidence that will show whether the action worked.

Critical evaluation: A critical analysis also considers limitations. A framework is a guide rather than an automatic answer: its usefulness depends on context, data quality, competence and the consequences of error. Ask whose interests may be overlooked, what could change the conclusion, whether the proposed response creates new risks and how uncertainty will be communicated. Where evidence is incomplete, state the gap and propose a proportionate way to learn more. Review the result after implementation and preserve lessons that can improve future projects.

Study checkpoint: For assessment, define the concept, explain its purpose, describe the steps or components, apply it to a realistic example and evaluate at least one limitation. Support recommendations with evidence and identify how performance or compliance will be checked.

3. Agile values and principles in practice

Agile values emphasise people and interactions, working solutions, customer collaboration and responding to change while recognising the value of processes, documentation, contracts and plans. Principles include frequent delivery, sustainable pace, technical excellence, simplicity and regular reflection. Applying these ideas requires judgement. A regulated project may need extensive evidence and formal approval; an agile team can still create that evidence continuously. The practical test is whether processes help the team deliver useful outcomes and learn, rather than becoming rituals disconnected from value.

Practical application: In applying this topic, begin by stating the project context and the decision to be made. Identify the people who hold relevant knowledge, authority or exposure to the consequences. Gather evidence from approved plans, actual delivery records, specialist advice and stakeholder experience. Separate verified facts from estimates and assumptions. Compare realistic options against agreed objectives, legal and policy obligations, resource capacity and the full life-cycle effects. Record the rationale, decision owner, required action, due date and evidence that will show whether the action worked.

Critical evaluation: A critical analysis also considers limitations. A framework is a guide rather than an automatic answer: its usefulness depends on context, data quality, competence and the consequences of error. Ask whose interests may be overlooked, what could change the conclusion, whether the proposed response creates new risks and how uncertainty will be communicated. Where evidence is incomplete, state the gap and propose a proportionate way to learn more. Review the result after implementation and preserve lessons that can improve future projects.

Study checkpoint: For assessment, define the concept, explain its purpose, describe the steps or components, apply it to a realistic example and evaluate at least one limitation. Support recommendations with evidence and identify how performance or compliance will be checked.

4. Scrum roles and accountabilities

Scrum defines accountabilities commonly described as Product Owner, Scrum Master and Developers. The Product Owner is accountable for maximising product value and effective Product Backlog management. The Scrum Master helps establish Scrum and improve team effectiveness. Developers create a usable increment each Sprint and manage their work. These accountabilities should not be confused with traditional job titles. One person may hold a role in a small setting, but conflicting responsibilities and decision rights must be made explicit. The team needs access to users and relevant technical expertise.

Practical application: In applying this topic, begin by stating the project context and the decision to be made. Identify the people who hold relevant knowledge, authority or exposure to the consequences. Gather evidence from approved plans, actual delivery records, specialist advice and stakeholder experience. Separate verified facts from estimates and assumptions. Compare realistic options against agreed objectives, legal and policy obligations, resource capacity and the full life-cycle effects. Record the rationale, decision owner, required action, due date and evidence that will show whether the action worked.

Critical evaluation: A critical analysis also considers limitations. A framework is a guide rather than an automatic answer: its usefulness depends on context, data quality, competence and the consequences of error. Ask whose interests may be overlooked, what could change the conclusion, whether the proposed response creates new risks and how uncertainty will be communicated. Where evidence is incomplete, state the gap and propose a proportionate way to learn more. Review the result after implementation and preserve lessons that can improve future projects.

Study checkpoint: For assessment, define the concept, explain its purpose, describe the steps or components, apply it to a realistic example and evaluate at least one limitation. Support recommendations with evidence and identify how performance or compliance will be checked.

5. Product vision, goals and roadmaps

A product vision describes the intended future value for users and the organisation. Product goals translate the vision into outcomes that can guide prioritisation. A roadmap communicates likely themes, capabilities and direction over time; it should not be mistaken for an immutable promise of exact features and dates. Good roadmaps make assumptions and confidence visible. They connect user needs, strategic objectives, dependencies and investment decisions. Review the roadmap when evidence changes, and explain why priorities move so stakeholders understand the trade-offs.

Practical application: In applying this topic, begin by stating the project context and the decision to be made. Identify the people who hold relevant knowledge, authority or exposure to the consequences. Gather evidence from approved plans, actual delivery records, specialist advice and stakeholder experience. Separate verified facts from estimates and assumptions. Compare realistic options against agreed objectives, legal and policy obligations, resource capacity and the full life-cycle effects. Record the rationale, decision owner, required action, due date and evidence that will show whether the action worked.

Critical evaluation: A critical analysis also considers limitations. A framework is a guide rather than an automatic answer: its usefulness depends on context, data quality, competence and the consequences of error. Ask whose interests may be overlooked, what could change the conclusion, whether the proposed response creates new risks and how uncertainty will be communicated. Where evidence is incomplete, state the gap and propose a proportionate way to learn more. Review the result after implementation and preserve lessons that can improve future projects.

Study checkpoint: For assessment, define the concept, explain its purpose, describe the steps or components, apply it to a realistic example and evaluate at least one limitation. Support recommendations with evidence and identify how performance or compliance will be checked.

6. Product backlog and prioritisation

A Product Backlog is an ordered, evolving list of work needed to improve a product. Items should be sufficiently clear for discussion, estimation and selection, but excessive detail too early can waste effort. Prioritisation may consider user value, risk reduction, urgency, cost of delay, dependencies, learning and regulatory obligations. Techniques such as MoSCoW, value-versus-effort mapping and weighted scoring can structure discussion. No formula removes the need for accountable judgement. Mandatory safety or legal work must not be deprioritised simply because a scoring model gives it a low commercial value.

Practical application: In applying this topic, begin by stating the project context and the decision to be made. Identify the people who hold relevant knowledge, authority or exposure to the consequences. Gather evidence from approved plans, actual delivery records, specialist advice and stakeholder experience. Separate verified facts from estimates and assumptions. Compare realistic options against agreed objectives, legal and policy obligations, resource capacity and the full life-cycle effects. Record the rationale, decision owner, required action, due date and evidence that will show whether the action worked.

Critical evaluation: A critical analysis also considers limitations. A framework is a guide rather than an automatic answer: its usefulness depends on context, data quality, competence and the consequences of error. Ask whose interests may be overlooked, what could change the conclusion, whether the proposed response creates new risks and how uncertainty will be communicated. Where evidence is incomplete, state the gap and propose a proportionate way to learn more. Review the result after implementation and preserve lessons that can improve future projects.

Study checkpoint: For assessment, define the concept, explain its purpose, describe the steps or components, apply it to a realistic example and evaluate at least one limitation. Support recommendations with evidence and identify how performance or compliance will be checked.

7. User stories, acceptance criteria and refinement

A user story expresses a need from the perspective of a user or stakeholder, often using the structure: as a user, I want a capability, so that I achieve a benefit. Acceptance criteria define observable conditions that demonstrate the item is complete. Refinement is the ongoing process of clarifying, splitting, estimating and ordering backlog items. Good stories focus on outcomes rather than prescribing unnecessary implementation detail. Include edge cases, accessibility, security and data requirements. A story is not ready merely because it has been written in a template.

Practical application: In applying this topic, begin by stating the project context and the decision to be made. Identify the people who hold relevant knowledge, authority or exposure to the consequences. Gather evidence from approved plans, actual delivery records, specialist advice and stakeholder experience. Separate verified facts from estimates and assumptions. Compare realistic options against agreed objectives, legal and policy obligations, resource capacity and the full life-cycle effects. Record the rationale, decision owner, required action, due date and evidence that will show whether the action worked.

Critical evaluation: A critical analysis also considers limitations. A framework is a guide rather than an automatic answer: its usefulness depends on context, data quality, competence and the consequences of error. Ask whose interests may be overlooked, what could change the conclusion, whether the proposed response creates new risks and how uncertainty will be communicated. Where evidence is incomplete, state the gap and propose a proportionate way to learn more. Review the result after implementation and preserve lessons that can improve future projects.

Study checkpoint: For assessment, define the concept, explain its purpose, describe the steps or components, apply it to a realistic example and evaluate at least one limitation. Support recommendations with evidence and identify how performance or compliance will be checked.

8. Sprint planning and forecasting

Sprint Planning establishes why the Sprint is valuable, what can be completed and how the selected work will be delivered. The team considers the Sprint Goal, backlog order, capacity, dependencies and its understanding of the work. Forecasting uses evidence from previous delivery and current conditions, not pressure to promise unrealistic output. Velocity, where used, is a team-specific historical measure and should not be used to compare individuals or teams. Forecasts should be updated as learning occurs and communicated with appropriate uncertainty.

Practical application: In applying this topic, begin by stating the project context and the decision to be made. Identify the people who hold relevant knowledge, authority or exposure to the consequences. Gather evidence from approved plans, actual delivery records, specialist advice and stakeholder experience. Separate verified facts from estimates and assumptions. Compare realistic options against agreed objectives, legal and policy obligations, resource capacity and the full life-cycle effects. Record the rationale, decision owner, required action, due date and evidence that will show whether the action worked.

Critical evaluation: A critical analysis also considers limitations. A framework is a guide rather than an automatic answer: its usefulness depends on context, data quality, competence and the consequences of error. Ask whose interests may be overlooked, what could change the conclusion, whether the proposed response creates new risks and how uncertainty will be communicated. Where evidence is incomplete, state the gap and propose a proportionate way to learn more. Review the result after implementation and preserve lessons that can improve future projects.

Study checkpoint: For assessment, define the concept, explain its purpose, describe the steps or components, apply it to a realistic example and evaluate at least one limitation. Support recommendations with evidence and identify how performance or compliance will be checked.

9. Daily coordination and impediment removal

A Daily Scrum is a short event for Developers to inspect progress toward the Sprint Goal and adapt the plan. It is not intended as a status performance for a manager. Teams may use a board, conversation or other method that supports coordination. Impediments can include delayed decisions, unavailable environments, unclear requirements, technical debt and external dependencies. The Scrum Master or project leadership helps remove systemic obstacles while the team manages its own work. Escalation should be timely when the team cannot resolve an impediment within its authority.

Practical application: In applying this topic, begin by stating the project context and the decision to be made. Identify the people who hold relevant knowledge, authority or exposure to the consequences. Gather evidence from approved plans, actual delivery records, specialist advice and stakeholder experience. Separate verified facts from estimates and assumptions. Compare realistic options against agreed objectives, legal and policy obligations, resource capacity and the full life-cycle effects. Record the rationale, decision owner, required action, due date and evidence that will show whether the action worked.

Critical evaluation: A critical analysis also considers limitations. A framework is a guide rather than an automatic answer: its usefulness depends on context, data quality, competence and the consequences of error. Ask whose interests may be overlooked, what could change the conclusion, whether the proposed response creates new risks and how uncertainty will be communicated. Where evidence is incomplete, state the gap and propose a proportionate way to learn more. Review the result after implementation and preserve lessons that can improve future projects.

Study checkpoint: For assessment, define the concept, explain its purpose, describe the steps or components, apply it to a realistic example and evaluate at least one limitation. Support recommendations with evidence and identify how performance or compliance will be checked.

10. Sprint review and stakeholder feedback

A Sprint Review is an opportunity to inspect the outcome of the Sprint with stakeholders and discuss progress toward product goals. It should be a working session, not merely a scripted demonstration. Feedback may change backlog priorities, reveal new needs or challenge assumptions about value. Stakeholders should understand what is complete, what remains uncertain and what decisions are needed. A review should not be used to disguise unfinished work as complete. Acceptance depends on agreed quality and completion criteria, not presentation polish.

Practical application: In applying this topic, begin by stating the project context and the decision to be made. Identify the people who hold relevant knowledge, authority or exposure to the consequences. Gather evidence from approved plans, actual delivery records, specialist advice and stakeholder experience. Separate verified facts from estimates and assumptions. Compare realistic options against agreed objectives, legal and policy obligations, resource capacity and the full life-cycle effects. Record the rationale, decision owner, required action, due date and evidence that will show whether the action worked.

Critical evaluation: A critical analysis also considers limitations. A framework is a guide rather than an automatic answer: its usefulness depends on context, data quality, competence and the consequences of error. Ask whose interests may be overlooked, what could change the conclusion, whether the proposed response creates new risks and how uncertainty will be communicated. Where evidence is incomplete, state the gap and propose a proportionate way to learn more. Review the result after implementation and preserve lessons that can improve future projects.

Study checkpoint: For assessment, define the concept, explain its purpose, describe the steps or components, apply it to a realistic example and evaluate at least one limitation. Support recommendations with evidence and identify how performance or compliance will be checked.

11. Retrospectives and continuous improvement

A retrospective examines how the team worked, including collaboration, tools, quality, processes and relationships. The purpose is to identify useful improvements and agree experiments, not assign blame. Teams may use structured prompts, timelines, data or anonymous feedback. Limit actions to a manageable number, assign owners and review whether changes made a difference. Psychological safety is essential because people must be able to discuss mistakes and friction honestly. Repeated retrospectives without follow-through undermine trust and waste the opportunity to improve.

Practical application: In applying this topic, begin by stating the project context and the decision to be made. Identify the people who hold relevant knowledge, authority or exposure to the consequences. Gather evidence from approved plans, actual delivery records, specialist advice and stakeholder experience. Separate verified facts from estimates and assumptions. Compare realistic options against agreed objectives, legal and policy obligations, resource capacity and the full life-cycle effects. Record the rationale, decision owner, required action, due date and evidence that will show whether the action worked.

Critical evaluation: A critical analysis also considers limitations. A framework is a guide rather than an automatic answer: its usefulness depends on context, data quality, competence and the consequences of error. Ask whose interests may be overlooked, what could change the conclusion, whether the proposed response creates new risks and how uncertainty will be communicated. Where evidence is incomplete, state the gap and propose a proportionate way to learn more. Review the result after implementation and preserve lessons that can improve future projects.

Study checkpoint: For assessment, define the concept, explain its purpose, describe the steps or components, apply it to a realistic example and evaluate at least one limitation. Support recommendations with evidence and identify how performance or compliance will be checked.

12. Kanban and flow-based management

Kanban visualises work, limits work in progress and manages flow through a system. A board represents workflow stages, policies and blocked work. Work-in-progress limits discourage starting more tasks than the system can finish, reducing context switching and exposing bottlenecks. Flow measures may include cycle time, throughput, work-item age and cumulative flow. Kanban does not require fixed-length Sprints. Teams should define what each column means, how work enters and exits, and how urgent work is handled without destabilising the whole system.

Practical application: In applying this topic, begin by stating the project context and the decision to be made. Identify the people who hold relevant knowledge, authority or exposure to the consequences. Gather evidence from approved plans, actual delivery records, specialist advice and stakeholder experience. Separate verified facts from estimates and assumptions. Compare realistic options against agreed objectives, legal and policy obligations, resource capacity and the full life-cycle effects. Record the rationale, decision owner, required action, due date and evidence that will show whether the action worked.

Critical evaluation: A critical analysis also considers limitations. A framework is a guide rather than an automatic answer: its usefulness depends on context, data quality, competence and the consequences of error. Ask whose interests may be overlooked, what could change the conclusion, whether the proposed response creates new risks and how uncertainty will be communicated. Where evidence is incomplete, state the gap and propose a proportionate way to learn more. Review the result after implementation and preserve lessons that can improve future projects.

Study checkpoint: For assessment, define the concept, explain its purpose, describe the steps or components, apply it to a realistic example and evaluate at least one limitation. Support recommendations with evidence and identify how performance or compliance will be checked.

13. Lean thinking and waste reduction

Lean thinking focuses on customer value, value streams, flow, pull and continuous improvement. Common forms of waste include waiting, unnecessary movement, excess processing, defects, inventory, overproduction and underused talent. In knowledge work, waste may appear as repeated approvals, hand-offs, unclear requirements or features nobody uses. Removing waste should not mean eliminating necessary controls, reflection or documentation. Map the end-to-end process, ask where value is created and test improvements while protecting safety, quality and staff wellbeing.

Practical application: In applying this topic, begin by stating the project context and the decision to be made. Identify the people who hold relevant knowledge, authority or exposure to the consequences. Gather evidence from approved plans, actual delivery records, specialist advice and stakeholder experience. Separate verified facts from estimates and assumptions. Compare realistic options against agreed objectives, legal and policy obligations, resource capacity and the full life-cycle effects. Record the rationale, decision owner, required action, due date and evidence that will show whether the action worked.

Critical evaluation: A critical analysis also considers limitations. A framework is a guide rather than an automatic answer: its usefulness depends on context, data quality, competence and the consequences of error. Ask whose interests may be overlooked, what could change the conclusion, whether the proposed response creates new risks and how uncertainty will be communicated. Where evidence is incomplete, state the gap and propose a proportionate way to learn more. Review the result after implementation and preserve lessons that can improve future projects.

Study checkpoint: For assessment, define the concept, explain its purpose, describe the steps or components, apply it to a realistic example and evaluate at least one limitation. Support recommendations with evidence and identify how performance or compliance will be checked.

14. Estimation and planning in agile teams

Agile teams may estimate using relative sizing, planning poker, affinity grouping or historical throughput. Story points, if used, represent relative complexity, uncertainty and effort within a team; they are not hours or a universal productivity measure. Estimation supports conversation about assumptions and dependencies. For highly uncertain work, a time-boxed experiment or spike may be more useful than a detailed estimate. Communicate forecasts as ranges and revise them when evidence changes. Avoid using estimates as individual performance targets.

Practical application: In applying this topic, begin by stating the project context and the decision to be made. Identify the people who hold relevant knowledge, authority or exposure to the consequences. Gather evidence from approved plans, actual delivery records, specialist advice and stakeholder experience. Separate verified facts from estimates and assumptions. Compare realistic options against agreed objectives, legal and policy obligations, resource capacity and the full life-cycle effects. Record the rationale, decision owner, required action, due date and evidence that will show whether the action worked.

Critical evaluation: A critical analysis also considers limitations. A framework is a guide rather than an automatic answer: its usefulness depends on context, data quality, competence and the consequences of error. Ask whose interests may be overlooked, what could change the conclusion, whether the proposed response creates new risks and how uncertainty will be communicated. Where evidence is incomplete, state the gap and propose a proportionate way to learn more. Review the result after implementation and preserve lessons that can improve future projects.

Study checkpoint: For assessment, define the concept, explain its purpose, describe the steps or components, apply it to a realistic example and evaluate at least one limitation. Support recommendations with evidence and identify how performance or compliance will be checked.

15. Definition of Done and technical quality

The Definition of Done establishes the quality conditions an increment must satisfy before it is considered complete. It may include code review, testing, security checks, documentation, accessibility, integration and deployment readiness. Clear completion criteria reduce hidden work and prevent teams from reporting partially finished features as delivered. The Definition of Done should be shared, realistic and strengthened as capability improves. It does not replace item-specific acceptance criteria; both are needed to establish that a feature meets its requirements and overall quality standards.

Practical application: In applying this topic, begin by stating the project context and the decision to be made. Identify the people who hold relevant knowledge, authority or exposure to the consequences. Gather evidence from approved plans, actual delivery records, specialist advice and stakeholder experience. Separate verified facts from estimates and assumptions. Compare realistic options against agreed objectives, legal and policy obligations, resource capacity and the full life-cycle effects. Record the rationale, decision owner, required action, due date and evidence that will show whether the action worked.

Critical evaluation: A critical analysis also considers limitations. A framework is a guide rather than an automatic answer: its usefulness depends on context, data quality, competence and the consequences of error. Ask whose interests may be overlooked, what could change the conclusion, whether the proposed response creates new risks and how uncertainty will be communicated. Where evidence is incomplete, state the gap and propose a proportionate way to learn more. Review the result after implementation and preserve lessons that can improve future projects.

Study checkpoint: For assessment, define the concept, explain its purpose, describe the steps or components, apply it to a realistic example and evaluate at least one limitation. Support recommendations with evidence and identify how performance or compliance will be checked.

16. Agile governance, contracts and compliance

Agile governance provides direction, funding, risk oversight and decision authority while allowing teams to adapt delivery. Governance can use outcome-based milestones, evidence reviews, product goals and incremental funding. Contracts may specify deliverables, service levels, acceptance, change mechanisms and collaboration responsibilities without prescribing every design decision. Compliance evidence should be generated as part of normal work. The project manager must reconcile iterative delivery with procurement rules, privacy, security, safety, records retention and audit requirements in the relevant jurisdiction.

Practical application: In applying this topic, begin by stating the project context and the decision to be made. Identify the people who hold relevant knowledge, authority or exposure to the consequences. Gather evidence from approved plans, actual delivery records, specialist advice and stakeholder experience. Separate verified facts from estimates and assumptions. Compare realistic options against agreed objectives, legal and policy obligations, resource capacity and the full life-cycle effects. Record the rationale, decision owner, required action, due date and evidence that will show whether the action worked.

Critical evaluation: A critical analysis also considers limitations. A framework is a guide rather than an automatic answer: its usefulness depends on context, data quality, competence and the consequences of error. Ask whose interests may be overlooked, what could change the conclusion, whether the proposed response creates new risks and how uncertainty will be communicated. Where evidence is incomplete, state the gap and propose a proportionate way to learn more. Review the result after implementation and preserve lessons that can improve future projects.

Study checkpoint: For assessment, define the concept, explain its purpose, describe the steps or components, apply it to a realistic example and evaluate at least one limitation. Support recommendations with evidence and identify how performance or compliance will be checked.

17. Hybrid project delivery models

Hybrid delivery combines predictive and adaptive methods. A construction project may use a fixed regulatory approval path and detailed critical-path schedule while using iterative prototyping for user interfaces or control systems. A hybrid model should define which components are fixed, which can evolve, how interfaces are governed and how integrated changes are approved. Without explicit boundaries, teams can experience conflicting reporting cycles and unclear authority. Tailor the model to uncertainty and dependency rather than labelling a project hybrid simply because it uses several tools.

Practical application: In applying this topic, begin by stating the project context and the decision to be made. Identify the people who hold relevant knowledge, authority or exposure to the consequences. Gather evidence from approved plans, actual delivery records, specialist advice and stakeholder experience. Separate verified facts from estimates and assumptions. Compare realistic options against agreed objectives, legal and policy obligations, resource capacity and the full life-cycle effects. Record the rationale, decision owner, required action, due date and evidence that will show whether the action worked.

Critical evaluation: A critical analysis also considers limitations. A framework is a guide rather than an automatic answer: its usefulness depends on context, data quality, competence and the consequences of error. Ask whose interests may be overlooked, what could change the conclusion, whether the proposed response creates new risks and how uncertainty will be communicated. Where evidence is incomplete, state the gap and propose a proportionate way to learn more. Review the result after implementation and preserve lessons that can improve future projects.

Study checkpoint: For assessment, define the concept, explain its purpose, describe the steps or components, apply it to a realistic example and evaluate at least one limitation. Support recommendations with evidence and identify how performance or compliance will be checked.

18. Scaling agile across teams

When multiple teams contribute to one product or programme, they need coordination around architecture, shared dependencies, integration, release planning and common quality expectations. Scaling should solve actual coordination problems rather than add layers of ceremony. Teams need clear ownership of interfaces and a way to resolve cross-team impediments. Shared backlogs or integrated planning may help, but local teams still require autonomy to organise their work. Avoid assuming that a framework guarantees success; assess whether it improves transparency, flow and delivery outcomes.

Practical application: In applying this topic, begin by stating the project context and the decision to be made. Identify the people who hold relevant knowledge, authority or exposure to the consequences. Gather evidence from approved plans, actual delivery records, specialist advice and stakeholder experience. Separate verified facts from estimates and assumptions. Compare realistic options against agreed objectives, legal and policy obligations, resource capacity and the full life-cycle effects. Record the rationale, decision owner, required action, due date and evidence that will show whether the action worked.

Critical evaluation: A critical analysis also considers limitations. A framework is a guide rather than an automatic answer: its usefulness depends on context, data quality, competence and the consequences of error. Ask whose interests may be overlooked, what could change the conclusion, whether the proposed response creates new risks and how uncertainty will be communicated. Where evidence is incomplete, state the gap and propose a proportionate way to learn more. Review the result after implementation and preserve lessons that can improve future projects.

Study checkpoint: For assessment, define the concept, explain its purpose, describe the steps or components, apply it to a realistic example and evaluate at least one limitation. Support recommendations with evidence and identify how performance or compliance will be checked.

19. Agile metrics and evidence-based improvement

Useful measures may include lead time, cycle time, throughput, escaped defects, deployment frequency, service reliability, customer outcomes and team health. Metrics should answer a decision question and be interpreted in context. A high velocity may reflect inflated estimates rather than value. More releases do not prove user benefit if adoption or quality is poor. Use a balanced set of leading and lagging indicators, examine trends and discuss unintended incentives. Never reduce a complex team's contribution to a single ranking.

Practical application: In applying this topic, begin by stating the project context and the decision to be made. Identify the people who hold relevant knowledge, authority or exposure to the consequences. Gather evidence from approved plans, actual delivery records, specialist advice and stakeholder experience. Separate verified facts from estimates and assumptions. Compare realistic options against agreed objectives, legal and policy obligations, resource capacity and the full life-cycle effects. Record the rationale, decision owner, required action, due date and evidence that will show whether the action worked.

Critical evaluation: A critical analysis also considers limitations. A framework is a guide rather than an automatic answer: its usefulness depends on context, data quality, competence and the consequences of error. Ask whose interests may be overlooked, what could change the conclusion, whether the proposed response creates new risks and how uncertainty will be communicated. Where evidence is incomplete, state the gap and propose a proportionate way to learn more. Review the result after implementation and preserve lessons that can improve future projects.

Study checkpoint: For assessment, define the concept, explain its purpose, describe the steps or components, apply it to a realistic example and evaluate at least one limitation. Support recommendations with evidence and identify how performance or compliance will be checked.

20. Case study: digital public service redesign

A public agency is replacing a paper-based application process with an online service. Requirements are uncertain because users have different levels of connectivity, digital confidence and accessibility needs. Students should propose a delivery life cycle, product vision, stakeholder engagement plan, backlog structure and first release goal. Explain how the team will test usability, protect personal data, provide assisted or offline alternatives and comply with approval requirements. Set measurable outcome indicators such as completion rate, processing time, error rate and user satisfaction, and define how feedback will influence later increments.

Practical application: In applying this topic, begin by stating the project context and the decision to be made. Identify the people who hold relevant knowledge, authority or exposure to the consequences. Gather evidence from approved plans, actual delivery records, specialist advice and stakeholder experience. Separate verified facts from estimates and assumptions. Compare realistic options against agreed objectives, legal and policy obligations, resource capacity and the full life-cycle effects. Record the rationale, decision owner, required action, due date and evidence that will show whether the action worked.

Critical evaluation: A critical analysis also considers limitations. A framework is a guide rather than an automatic answer: its usefulness depends on context, data quality, competence and the consequences of error. Ask whose interests may be overlooked, what could change the conclusion, whether the proposed response creates new risks and how uncertainty will be communicated. Where evidence is incomplete, state the gap and propose a proportionate way to learn more. Review the result after implementation and preserve lessons that can improve future projects.

Study checkpoint: For assessment, define the concept, explain its purpose, describe the steps or components, apply it to a realistic example and evaluate at least one limitation. Support recommendations with evidence and identify how performance or compliance will be checked.

21. Release management, adoption and operational transition

A release moves a tested increment into use. Release planning considers readiness, dependencies, migration, training, support, security, rollback and communication. Frequent deployment is not always appropriate; high-risk or regulated services may require staged releases and formal authorisation. Operational teams need runbooks, monitoring, ownership and support capacity. Adoption should be measured through real user outcomes rather than release counts. Plan for defects, feedback and future maintenance. The product team should understand how responsibility transfers or continues after the project delivery phase.

Practical application: In applying this topic, begin by stating the project context and the decision to be made. Identify the people who hold relevant knowledge, authority or exposure to the consequences. Gather evidence from approved plans, actual delivery records, specialist advice and stakeholder experience. Separate verified facts from estimates and assumptions. Compare realistic options against agreed objectives, legal and policy obligations, resource capacity and the full life-cycle effects. Record the rationale, decision owner, required action, due date and evidence that will show whether the action worked.

Critical evaluation: A critical analysis also considers limitations. A framework is a guide rather than an automatic answer: its usefulness depends on context, data quality, competence and the consequences of error. Ask whose interests may be overlooked, what could change the conclusion, whether the proposed response creates new risks and how uncertainty will be communicated. Where evidence is incomplete, state the gap and propose a proportionate way to learn more. Review the result after implementation and preserve lessons that can improve future projects.

Study checkpoint: For assessment, define the concept, explain its purpose, describe the steps or components, apply it to a realistic example and evaluate at least one limitation. Support recommendations with evidence and identify how performance or compliance will be checked.

Integrated worked application

Consider a regional organisation implementing a service improvement across several sites. The sponsor has approved a strategic outcome, but the delivery team must translate it into an achievable plan. Begin with the intended user and organisational outcomes, then define the scope, constraints, assumptions and acceptance evidence. Map the stakeholders and identify who can approve decisions. Break the work into manageable packages, estimate the resources and sequence dependencies. Establish a baseline and a proportionate set of indicators. During implementation, compare actual evidence with the plan, investigate material differences and decide whether corrective action or formal change approval is required.

Suppose a new requirement emerges after a pilot reveals that a group of users cannot access the service through the intended channel. Do not treat this only as a technical defect. Analyse the requirement, accessibility implications, affected users, cost and schedule consequences, data and security considerations, operational support and expected benefits. Develop options such as adapting the interface, adding assisted access or revising rollout sequence. Evaluate each option against user outcomes, compliance, affordability and delivery risk. Present a recommendation with assumptions and an explicit decision request.

After approval, update the relevant plans and communicate the change to delivery and operational teams. Test the revised solution with representative users and collect evidence against acceptance criteria. At transition, confirm training, support, ownership, documentation and unresolved issues. Later, evaluate whether the service is used and whether the intended outcome has improved. This sequence demonstrates integration: project success is not a collection of separate documents but a coherent chain from need to sustainable benefit.

Extended case study: multi-site public service transformation

A public organisation intends to modernise a service delivered through twelve regional offices. The current process relies on paper records, repeated data entry and manual approvals. Users report long waiting times and inconsistent decisions. The proposed project introduces a shared digital platform, revised operating procedures and staff development. The organisation has a fixed funding envelope, varied internet connectivity, limited internal technical capacity and a target launch period. Some stakeholders support rapid implementation; others are concerned about privacy, job changes, accessibility and disruption.

Prepare a structured project response. Define the intended outcomes and measurable indicators. Identify stakeholders, their interests and engagement needs. Set out scope, exclusions, assumptions and constraints. Propose a delivery approach that allows learning while maintaining necessary governance. Develop a high-level schedule, budget logic, risk responses and quality criteria. Explain procurement and supplier oversight where external services are required. Plan training, data migration, operational readiness and post-launch support. Include an evaluation design that can distinguish outputs from outcomes and consider whether observed changes are plausibly connected to the intervention.

During implementation, the pilot identifies data inconsistencies and a connectivity gap in three offices. The supplier requests a variation and the sponsor asks whether the launch date can be retained. Analyse the decision using evidence rather than preference. Consider a phased release, additional validation, offline capability, targeted support or a revised timetable. Identify approval authority, impact on cost and benefits, and how users will be informed. State what evidence would justify proceeding, pausing or changing the plan. Your response should demonstrate professional judgement, ethical awareness and a clear audit trail.

University assessment questions and model answer guidance

1. Explain the principal concepts and purpose addressed in this chapter.

Model answer guide: Define the key terms accurately, explain their relationship to project objectives and distinguish them from related concepts. Use a relevant example and show why the concepts matter to project decisions.

2. Compare two approaches or frameworks relevant to the chapter.

Model answer guide: Identify the purpose and assumptions of each approach, compare their strengths and limitations, and explain which project conditions would make each more suitable. Avoid claiming that one method is universally superior.

3. Apply the chapter's methods to a project experiencing a major challenge.

Model answer guide: Define the problem, establish the evidence, identify affected stakeholders, develop feasible options, assess impacts on scope, time, cost, quality, risk and benefits, recommend an action and specify how it will be monitored.

4. Evaluate the ethical, legal and sustainability implications of a project decision.

Model answer guide: Identify relevant duties and affected groups, assess possible harm and distribution of benefits, explain applicable controls and show how transparency, participation and monitoring can improve the decision.

5. Discuss how performance should be measured and reported.

Model answer guide: Select indicators aligned to outcomes, define sources and frequency, explain thresholds and limitations, and distinguish activity, output, outcome and impact measures. Recommend a reporting format suited to decision-makers.

6. Explain how lessons learned should influence future projects.

Model answer guide: Use evidence to identify causes and context, distinguish effective practice from isolated success, formulate actionable recommendations and assign responsibility for embedding improvements.

7. Prepare a concise recommendation for a project sponsor.

Model answer guide: State the decision required, preferred option, evidence, assumptions, costs, benefits, main risks, alternatives, approvals, implementation responsibilities and review triggers.

8. Essay: project success requires integration of technical delivery and organisational change. Discuss.

Model answer guide: Explain the role of outputs and technical controls, then analyse user adoption, governance, operational readiness, benefits, ethics and sustainability. Support the argument with examples and a balanced conclusion.

Revision checklist and independent study

For deeper study, consult current academic texts, peer-reviewed research, recognised professional standards, institutional library resources and applicable national laws or sector guidance. Confirm the edition and jurisdiction relevant to your course. Professional standards and legislation can change, and students should not treat these study notes as a substitute for official institutional or regulatory requirements.

Official Education References

Use these official organisations for curriculum guidance, examinations and further learning information.