Otavio Ferreira (@otaviofff)Technical Architect, Scrum Master
•   Question•   Basic Agile Concepts•   Basic Agile Techniques•   Agile Planning•   Agile Tracking
When will thisproduct be done?
•   Question•   Basic Agile Concepts•   Basic Agile Techniques•   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 ...
• Story Points  – Estimated story complexity  – Measured in Fibonacci numbers           120           100             80  ...
• 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  – Stabil...
•   Question•   Basic Agile Concepts•   Basic Agile Techniques•   Agile Planning•   Agile Tracking
• Story Writing Workshop  – Participants     • Product Owner     • Scrum Master     • Team  – Goal     • Populate the prod...
• Story Estimation Workshop  – Participants     • Team     • Scrum Master  – Goal     • Estimate the complexity of stories...
•   Question•   Basic Agile Concepts•   Basic Agile Techniques•   Agile Planning•   Agile Tracking
• Product Planning  – Product Backlog                 Priority              Points                            Story 1     ...
• Product Planning  – Product Plan                              10      Story 1   2                             Epic A   S...
• Sprint Planning  – Sprint Backlog                                      5                                               S...
• Sprint Planning     – Sprint Plan           Sprint 1   Sprint   Complexity   Start date     End date           Sprint 2 ...
• Release Planning  – Release Backlog                                    Story 1    2                                    S...
• Release Planning     – Release Plan                      Release   Complexity    Start date      End date          Relea...
• Release Planning      – Release Plan (Hidden Complexity)Release    Scenario      Buffer (%)   Complexity   Sprints   Rel...
• Resulting Planning Tree                                       5                                                Story 1  ...
•   Question•   Basic Agile Concepts•   Basic Agile Techniques•   Agile Planning•   Agile Tracking
• Sprint Tracking  – Sprint Completeness Chart              10%        24%                       Done                     ...
• Sprint Tracking  – Sprint Burndown Chart                       7.0                       6.0                       5.0  ...
• Release Tracking  – Release Completeness Chart                                37%                                      D...
• Release Tracking  – Release Burndown Chart                        35.0                        30.0                      ...
• Release Tracking  – Release Burnup Chart                    10                     9                     8              ...
Team Velocity• Team Velocity Tracking                              6 points/sprint                                        ...
•   Question•   Basic Agile Concepts•   Basic Agile Techniques•   Agile Planning•   Agile Reporting    Otavio Ferreira    ...
Upcoming SlideShare
Loading in...5
×

Agile Development Metrics

2,482

Published on

Learn how to answer the most recurrent question in the software development industry: When will this product be done?

0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
2,482
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
79
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Agile Development Metrics

  1. 1. Otavio Ferreira (@otaviofff)Technical Architect, Scrum Master
  2. 2. • Question• Basic Agile Concepts• Basic Agile Techniques• Agile Planning• Agile Tracking
  3. 3. When will thisproduct be done?
  4. 4. • Question• Basic Agile Concepts• Basic Agile Techniques• Agile Planning• Agile Tracking
  5. 5. • Roles – Product Owner: Owns the product – Scrum Master: Owns the process – Team: Owns the software, source-code
  6. 6. • 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.
  7. 7. • Story Points – Estimated story complexity – Measured in Fibonacci numbers 120 100 80 60 40 20 0 1 2 3 4 5 6 7 8 9 10 Complexity 0 1 2 3 5 8 13 20 40 100
  8. 8. • Sprint – Development iteration – Predefined time-box, typically 2 weeks
  9. 9. • Team Velocity – Number of story points the team can deliver within one sprint – Measured in points/sprint – Stabilized over time
  10. 10. • Question• Basic Agile Concepts• Basic Agile Techniques• Agile Planning• Agile Tracking
  11. 11. • Story Writing Workshop – Participants • Product Owner • Scrum Master • Team – Goal • Populate the product backlog • Write user stories as far as requirements visibility goes
  12. 12. • 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
  13. 13. • Question• Basic Agile Concepts• Basic Agile Techniques• Agile Planning• Agile Tracking
  14. 14. • Product Planning – Product Backlog Priority Points Story 1 2 Story 2 3 Story 3 5 Story 4 2 Story 5 2 Story 6 3 Story 7 1 Story 8 2 Story 9 5 Story 10 8
  15. 15. • Product Planning – Product Plan 10 Story 1 2 Epic A Story 2 3 Story 3 5 Story 4 2 8 Story 5 2 33 Product Epic B Story 6 3 Story 7 1 15 Story 8 2 Epic C Story 9 5 Story 10 8
  16. 16. • Sprint Planning – Sprint Backlog 5 Story 1 2 Sprint 1 Sprint Backlog Story 2 3 Team Velocity 7 7 points/sprint Story 3 5 Sprint 2 Story 4 2 6 Story 5 2 33 Product Sprint 3 Story 6 3 Story 7 1 7 Story 8 2 Sprint 4 Story 9 5 8 Sprint 5 Story 10 8
  17. 17. • Sprint Planning – Sprint Plan Sprint 1 Sprint Complexity Start date End date Sprint 2 1 5 02 June 15 June 2 7 16 June 29 JuneProduct Sprint 3 3 5 30 June 13 July 4 7 14 July 27 July Sprint 4 5 8 28 July 10 August Sprint 5 5 33 02 June 10 August 10 weeks = 2.5 month project
  18. 18. • Release Planning – Release Backlog Story 1 2 Story 2 3 High Priority 18 Story 3 5 Release 1 Story 4 2 Release Backlog Story 5 2 Story 6 3 33 Product Story 7 1 15 Story 8 2 Release 2 Story 9 5 Story 10 8
  19. 19. • Release Planning – Release Plan Release Complexity Start date End date Release 1Product 1 18 02 June 13 July Release 2 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
  20. 20. • Release Planning – Release Plan (Hidden Complexity)Release Scenario Buffer (%) Complexity Sprints Release date1 Unfeasible 0 33 5 10 August1 Optimistic 10 37 6 24 August1 Realistic 20 40 7 07 September1 Pessimistic 30 43 8 21 September
  21. 21. • Resulting Planning Tree 5 Story 1 2 Sprint 1 Story 2 3 7 18 Story 3 5 Sprint 2 Release 1 Story 4 2 6 Story 5 2 Sprint 3 Story 6 3 33 Product Story 7 1 7 Story 8 2 15 Sprint 4 Story 9 5 Release 2 8 Sprint 5 Story 10 8
  22. 22. • Question• Basic Agile Concepts• Basic Agile Techniques• Agile Planning• Agile Tracking
  23. 23. • Sprint Tracking – Sprint Completeness Chart 10% 24% Done In Development In Testing 66%
  24. 24. • Sprint Tracking – Sprint Burndown Chart 7.0 6.0 5.0 4.0 Story Points 3.0 2.0 1.0 0.0 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 Sprint Day
  25. 25. • Release Tracking – Release Completeness Chart 37% Done In Progess New 60% 3%
  26. 26. • Release Tracking – Release Burndown Chart 35.0 30.0 25.0 20.0 Story Points 15.0 10.0 5.0 0.0 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 Sprint
  27. 27. • Release Tracking – Release Burnup Chart 10 9 8 7 6 Story Points 5 4 3 2 1 0 1 2 3 4 5 Points Burned 3 7 7 8 8 Sprint
  28. 28. Team Velocity• Team Velocity Tracking 6 points/sprint (stable) – Team Velocity Chart 10 9 9 8 8 8 8 7 7 7 6 5 Story Points 5 4 3 3 2 2 2 1 1 0 0 0 0 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 Sprint
  29. 29. • Question• Basic Agile Concepts• Basic Agile Techniques• Agile Planning• Agile Reporting Otavio Ferreira Agile Development Metrics http://otaviofff.me Questions? http://twitter.com/otaviofff Thank you!
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×