Agile Development Metrics

Otavio Ferreira (@otaviofff) Technical Architect, Scrum Master

• Question

• Basic Agile Concepts

• Basic Agile Techniques

• Agile Planning

• Agile Tracking

When will this product be done?

• Question



• Agile Planning

• Agile Tracking

• Roles

– Product Owner: Owns the product

– Scrum Master: Owns the process

– Team: Owns the software, source-code

• Story

– Piece of software relevant to end users

– Functional requirement

– Template

• As an <actor>,

• I wan to <action>,

• So that I can <achievement>.

Story 1: As a community member, I want to have a user profile, so that I can present myself to the community.

• Story Points

– Estimated story complexity

– Measured in Fibonacci numbers

1 2 3 4 5 6 7 8 9 10

Complexity 0 1 2 3 5 8 13 20 40 100

0

20

40

60

80

100

120

• Sprint

– Development iteration

– Predefined time-box, typically 2 weeks

• Team Velocity

– Number of story points the team can deliver within one sprint

– Measured in points/sprint

– Stabilized over time

• Question



• Agile Planning

• Agile Tracking

• Story Writing Workshop

– Participants

• Product Owner

• Scrum Master

• Team

– Goal

• Populate the product backlog

• Write user stories as far as requirements visibility goes

• Story Estimation Workshop

– Participants

• Team

• Scrum Master

– Goal

• Estimate the complexity of stories

– How to run

• Consensus-based technique

• Planning poker

4.27 cm ---{ 5x }--- 21.35 cm

• Question



• Agile Planning

• Agile Tracking

• Product Planning

– Product Backlog

Story 1

Story 10

Story 9

Story 2

Story 3

Story 4

Story 5

Story 6

Story 7

Story 8

Points Priority

2

3

5

2

2

3

1

2

5

8

• Product Planning

– Product Plan

10

8

15

Product

Epic A

Story 1

Story 2

Story 3

Epic B

Story 4

Story 5

Story 6

Story 7

Epic C

Story 8

Story 9

Story 10

2

3

5

2

2

3

1

2

5

8

33

• Sprint Planning

– Sprint Backlog

8

Product

Sprint 1 Story 1

Story 2

Sprint 2 Story 3

Story 4

Sprint 3

Story 5

Story 6

Story 7

Sprint 4 Story 8

Story 9

Sprint 5 Story 10

2

3

5

2

2

3

1

2

5

8

5

7

7

6

Team Velocity 7 points/sprint

33

Sprint Backlog

• Sprint Planning

– Sprint Plan

Product

Sprint 1

Sprint 2

Sprint 3

Sprint 4

Sprint 5

Sprint Complexity Start date End date

1 5 02 June 15 June

2 7 16 June 29 June

3 5 30 June 13 July

4 7 14 July 27 July

5 8 28 July 10 August

5 33 02 June 10 August

10 weeks = 2.5 month project

• Release Planning

– Release Backlog

Product

Release 1

Story 1

Story 2

Story 3

Story 4

Story 5

Story 6

Story 7

Release 2

Story 8

Story 9

Story 10

2

3

5

2

2

3

1

2

5

8

33

Release Backlog

18

15

High Priority


– Release Plan

Product

Release 1

Release 2

Release Complexity Start date End date

1 18 02 June 13 July

2 15 14 June 10 June

2 33 02 June 10 August

1) 6 weeks = 1.5 month release 2) 4 weeks = 1.0 month release


– Release Plan (Hidden Complexity)

Release Scenario Buffer (%) Complexity Sprints Release date

1 Unfeasible 0 33 5 10 August

1 Optimistic 10 37 6 24 August

1 Realistic 20 40 7 07 September

1 Pessimistic 30 43 8 21 September

• Resulting Planning Tree

8

2

3

5

2

2

3

1

2

5

8

5

7

7

6

33

18

15

Product

Release 1

Sprint 1

Story 1

Story 2

Sprint 2

Story 3

Story 4

Sprint 3

Story 5

Story 6

Story 7

Release 2

Sprint 4

Story 8

Story 9

Sprint 5 Story 10

• Question



• Agile Planning

• Agile Tracking

• Sprint Tracking

– Sprint Completeness Chart

66%

24%

10%

Done

In Development

In Testing

• Sprint Tracking

– Sprint Burndown Chart

0 1 2 3 4 5 6 7 8 9

Ideal Burndown 6.0 5.3 4.7 4.0 3.3 2.7 2.0 1.3 0.7 0.0

Current Burndown 6 6 6 4 4 4 1 1 0 0

0.0

1.0

2.0

3.0

4.0

5.0

6.0

7.0

Story Points

Sprint Day

• Release Tracking

– Release Completeness Chart

37%

3%

60%

Done

In Progess

New


– Release Burndown Chart

1 2 3 4 5 6

Ideal Burndown 33.0 26.4 19.8 13.2 6.6 0.0

Current Burndown 33 30 23 16 8 0

0.0

5.0

10.0

15.0

20.0

25.0

30.0

35.0

Story Points

Sprint


– Release Burnup Chart

1 2 3 4 5

Points Burned 3 7 7 8 8

0

1

2

3

4

5

6

7

8

9

10

Story Points

Sprint

• Team Velocity Tracking

– Team Velocity Chart

0 1 2 3 4 5

Points Planned 0 5 9 8 8 8

Points Done 0 3 7 7 8 8

Tech Debit 0 2 2 1 0 0

0

5

9

8 8 8

0

3

7 7

8 8

0

2 2

1

0 0 0

1

2

3

4

5

6

7

8

9

10

Story Points

Sprint

Team Velocity 6 points/sprint

(stable)

• Question



• Agile Planning

• Agile Reporting

Agile Development Metrics Questions? Thank you!

Otavio Ferreira http://otaviofff.me http://twitter.com/otaviofff

http://otaviofff.me/

http://otaviofff.me/

http://twitter.com/otaviofff

Agile Development Metrics

Technology

Transcript of Agile Development Metrics