Intro into Agile Metrics. Learn about basic Agile, Scrum and Kanban Metrics, such as Velocity, Burndown chart, Team Hapinness and others.

1. Agile Metrics, 101
by Andrii Brylov, SPC4, CSM, CSPO

2. You can’t manage, what you can’t measure.
Peter Drucker
At regular intervals, the team reflects on
how to become more effective, then
tunes and adjusts its behavior
accordingly.
Agile Manifesto, Principle #12

3. How to
measure?
Tell me how you measure me, and I
will tell you how I will behave.
E. Goldratt

4. How to measure?
Meaningful Metrics
● Ignore Vanity Metrics.
● Focus on a trend, not
a raw number.
● Measure during long
intervals.
● Metrics are not for
management.
KISS
● Measure the simplest
thing that might help.
Don’t measure for sake of
measurement.
Record Context
● Data without context
is noise.
● Understand your
numbers - there is a
story behind every
number.

5. Measure metrics, that if
gamed, would improve
the overall result.

6. What to
measure?

7. Domains
Agile (ScrumKanban)
Focus on the process
Focus on the team, rather than individual
eXtreme Programming ● Focus on technical implementation
Product Metrics ● Focus on product and customer interactions

8. Scrum - Velocity
What?
How much work (in story points) team can
finish within a Sprint.
Why?
● Protects the team during planning.
● Improves predictability & forecasting.
● Without velocity release planning is
impossible.
How?
● All Stories are sized in story points
before team starts working on them.
● Definition of Ready and Definition of
Done are enforced.
● Calculate total of story points finished
vs committed.
● For forecasting use average from last 3-
4 sprints.
● Measure your trend - it should

10. Scrum - Sprint Burndown
What?
Measure progress during Sprint by
measuring remaining work (in hours and
story points).
Why?
● Makes progress visible.
● Identifies “stuck” stories.
How?
● Estimate all stories in story points, task
them out, estimate tasks in hours.
● Team members report remaining work
in hours at the standup.
● Track total of remaining work every
day.
● Look for antipatterns

11. Burndown Antipatterns

12. ScrumKanban - Work In Progress
What?
● How many work items are in progress
(in qa, code review, PO review) at the
same moment.
Why?
● Minimize context switching.
● Stop starting, start finishing.
How?
● Define your WIP Limit for the team,
for every work state, and for every
team member.
● Track how many of work items are in
progress (in qa, code review, PO
review) at every moment for every
member and the whole team.
● Intervene.

13. ScrumKanban - Team HappinessMorale
What?
Measure how team members feel about
every Sprint.
What?
Happy people are more productive.
How?
● Ask your team members to draw a
smile and post it on the wall during
retrospective.
● Understand the story behind their
choice.
● Keep track of the happinessmorale.

15. ScrumKanban - Experiments run
What?
Track your experiments and how they
impacted your teamprocess.
Why?
● Relentless improvement is impossible
without experimentation
How?
● Track information about experiments
you run in a common place (board,
excel file).
● Agree upon time and expected
outcome.
● Measure impactchange.

16. Q&A