2. Content
• Goal of agile
• Goal of metrics
• Data & measurement
• Indicators
• Calibration
• Scope
Monday, October 21, 13
3. Goal of agile
• Always build the potentially shipable
product increment.
• Always build high quality product.
• According to customer time-to-market.
• Working with people (not resources) in the
happy context company.
Monday, October 21, 13
4. Goal of metrics
• Be predictable to estimate and develop
software with a good rate of ROI for my
company.
Monday, October 21, 13
5. Data &
measurements
• Data:
• Story Points
• Sprint Timebox
• Hours per devs
• Basic measurements:
• Capacity
• Velocity
Monday, October 21, 13
6. Capacity:
• ideal_hours * sprint_timebox * devs_of_
team
• Ex: 7.5 hs * 10 days * 5 devs = 375 hs
Monday, October 21, 13
7. Real capacity:
• Capacity - (Holidays - study days - breaks
or interruption - others)
• Ex: 375 hs - (1 dev * 3 days) = 352,5 hs
Monday, October 21, 13
8. Velocity of sprint:
• (total_accepted_story_points / capacity)
real_capacity
• Ex: (36 / 375) 352,5 = 33,84 story points
Monday, October 21, 13
9. Velocity Chart
Story point accepted
40
30
20
36
33
28
25
30
10
0
Sprint 6
Monday, October 21, 13
Sprint 7
Sprint 8
Sprint 9
Sprint 10
10. Team Velocity:
• Velocity average of the last five sprints:
• Ex: (25 + 33 + 28 + 30 + 36) / 5 = 30,4
story points
Monday, October 21, 13
11. Indicators
• % of stories accepted
• % of stories rejected
• % of stories adding at the middle of sprint
• % of defect stories
• % of bugs under staging or production
Monday, October 21, 13
12. Calibration
• When? Retrospective meeting time.
• Who? The Team and Scrum Master.
• How? Reflexion about measurements and
indicators and take at least one item
calibration in the action plan.
Monday, October 21, 13
13. Scope
• Time scope:
• Sprint
• Project
• General scope:
• Team
• Customer
• Company
Monday, October 21, 13