AgileKoc
EN

Intermediate applied learning path

Measure value and flow for better Agile decisions

Read WIP, throughput, cycle time, and work item age as system signals—not individual targets. Use them with value, quality, and team-health evidence in Scrum, Kanban, and other Agile ways of working.

  • 3 applied PracticeLabs
  • Intermediate
  • ~83 min
  • 7 steps
  • Verifiable credential

Who this is for

  • • Product and delivery teams
  • • Operations teams
  • • Managers and transformation roles

What you'll be able to do

  • • Distinguish measuring for decisions from measuring for judgment
  • • Read WIP, throughput, cycle time, and work item age correctly to diagnose degrading flow
  • • Build an honest, data-based probability statement instead of a fixed date promise
  • • Diagnose how a metric is being gamed and propose a balanced, non-blaming alternative

Not Kanban-only

Flow metrics work in Scrum too

These measures come from flow thinking, but they do not require a Kanban framework. A Scrum Team can use them in Daily Scrum, Sprint Planning, Sprint Review, and Retrospective to inspect flow and improve forecasts.

WIP
How many work items have started but are not finished?
Throughput
How many work items finish in a given period?
Cycle time
How long does a finished item take from start to finish?
Work item age
How long has an unfinished item been in progress?

How it works

Learn what each signal means, diagnose a realistic dataset, and turn the evidence into a safer decision.

  1. 01

    Build a balanced view

    Connect flow signals with value, quality, and team health so a local improvement does not hide a system problem.

  2. 02

    Practise three decisions

    Diagnose degraded flow, set an evidence-based service-level expectation, and detect metric gaming. Each PracticeLab unlocks for 50 🪙.

  3. 03

    Earn the applied credential

    Complete every lesson and earn at least 3 stars in each PracticeLab without assistance. There is no separate final quiz.

AgileKoc achievement credential

Make evidence-based measurement verifiable

Complete all 7 required steps and earn at least 3 stars in every PracticeLab without assistance to receive a shareable, publicly verifiable AgileKoc applied-practice credential. It is not an accredited certification.

7 required steps
Path curriculum7 steps · ~83 minView all +
  1. Measuring for Decisions, Not JudgmentLearn that a metric should change a decision, then build a balanced view that watches value, flow, quality, and team health together.
  2. Flow Metrics Fundamentals: WIP, Throughput, Cycle TimeNumbers aren't comparable without a shared definition of the work — learn the four core flow metrics and what each one tells you.
  3. PracticeLab: Flow Dataset DiagnosisPracticeLab50 🪙Move from degrading flow metrics to a non-blaming system hypothesis and a reversible experiment — get AI rubric feedback.
  4. Service Level Expectations: A Forecast, Not a PromiseLearn to build an honest, data-based probability statement instead of a fixed date promise, and why less WIP speeds up flow.
  5. PracticeLab: Service Level ExpectationPracticeLab50 🪙Build an honest probability statement for a stakeholder under pressure, instead of a fixed date promise — get AI rubric feedback.
  6. Metric Traps and Team HealthLearn why a speed signal is unreliable without quality and team-health signals, and spot common traps like turning velocity into a target.
  7. PracticeLab: Metric Gaming DiagnosisPracticeLab50 🪙Diagnose how a metric is being gamed and propose a balanced, non-blaming alternative — get AI rubric feedback.

Applied practice credential

Complete every required lesson and earn at least 3 stars on each PracticeLab without assistance (0/7). Your credential is issued automatically; there is no separate quiz.

Before you start

Short answers about access, time, assessment, and the AgileKoc credential.

Are flow metrics only for Kanban teams?
No. They describe how work moves through a system. Scrum Teams can use the same evidence alongside Sprint Goals and product outcomes to inspect progress, risk, and predictability.
Does this course teach Agile measurement or only flow metrics?
It teaches an Agile measurement approach anchored in flow. You connect flow data with value, quality, and team-health signals instead of treating a single number as success.
Why is velocity not the main metric?
Velocity is a team-specific planning aid, not a cross-team performance target. Turning it into a target encourages gaming and can hide quality or value problems.
How much does the path cost?
All lessons are free. The 3 PracticeLabs cost 50 🪙 each to unlock.
How do I earn the credential?
Complete every required lesson and score at least 3 stars in every PracticeLab without assistance. The credential is issued automatically.

Cookie policy

See privacy policy