← Back to the exam

Free study guide

Enterprise Agile Coach — Free Curriculum

This free curriculum covers every domain assessed in the Oxford Certified Enterprise Agile Coach examination: coaching stances and skills, teams, facilitation, Scrum and Kanban, scaling frameworks, organisational design, leadership, change, strategy and portfolio, metrics, technical agility, finance and coaching ethics. Read each chapter, note the key points, and then sit the 100-question examination.

Ready? Take the free exam 125 min · 100 questions
Chapter 1

The agile coach's stances

An enterprise agile coach works with individuals, teams, leaders and the whole organisation. Effective coaches move deliberately between stances. Teaching transfers knowledge when people lack it; mentoring shares the coach's own experience and advice; professional coaching uses powerful questions so people find their own answers; facilitating guides a group's process while the group owns the content; and, occasionally, the coach offers expert advice.

Choosing the stance depends on the situation: a team new to Kanban needs teaching, a new Scrum Master asking "how did you handle this?" benefits from mentoring, and a leader exploring options benefits from coaching. The coach's goal is to build capability so the organisation can sustain improvement without them — the "exit strategy".

  • Teaching, mentoring, coaching, facilitating, advising
  • Choose the stance deliberately based on need
  • Build capability, not dependency
  • Plan an exit strategy from the start
Key takeaway: The right stance at the right moment is the core skill of an agile coach.
Chapter 2

Coaching skills and ethics

Powerful open questions ("What would need to be true for this to work?") create insight; leading or blaming questions do not. Deep, global listening notices tone, energy, body language and what is left unsaid. The GROW model structures conversations: Goal, Reality, Options, Way forward.

Coaching starts with contracting: agreeing goals, boundaries, roles and confidentiality. When a sponsor asks for private information about individuals, the coach clarifies the agreement and shares patterns and themes rather than personal confidences. Ethical coaches act in the client's best interest with honesty and respect for autonomy, do not promise guaranteed results, avoid pushing one framework everywhere and give credit to the teams.

  • Ask open, curious questions
  • Listen at a deep, global level
  • Use GROW to structure conversations
  • Contract clearly, including confidentiality
  • Honesty, respect for autonomy, no one-size-fits-all
Key takeaway: Trust is the coach's most important asset — protect it through clear agreements.
Chapter 3

Teams, trust and psychological safety

Tuckman's stages — forming, storming, norming, performing — describe team development. Forming teams need clear purpose and structure; storming involves conflict as roles are tested. Amy Edmondson defines psychological safety as a shared belief that the team is safe for interpersonal risk-taking. Leaders build it by admitting mistakes, framing work as learning and responding to bad news with curiosity.

Lencioni's Five Dysfunctions of a Team start with absence of trust, which leads to fear of conflict (artificial harmony), lack of commitment, avoidance of accountability and inattention to results. High-performing teams have healthy, constructive conflict. Working agreements make norms explicit, and the Agile Fluency Model describes zones of team capability — focusing, delivering, optimising and strengthening.

  • Forming → storming → norming → performing
  • Psychological safety enables learning and speaking up
  • Trust is the foundation; healthy conflict is essential
  • Make team norms explicit
  • Teams grow through fluency zones with different investments
Key takeaway: Safe teams surface problems early — and early problems are cheap to fix.
Chapter 4

Facilitation

Facilitators manage process so groups can focus on content and decisions. Timeboxes create focus; techniques such as fist of five check agreement quickly. Liberating Structures such as 1-2-4-All — silent reflection, then pairs, then fours, then the whole group — include quieter voices that dominant participants might otherwise drown out.

Retrospectives should vary formats, use data and lead to a small number of owned improvement actions. Root-cause tools such as the 5 Whys explore cause and effect rather than blaming individuals.

  • Neutral on content, active on process
  • Timebox activities
  • Use inclusive structures like 1-2-4-All
  • Quick decision checks such as fist of five
  • Retrospectives end with owned actions
Key takeaway: Great facilitation makes it easy for everyone to contribute their best thinking.
Chapter 5

Scrum mastery at enterprise level

In the Scrum Guide, the Scrum Master is accountable for the Scrum Team's effectiveness, the Product Owner for maximising value and the Developers for creating a usable Increment. Each artifact has a commitment: the Product Goal for the Product Backlog, the Sprint Goal for the Sprint Backlog and the Definition of Done for the Increment. Teams working on the same product share one Definition of Done so their work integrates.

Common anti-patterns include Product Owners without real decision authority, Daily Scrums turned into status reports, Sprint Reviews that are slide shows instead of hands-on inspection of the product, and "zombie Scrum" — events performed mechanically without valuable increments. Spikes are timeboxed investigations that reduce uncertainty.

  • Accountabilities: Scrum Master, Product Owner, Developers
  • Commitments: Product Goal, Sprint Goal, Definition of Done
  • Empower Product Owners with real decision rights
  • Make Reviews interactive and outcome-focused
  • Watch for zombie Scrum and status-meeting Daily Scrums
Key takeaway: Scrum works when its roles have real authority and its events create real learning.
Chapter 6

Kanban and flow

Kanban improves flow by visualising work, limiting WIP, managing flow, making policies explicit, implementing feedback loops and improving collaboratively. Little's Law states that average lead time equals average WIP divided by average throughput, so at constant throughput lower WIP shortens lead times.

Cumulative flow diagrams show work in each state over time and reveal bottlenecks. Throughput counts items finished per time unit. Service Level Expectations forecast delivery times, for example "85% of items finish within 8 days". Classes of service and explicit expedite policies prevent urgent work from destroying predictability. Monte Carlo simulation uses historical throughput to produce probabilistic forecasts with confidence ranges.

  • Little's Law: lead time = WIP ÷ throughput
  • Use CFDs to see bottlenecks
  • Set SLEs from real data
  • Make classes of service and expedite policies explicit
  • Forecast probabilistically with Monte Carlo
Key takeaway: Stop starting, start finishing — flow beats busyness.
Chapter 7

Scaling agile

Scaling frameworks align many teams to a shared goal. In SAFe, an Agile Release Train is a long-lived team of agile teams; PI Planning aligns them on objectives, dependencies and risks; the Release Train Engineer facilitates and coaches. Large-Scale Scrum (LeSS) uses one Product Owner and one Product Backlog for many teams with minimal extra roles. In Nexus, the Nexus Integration Team ensures an integrated Increment every Sprint.

All approaches share principles: align to a shared product goal, manage dependencies visibly, integrate frequently and keep coordination light. Scaling never replaces strong team-level practices. Transformations succeed when they start from business outcomes and value streams, pilot and adapt — not when frameworks are "installed" everywhere at once. Good large-scale planning starts with clear context, lets teams plan their own work and ends with a confidence vote. Communities of practice spread knowledge across teams.

  • SAFe: ART, PI Planning, RTE
  • LeSS: one PO, one backlog, minimal roles
  • Nexus: integration team, integrated increment
  • Pilot, learn and adapt — do not big-bang
  • Communities of practice spread learning
Key takeaway: Scale agility, not bureaucracy.
Chapter 8

Organisational design and Team Topologies

Conway's Law observes that systems mirror the communication structures of the organisations that build them; the inverse Conway manoeuvre shapes teams to encourage the desired architecture. Team Topologies defines four team types: stream-aligned teams aligned to a flow of value, platform teams providing internal services, enabling teams that build capabilities in other teams and step back, and complicated-subsystem teams for specialist areas. Team cognitive load is a key design constraint.

Cross-functional feature teams aligned to value streams reduce hand-offs compared with component teams. When features require work from many component teams with separate backlogs, reorganising around value streams usually speeds delivery more than adding coordination.

  • Conway's Law and the inverse Conway manoeuvre
  • Stream-aligned, platform, enabling, complicated-subsystem teams
  • Design for manageable cognitive load
  • Long-lived, cross-functional teams aligned to value
Key takeaway: Structure shapes flow — design teams around the value they deliver.
Chapter 9

Agile leadership and complexity

Agile organisations need servant and adaptive leaders who set direction, communicate intent and create conditions for self-organisation, rather than assigning daily tasks. Leader-leader models push decisions to those with the information, supported by clarity and competence. Self-managing teams still need clear boundaries and direction.

The Cynefin framework helps choose approaches: clear situations use best practice; complicated ones need expert analysis; complex ones need probe-sense-respond through safe-to-fail experiments; chaotic ones need immediate action to stabilise. Systems thinking looks at structures and interactions rather than blaming individuals, and transparent visualisation of strategy and portfolio connects leadership intent with team work.

  • Servant, adaptive leadership with clear intent
  • Push authority to information
  • Cynefin: clear, complicated, complex, chaotic
  • Systems thinking over individual blame
  • Make strategy visible
Key takeaway: Leaders create the environment in which agility succeeds or fails.
Chapter 10

Leading change

Kotter's eight steps begin with creating urgency, then building a guiding coalition, forming a vision, enlisting others, removing barriers, generating short-term wins, sustaining acceleration and anchoring change in culture. ADKAR focuses on individuals: Awareness, Desire, Knowledge, Ability and Reinforcement. When incentives still reward individual heroics, reinforcement is missing and old habits return.

Resistance usually signals legitimate concerns; explore it with curiosity. Agile transformations should themselves be iterative and evidence-based, measured by outcomes rather than the number of people trained or certified. Maturity assessments help teams reflect and choose improvements — they should not be used to rank or punish teams.

  • Kotter: urgency first, then a guiding coalition
  • ADKAR: awareness, desire, knowledge, ability, reinforcement
  • Align incentives with desired behaviours
  • Treat resistance as information
  • Transform iteratively and measure outcomes
Key takeaway: Change sticks when people understand it, want it, can do it and are rewarded for it.
Chapter 11

Strategy, OKRs and portfolio

OKRs combine an inspiring Objective with a few measurable Key Results that describe outcomes ("increase weekly active customers from 20,000 to 30,000"), not activities. Tying OKRs directly to individual bonuses encourages sandbagging and gaming.

Cost of Delay expresses the economic impact of waiting. Weighted Shortest Job First divides Cost of Delay by job size, so smaller jobs with equal value go first. Lean Portfolio Management funds long-lived value streams within guardrails rather than approving every project in detail. MVPs test key hypotheses to decide whether to pivot or persevere. Beyond Budgeting replaces rigid annual budgets with rolling, decentralised resource allocation, and agile contracts share risk while allowing scope to evolve.

  • Objectives inspire; key results measure outcomes
  • Do not link OKRs directly to bonuses
  • WSJF = Cost of Delay ÷ job size
  • Fund value streams, not projects
  • Rolling budgets and collaborative contracts
Key takeaway: Prioritise by economics and outcomes, not by who shouts loudest.
Chapter 12

Metrics, anti-patterns and technical agility

Measure flow (flow time, velocity, load, efficiency) and outcomes (customer and employee satisfaction, business results). Velocity is relative and team-specific; comparing or ranking teams by it causes estimate inflation. Watermelon reporting — green outside, red inside — signals low transparency. Probabilistic forecasts with confidence ranges are more honest than fixed-date promises under uncertainty.

Technical agility enables business agility. DORA metrics — deployment frequency, lead time for changes, change failure rate and time to restore service — measure delivery performance. Continuous integration, trunk-based development, test automation and continuous delivery keep software releasable at any time; long manual regression cycles are a key constraint to remove.

  • Flow and outcome metrics, not output rankings
  • Never compare velocity across teams
  • Beware watermelon reporting
  • DORA metrics for delivery performance
  • Automate testing and integrate continuously
Key takeaway: What you measure shapes behaviour — measure learning and value.

Ready? Take the free exam

Take the exam and earn your digital badge free of charge. After passing, you may order the official certificate.

Start free exam