In agile software development, the focus is on adapting to changing conditions or requirements and optimizing the process continuously. Adaptations and optimizations are driven by the development team itself. To be able to judge the course of an iteration reasonably, metrics are generally used. The main objective of this talk it to propose metrics and appropriate visualizations to answer questions of agile development teams. The metrics provide team members with better access to the metadata of their own work. This is intended to enable the team to better understand their own work and to adapt their processes meaningfully based on the information obtained.

1. RICHARD FICHTNER
@RichardFichtner
XDEV Software Corp.

2. RICHARD FICHTNER
@RichardFichtner
XDEV Software Corp.
about.me
▪15+ years full stack
▪my passion
▪ clean code
▪ agile stuff
@RichardFichtner

3. RICHARD FICHTNER
@RichardFichtner
XDEV Software Corp.

4. RICHARD FICHTNER
@RichardFichtner
XDEV Software Corp.
Agenda
▪Why do we need metrics for agile teams?
▪What agile teams want to know?
▪Where is the data coming from?
▪Metrics that helped us and how to build them

5. RICHARD FICHTNER
@RichardFichtner
XDEV Software Corp.
Why do we need
metrics
for agile teams?

6. RICHARD FICHTNER
@RichardFichtner
XDEV Software Corp.Das sind die Quellen

7. RICHARD FICHTNER
@RichardFichtner
XDEV Software Corp.
Principles behind the Agile Manifesto
“The best architectures, requirements, and designs
emerge from self-organizing teams.”
- Manifesto for Agile Software Development
http://agilemanifesto.org/principles.html

8. RICHARD FICHTNER
@RichardFichtner
XDEV Software Corp.
The Scrum Team
“Self-organizing teams choose how best to accomplish their
work, rather than being directed by others outside the team”
- The Scrum Guide™
http://www.scrumguides.org/scrum-guide.html

9. RICHARD FICHTNER
@RichardFichtner
XDEV Software Corp.

10. RICHARD FICHTNER
@RichardFichtner
XDEV Software Corp.
Making decisions
gather data -> generate insights -> decide what to do
Derby, Esther und Larsen, Diana. 2006. Agile Retrospectives: Making Good Teams Great. s.l. : O'Reilly UK Ltd., 2006. 978-0977616640

11. RICHARD FICHTNER
@RichardFichtner
XDEV Software Corp.
The agony of choice
„What is not measurable make measurable“
- Galileo Galilei (1564-1642)
1. Understand your own work (make it measurable)
2. Identify potential for improvement
3. take action
4. Measure changes

12. RICHARD FICHTNER
@RichardFichtner
XDEV Software Corp.
Metrics
„A metric is a recurring measurement that has informational,
diagnostic, motivational, or predictive power of some kind. It
helps you understand whether you’re at risk of missing
expected results, or whether changes in process or practices
are resulting in improved performance.“
- Nicolette, David
Nicolette, David. 2015. Software Development Metrics. Shelter Island : Manning, 2015. 978-1617291357 p. 2

13. RICHARD FICHTNER
@RichardFichtner
XDEV Software Corp.
What can metrics do?
▪Create understanding / insight
▪control function
▪Identify potential for improvement

14. RICHARD FICHTNER
@RichardFichtner
XDEV Software Corp.
Limitations of metrics
▪Metrics are NOT the reality!
▪Be pragmatic, please
▪ It is a contextual representation of reality
▪ A single metric can’t explain the whole world

15. RICHARD FICHTNER
@RichardFichtner
XDEV Software Corp.
Agile vs. Metrics
“Individuals and interactions over processes and tools”
“Customer collaboration over contract negotiation”
“Responding to change over following a plan”
- Manifesto for Agile Software Development
http://agilemanifesto.org/

16. RICHARD FICHTNER
@RichardFichtner
XDEV Software Corp.
What agile teams
want to know?

17. RICHARD FICHTNER
@RichardFichtner
XDEV Software Corp.
Questions of agile teams
▪ How many (Story Points) can we do in an iteration?
▪ How homogeneous is our team?
▪ How much time is invest in which tasks (types)?
▪ Who worked on which task types?
▪ About which tasks should we speak face-to-face?
▪ Why did they release the second and third matrix movie?

18. RICHARD FICHTNER
@RichardFichtner
XDEV Software Corp.
Where is the data
coming from?

19. RICHARD FICHTNER
@RichardFichtner
XDEV Software Corp.
Where is the data coming from?
▪Manuel capture
▪ Deliberate and unintentional manipulation
▪ Overhead for the development team
▪Automated capture
▪ Already takes place in many systems

20. RICHARD FICHTNER
@RichardFichtner
XDEV Software Corp.
Where is the data coming from?
Davies, Christopher W. H. 2015. Agile Metrics in Action: How to Measure and Improve Team Performance. Shelter Island : Manning, 2015. 978-1617292484 p. 8

21. RICHARD FICHTNER
@RichardFichtner
XDEV Software Corp.
Where is the data coming from?
Davies, Christopher W. H. 2015. Agile Metrics in Action: How to Measure and Improve Team Performance. Shelter Island : Manning, 2015. 978-1617292484 p. 8

22. RICHARD FICHTNER
@RichardFichtner
XDEV Software Corp.
Integration of the data
▪time
▪user
▪issue keys

23. RICHARD FICHTNER
@RichardFichtner
XDEV Software Corp.
Data protection and privacy
▪General Data Protection Regulation (GDPR)
▪Talk to your data protection person

24. RICHARD FICHTNER
@RichardFichtner
XDEV Software Corp.

25. RICHARD FICHTNER
@RichardFichtner
XDEV Software Corp.

26. RICHARD FICHTNER
@RichardFichtner
XDEV Software Corp.
Team Homogeneity (TH)
answered questions
▪How homogeneous is the team (for component x)?
▪Is it a team or several teams?
▪Who worked on which task types?
data sources
▪Project tracking tool
▪Version control system

27. RICHARD FICHTNER
@RichardFichtner
XDEV Software Corp.
Team Homogeneity (TH)
ComponentClassFileChange
Commit
[Date]
User

28. RICHARD FICHTNER
@RichardFichtner
XDEV Software Corp.
0%
20%
40%
60%
80%
100%
0%
10%
20%
30%
40%
50%
60%
70%
80%
90%
100%
t1 t2 t3 t4 t5 t6
Team Homogeneity
Alice Bob Claire TH

29. RICHARD FICHTNER
@RichardFichtner
XDEV Software Corp.
Team Time Commitment (TTC)
answered question
▪ How much time has been spent by the development team?
value
▪ Looking back: Recognizing disturbances of the team
▪ Looking ahead: better sprint capacity planning
data sources
▪ Project tracking tool

30. RICHARD FICHTNER
@RichardFichtner
XDEV Software Corp.
TTC vs Velocity
𝑃ower =
∆ 𝑊𝑜𝑟𝑘
∆ 𝑇𝑖𝑚𝑒
𝑉𝑒𝑙𝑜𝑐𝑖𝑡𝑦 =
𝑇𝑎𝑠𝑘𝑠 𝐶𝑜𝑚𝑝𝑙𝑒𝑡𝑒𝑑
𝑆𝑝𝑟𝑖𝑛𝑡 𝑇𝑖𝑚𝑒𝑓𝑟𝑎𝑚𝑒

31. RICHARD FICHTNER
@RichardFichtner
XDEV Software Corp.
Team Time Commitment (TTC)
0
50
100
150
200
250
300
350
400
Day 1 Day 2 Day 3 Day 4 Day 5 Day 6 Day 7 Day 8 Day 9 Day 10
Timeinhours
Burndown Chart (Completed Tasks)
Ideal Tasks Remaining Actual Tasks Remaining

32. RICHARD FICHTNER
@RichardFichtner
XDEV Software Corp.
Team Time Commitment (TTC)
-50
0
50
100
150
200
250
300
350
400
Day 1 Day 2 Day 3 Day 4 Day 5 Day 6 Day 7 Day 8 Day 9 Day 10
Timeinhours
Burndown Chart (Team Time Commitment)
Ideal Invested Time Actual Invested Time

33. RICHARD FICHTNER
@RichardFichtner
XDEV Software Corp.
Team Time Commitment (TTC)
-50
0
50
100
150
200
250
300
350
400
Day 1 Day 2 Day 3 Day 4 Day 5 Day 6 Day 7 Day 8 Day 9 Day 10
Timeinhours
Burndown Chart Vergleich
Ideal Tasks Remaining / Invested Time Actual Tasks Remaining Invested Time

34. RICHARD FICHTNER
@RichardFichtner
XDEV Software Corp.
Sprint Profile (SP)
Answered questions
▪ How much time did the team invest, in which types of tasks (features, bugs, hotfixes,
meetings) in the sprint?
value
▪ Looking Back: Sprints become comparable in the "task type" dimension
▪ Looking ahead: as a basis for forecasts of capacities per "task type"
data sources
▪ Project tracking tool

35. RICHARD FICHTNER
@RichardFichtner
XDEV Software Corp.
Sprint Profile (SP)
0
50
100
150
200
250
Features
Bugs
Hotfixes
Meetings
Comparison: Sprint Profile (h)
Sprint 1
Sprint 2

36. RICHARD FICHTNER
@RichardFichtner
XDEV Software Corp.
Comment Ping Pong (CPP)
answered question
▪ About which tasks should the team talk face-to-face?
value
▪ Shows where there is a high need for direct communication. This may
indicate a number of problems.
▪ Allows timely countermeasures to be taken
data sources
▪ Project tracking tool

37. RICHARD FICHTNER
@RichardFichtner
XDEV Software Corp.
Comment Ping Pong (CPP)
„Individuals and interactions over processes and tools”
„The most efficient and effective method of conveying
information to and within a development team is face-to-face
conversation.“
- Manifesto for Agile Software Development
http://agilemanifesto.org/principles.html

38. RICHARD FICHTNER
@RichardFichtner
XDEV Software Corp.
Comment Ping Pong (CPP)
0
0,5
1
1,5
2
2,5
3
3,5
4
4,5
14:00 14:15 14:30 14:45 15:00 15:15 15:30 15:45 16:00 16:15 16:30
Comment Ping Pong
Comments CPP Threshold

39. RICHARD FICHTNER
@RichardFichtner
XDEV Software Corp.
Pull Request Size (PRS)
Answered question
▪ How extensive are the code changes that should be checked by a pull
request?
value
▪ Can increase the motivation to review pull request and their quality
▪ Can help to improve lead time
data sources
▪ Version control system

40. RICHARD FICHTNER
@RichardFichtner
XDEV Software Corp.
Pull Request Size (PRS)
0
2
4
6
8
10
12
14
16
18
20
PR 1 PR 2 PR 3 PR 4 PR 5 PR 6 PR 7 PR 8
changed files per pull request
changed files Baseline

41. RICHARD FICHTNER
@RichardFichtner
XDEV Software Corp.
Stuck Work (SW)
Answered question
▪ Which un-shipped tasks where worked on but abandoned?
value
▪ Helps to identify capital tieup
▪ Helps reduce "Muda“ (wastefulness)
data sources
▪ Version control system, Project tracking tool, Continuous integration

42. RICHARD FICHTNER
@RichardFichtner
XDEV Software Corp.
Stuck Work (SW)
variable description
A Task that has already been worked on and whose changes have not yet been shipped.
tA Duration between the first work on this task and now (= time of the query) in days
laA Duration between the last work on the task and now (= time of the query) in days
WA invested work in person days
SWA = (tA + laA) * wA

43. RICHARD FICHTNER
@RichardFichtner
XDEV Software Corp.
Stuck Work (SW)
250 270 290 310 330 350 370 390 410
A3
A4
A5
A1
A2
Stuck Work

44. RICHARD FICHTNER
@RichardFichtner
XDEV Software Corp.
Summary
▪The data is already there
▪A look at the data is worthwhile
▪The discussion about the metrics is the true value
inspect and adapt

45. RICHARD FICHTNER
@RichardFichtner
XDEV Software Corp.
Interesting links / books
▪Davies, Christopher W. H. 2015. Agile Metrics in Action: How to
Measure and Improve Team Performance
▪Fenton, Norman and Bieman, James. 2014. Software Metrics: A
Rigorous and Practical Approach
▪Nicolette, David. 2015. Software Development Metrics
▪https://jqassistant.org/shadows-of-the-past-analysis-of-git-
repositories/ Dirk Mahler 2017

46. RICHARD FICHTNER
@RichardFichtner
XDEV Software Corp.
Q & A

47. RICHARD FICHTNER
@RichardFichtner
XDEV Software Corp.
Find me and chat with me!

48. RICHARD FICHTNER
@RichardFichtner
XDEV Software Corp.
picture credits
All pictures in this presentation originate from pixabay.
This is a human-readable summary of the Pixabay License (read the full text).
You can use all images and videos published on Pixabay for free (except as set out below). You may
use them for commercial and non-commercial purposes, in altered and unaltered form. You don't
need to ask permission from or provide credit to the image author or Pixabay, although it is
appreciated when possible.
Das sind die Quellen