Prof. Dr. Larry AdamsAcademic, Author & Researcher
Project Management — Level 7 · 13 slides

Presentation · 13 slides

Project Management — Level 7

Governance, Strategy Delivery, Risk, Benefits and Complex Programme Leadership

Prof. Dr. Larry Adams

A Level 7 teaching deck on Project Management: Governance, Strategy Delivery, Risk, Benefits and Complex Programme Leadership.

Free to view online and to download for teaching, with acknowledgement of the author. To reproduce or adapt any part of a deck, please request permission through the contact page beforehand.

  1. Project Management — Level 7

    UKVAA • ADVANCED STUDY SERIES

    Level 7 Project Management

    Governance, Strategy Delivery, Risk, Benefits and Complex Programme Leadership

    Level 7 | Strategic and critical application

    Teaching presentation • First edition • 2026

    01
  2. Learning outcomes

    • Evaluate project selection, governance and strategic alignment.
    • Develop integrated scope, schedule, cost, quality and resource plans.
    • Manage uncertainty, stakeholders, suppliers, change and assurance.
    • Choose predictive, agile or hybrid approaches with justification.
    • Measure benefits and learning beyond project closure.
    02
  3. Project, programme and portfolio context

    • Projects deliver unique outputs; programmes coordinate related projects to achieve outcomes and benefits.
    • Portfolios prioritise investment across initiatives against strategy, capacity and risk.
    • Success includes adoption, safety, sustainability and benefits—not only time, cost and scope.
    • Projects operate within governance, operating models, regulation and external constraints.
    03
  4. Business case and governance

    • Define the problem, opportunity, strategic fit, options and consequences of inaction.
    • Compare whole-life cost, benefits, disbenefits, dependencies and uncertainty.
    • Name sponsor, steering group, project manager, product owner, team and assurance roles.
    • Use decision rights, tolerances, stage gates, escalation thresholds and decision logs.
    • Revisit the business case; sunk cost alone is not a reason to continue.
    04
  5. Scope, requirements and schedule

    • Define outcomes, requirements, acceptance criteria, exclusions and assumptions.
    • Use a work breakdown structure to create manageable work packages.
    • Sequence dependencies and milestones; identify critical and near-critical paths.
    • Use three-point estimates when uncertainty is material and state planning assumptions.
    • Control change through authorised impact assessment rather than informal scope expansion.
    05
  6. Cost, forecasting and earned value

    • Build estimates from work packages, resources, supplier quotes and explicit assumptions.
    • Distinguish contingency for known risks from management reserve.
    • Track actual cost, commitments, forecast final cost and change exposure.
    • Earned value compares planned value, earned value and actual cost to diagnose trends.
    • Metrics are signals: investigate causes before deciding corrective action.
    06
  7. Risk and uncertainty

    • Identify threats and opportunities across strategic, technical, commercial and external domains.
    • Score probability and impact consistently; assign owners, triggers and due dates.
    • Treat, avoid, share or accept threats according to appetite; exploit or enhance opportunities.
    • Use sensitivity analysis and simulation for complex, high-uncertainty cases.
    • Report residual risk and escalation thresholds honestly.
    07
  8. Stakeholders, teams and quality

    • Map stakeholders by influence, interest, impact and legitimate concerns.
    • Plan two-way engagement and close feedback loops.
    • Clarify team purpose, decision rights, norms and conflict-resolution routes.
    • Define quality and acceptance criteria before delivery; combine reviews, testing and assurance.
    • Build psychological safety alongside accountability and delivery discipline.
    08
  9. Agile, predictive and hybrid delivery

    • Predictive methods support stable requirements and strong upfront coordination.
    • Agile supports iterative learning, prioritisation and frequent usable increments.
    • Hybrid models can combine stage-gate governance with iterative product delivery.
    • Choose based on uncertainty, safety, regulation, capability and stakeholder access.
    • Agile does not mean no planning, documentation, accountability or quality controls.
    09
  10. Procurement, change and benefits

    • Assess make-or-buy through capability, total cost, risk and strategic control.
    • Contracts should define deliverables, service levels, acceptance, security, IP and exit provisions.
    • Assess changes across scope, schedule, cost, quality, risk, benefits and operations.
    • Name benefit owners and define baseline, target, measurement method and realisation date.
    • Plan adoption, training, operational handover and post-project review.
    10
  11. Integrated project plan workshop

    • Prepare business case, outcomes map and governance structure.
    • Create scope baseline, schedule, budget, quality plan and resource forecast.
    • Build risk, stakeholder, communication, procurement and change registers.
    • Define acceptance, transition, operational readiness and benefit ownership.
    • Present assumptions, decision gates, early warnings and recovery options.
    11
  12. End-text references and further reading (1)

    • AXELOS (2017). Managing Successful Projects with PRINCE2. TSO.
    • Edmondson, A.C. (2018). The Fearless Organization. Wiley.
    • Fleming, Q.W. & Koppelman, J.M. (2016). Earned Value Project Management (4th ed.). PMI.
    • Freeman, R.E. (1984). Strategic Management: A Stakeholder Approach. Pitman.
    • HM Treasury (2022). The Green Book.
    • UKVAA | References for further reading; check current editions and local requirements
    • UKVAA | References for further reading; check current editions and local requirements
    12
  13. End-text references and further reading (2)

    • ISO 9001:2015; ISO 20400:2017; ISO 21502:2020; ISO 31000:2018.
    • Kerzner, H. (2022). Project Management: A Systems Approach (13th ed.). Wiley.
    • PMI (2021). PMBOK Guide (7th ed.). Project Management Institute.
    • PMI & Agile Alliance (2017). Agile Practice Guide.
    • Schwaber, K. & Sutherland, J. (2020). The Scrum Guide.
    • UKVAA | References for further reading; check current editions and local requirements
    • UKVAA | References for further reading; check current editions and local requirements
    13
01 / 13