Playbooks
Real-world delivery playbooks for enterprise Agile teams.
59 practical guides across 5 delivery roles — filter by your role to find what's relevant. Each playbook is written from real enterprise experience, not theory.
Showing 59 of 59 playbooks
Agile Metrics That Actually Matter
Use metrics for decisions, not theatre: flow, predictability, quality, health, and business outcomes.
Read guideBenefits Realisation — From Business Case to Outcomes
Most programmes deliver on time and budget but never measure whether they achieved the outcomes promised in the business case. Benefits realisation closes this gap — here's how to implement it from day one.
Read guideBenefits Tracking Across the Portfolio
Individual programmes track their own benefits. The Portfolio Manager tracks whether the organisation's total investment is delivering the total expected return. Here's how to build that aggregate view.
Read guideBuilding Portfolio Health Dashboards
A portfolio dashboard gives executives a single view of delivery health across all programmes and projects. Here's how to build one that drives investment decisions — not just displays status.
Read guideBuilding Psychological Safety in Agile Teams
Google's Project Aristotle found psychological safety is the single biggest predictor of team performance. Here's how Scrum Masters can build it deliberately — not just hope it happens.
Read guideBuilding Trust with Engineering Teams
Engineers don't trust Delivery Managers by default — they've been burned by managers who add process without understanding the work. Here's how to earn trust through competence, consistency, and genuine service.
Read guideBuilding a Delivery Health Dashboard
A delivery health dashboard should drive decisions, not just display data. Here's how to build one that surfaces risk early, aligns stakeholders, and makes delivery conversations faster and more productive.
Read guideBuilding a Portfolio Management Capability
Portfolio management isn't a role — it's an organisational capability. Here's how to build it from scratch: the people, processes, tools, and governance that turn a collection of projects into a strategically managed investment portfolio.
Read guideBuilding and Evolving Your Definition of Done
A weak Definition of Done is the single biggest source of escaped defects, rework, and 'done but not really done' stories. Here's how to build one that actually protects quality.
Read guideBuilding and Running a Programme Management Office
A PMO that adds value accelerates delivery. A PMO that adds bureaucracy slows it down. Here's how to build one that teams actually want to engage with — not one they work around.
Read guideCapacity Planning for Delivery Teams
Capacity planning is not about squeezing maximum output from teams. It's about making realistic commitments, preventing burnout, and giving stakeholders honest forecasts they can plan around.
Read guideCapacity vs Demand Management at Portfolio Level
Every portfolio has more demand than capacity. The question isn't 'can we do everything?' — it's 'what's the best use of the capacity we have?' Here's how to make that visible and actionable.
Read guideChange Control in Agile-Hybrid Environments
Agile embraces change. Governance requires control. These aren't contradictions — they operate at different levels. Here's how to implement change control that protects commitments without killing agility.
Read guideCoaching Product Owners as a Scrum Master
The Scrum Master serves the Product Owner — but most don't know how. Here's a practical guide to coaching POs on backlog management, stakeholder alignment, and value maximisation without overstepping.
Read guideContinuous Improvement at Scale
Individual team retrospectives improve individual teams. But systemic problems — slow pipelines, unclear strategy, organisational silos — need improvement at scale. Here's how to drive continuous improvement across multiple teams and the organisation.
Read guideCross-Programme Dependency Orchestration
When dependencies cross programme boundaries, resolution requires influence without authority. Here's how to orchestrate dependencies across programmes, vendors, and organisational silos.
Read guideCross-Team Delivery Coordination
When multiple teams must deliver a coordinated outcome, the Delivery Manager becomes the connective tissue. Here's how to coordinate without becoming a bottleneck or adding unnecessary process.
Read guideDORA Metrics — A Practical Implementation Guide
DORA metrics are the gold standard for measuring software delivery performance. But most teams measure them wrong, report them without context, or use them punitively. Here's how to implement them properly.
Read guideDelivery Governance for Enterprise Teams
Cadences, dashboards, decision forums, and escalation patterns that help large delivery systems move.
Read guideDelivery Manager's Guide to Dependency Management
Cross-team dependencies are the number one cause of delivery delays in enterprise environments. Here's a practical operating model for surfacing them early, tracking them actively, and resolving them before they become release risk.
Read guideDelivery Reporting That Drives Decisions
Most delivery reports are read, acknowledged, and forgotten. Effective reporting drives action — it surfaces the one thing leadership needs to decide, not fifty things they need to know.
Read guideEarned Value Management Made Practical
EVM is the most reliable way to answer 'are we on track?' for budget and schedule simultaneously. But most PMs either avoid it (too complex) or misuse it (reporting without action). Here's how to make it practical.
Read guideFacilitating Effective Daily Standups
Most standups are status reports to the Scrum Master. They should be team coordination events that surface blockers and align effort toward the Sprint Goal. Here's how to make the shift.
Read guideHandling Release Bottlenecks
Diagnose bottlenecks across environments, approvals, dependencies, scope, and release confidence.
Read guideHybrid Project Management — Blending Agile and Waterfall
Pure Agile doesn't work for every project. Pure Waterfall is too rigid for most. Hybrid project management gives you structured governance with flexible execution — here's how to implement it effectively.
Read guideIncident Management for Delivery Leaders
When production breaks, the Delivery Manager's job isn't to fix the code — it's to ensure the response is coordinated, communication is clear, and the organisation learns from every incident to prevent recurrence.
Read guideJira Cloud Migration Governance
A field-tested governance approach for migration readiness, cleanup, stakeholder comms, and cutover.
Read guideManaging Cross-Team Dependencies
A practical operating model for surfacing, owning, and resolving dependencies before they become release risk.
Read guideManaging Multiple Agile Teams as a Delivery Manager
When you own delivery across 3-5 squads, you can't be in every standup or solve every blocker personally. Here's how to build a delivery system that scales your attention without losing visibility.
Read guideManaging Organisational Change in Programmes
Technology delivery without change management is just installing software nobody uses. Here's how Programme Managers ensure that people, processes, and culture change alongside the technology.
Read guideManaging Portfolio-Level Risk
Portfolio risk is not the sum of programme risks. It's the systemic threats that affect multiple investments simultaneously — market shifts, resource constraints, technology failures, and strategic misalignment.
Read guideManaging Programme-Level RAID
Project-level RAID logs track local risks. Programme-level RAID tracks systemic threats that span multiple projects and require coordinated response. Here's how to run it without duplicating what project managers already do.
Read guideManaging Project Scope Creep
Scope creep doesn't announce itself. It arrives as 'just one small addition' repeated fifty times until the project is unrecognisable from its original plan. Here's how to detect it early and manage it without becoming the person who always says no.
Read guideManaging Technical Debt in Scrum Teams
Technical debt silently eats velocity, increases defect rates, and burns out developers. Here's a practical framework for making debt visible, prioritising repayment, and preventing accumulation — without stopping feature delivery.
Read guideManaging Vendor Relationships in Agile Projects
Vendor contracts were designed for waterfall. Agile delivery needs flexibility. Here's how to structure vendor relationships that support iterative delivery without losing commercial control.
Read guideMeasuring and Improving Scrum Team Maturity
Team maturity isn't about how long you've been doing Scrum. It's about how effectively the team self-manages, delivers value, and continuously improves. Here's how to assess it honestly and grow deliberately.
Read guidePortfolio Governance Cadences and Forums
Portfolio governance connects investment decisions to delivery outcomes. Here's how to design forums that make decisions fast, surface problems early, and keep the portfolio aligned with strategy.
Read guidePortfolio Investment Decision-Making
Every portfolio decision is an investment decision — committing scarce resources to one initiative means not committing them to another. Here's how to make these decisions with rigour, transparency, and speed.
Read guidePortfolio Prioritisation Frameworks
When every initiative is 'top priority,' nothing is. Here's how to apply structured prioritisation frameworks — WSJF, weighted scoring, MoSCoW, and RICE — to make defensible investment decisions at portfolio level.
Read guidePortfolio Rationalisation and Sunset Decisions
A portfolio that only grows never improves. Rationalisation — stopping, consolidating, and sunsetting — is how you free capacity for higher-value work. Here's how to make these difficult decisions well.
Read guideProgramme Budget and Financial Governance
Programme budgets are larger, more complex, and more politically sensitive than project budgets. Here's how to manage multi-million pound programme finances with the rigour sponsors expect and the flexibility delivery needs.
Read guideProgramme Governance Frameworks That Scale
Programme governance is the structure that keeps strategy, execution, and accountability aligned across multiple projects. Too light and things drift. Too heavy and teams drown in process. Here's how to get the balance right.
Read guideProgramme Milestone Planning and Tracking
Milestones are the programme's heartbeat — they create accountability, enable governance, and give stakeholders confidence that delivery is progressing. Here's how to plan them realistically and track them honestly.
Read guideProgramme Reporting for Steering Committees
Steering committees have 60 minutes and limited patience. Your report needs to surface the signal, drive decisions, and build confidence — not demonstrate how busy you've been.
Read guideProject Budget Management and Forecasting
Budget management is not just tracking spend — it's forecasting where you'll land, communicating variances early, and making trade-off recommendations before the money runs out.
Read guideProject Closure and Lessons Learned
Most projects end with a whimper — the team disperses, the PM moves on, and nobody captures what was learned. Proper closure protects the organisation's investment and makes the next project better.
Read guideProject Risk Management — Beyond the RAID Log
A RAID log is necessary but not sufficient. Effective risk management requires proactive identification, quantified assessment, active mitigation, and a culture where raising risks is rewarded — not punished.
Read guideResource Planning and Allocation for Projects
Resource planning is where project ambition meets organisational reality. Here's how to secure the right people, manage competing demands, and deliver without burning out your team.
Read guideRisk Governance in Agile Delivery
Blend lightweight Agile rhythms with the governance discipline enterprise environments need.
Read guideRunning Effective Delivery Governance Cadences
Governance without cadence is chaos. Cadence without purpose is bureaucracy. Here's how to design governance rhythms that surface risk early, drive decisions fast, and keep delivery on track without drowning teams in meetings.
Read guideRunning High-Impact Retrospectives
How to move retrospectives from discussion to measurable team experiments and follow-through.
Read guideScaling Scrum — From One Team to Many
When one Scrum team becomes three, everything that worked before breaks. Dependencies multiply, integration gets harder, and coordination overhead explodes. Here's how to scale without losing agility.
Read guideScrum Master Anti-Patterns and How to Fix Them
The most dangerous Scrum Master anti-patterns look productive on the surface but quietly destroy the feedback loops Scrum depends on. Here's how to recognise and fix the twelve most common ones.
Read guideScrum Master's Guide to Jira Board Governance
A messy Jira board hides problems, misleads stakeholders, and makes every ceremony harder. Here's how to establish governance that keeps your board trustworthy without becoming a Jira police officer.
Read guideSprint Planning That Actually Works
Most sprint planning sessions are a PM presenting tickets while the team argues about estimates. Here's how to run planning that produces a clear, achievable commitment the whole team believes in.
Read guideStakeholder Communication Plans That Work
When an executive says 'I thought this was still on schedule' and the team says 'we flagged that two weeks ago,' the problem is communication — not delivery. Here's how to build a communication plan that prevents surprises.
Read guideStakeholder Engagement for Delivery Leads
Build trust through crisp updates, decision logs, expectation setting, and transparent trade-offs.
Read guideStrategic Alignment — Connecting Delivery to Strategy
If you can't draw a clear line from every active initiative to a strategic objective, you're spending money without purpose. Here's how to build and maintain strategic alignment across the portfolio.
Read guideVendor and Third-Party Governance in Programmes
When your programme depends on 3-5 vendors delivering simultaneously, governance becomes critical. Here's how to manage vendor performance, contracts, and relationships at programme scale without becoming a procurement department.
Read guide