Agile Estimating. User Story As a buyer, I want to have my shipping information confirmed so I get a chance to correct any errors Estimate = 8 Points

Size: px

Start display at page:

Download "Agile Estimating. User Story As a buyer, I want to have my shipping information confirmed so I get a chance to correct any errors Estimate = 8 Points"

Adele Flowers
5 years ago
Views:

1 Agile Estimating User Story As a buyer, I want to have my shipping information confirmed so I get a chance to correct any errors Estimate = 8 Points 1

2 Agenda 2 levels of es>ma>ng precision What influences the size of a story? Planning releases Planning itera>ons Exercises 2

3 2 Levels of EsEmaEng Precision Story Points and Velocity for Planning Releases Task Hours and Capacity for Planning Itera>ons PRIORITIZED RELEASE BACKLOG Size in Story Points User Story A 8 User Story B 5 User Story C 2 User Story D 20 User Story E 40 ITERATION BACKLOG Size in Task Hours User Story A, Task 1 6 User Story A, Task 2 4 User Story A, Task 3 6 User Story A, Task 4 2 3

4 Agile Uses Points to EsEmate Story Size TradiEonal Size EsEmates Are Absolute <LINES.OF.CODE> <FUNCTION.POINTS> <DAYS.HOURS> Agile Size EsEmates Are RelaEve 1 Point 3 Points 8 Points 4

5 Why is a Rela%ve Size Measure BePer? Humans are good at comparing size, not very good at es>ma>ng absolute Can you tell the difference between a 1 and a 2? How about between a 33 and a 34? Rela>ve Size es>mates don t change Es>ma>ng is faster Easier to reach accurate consensus on size Basic math s>ll works = 6 5

6 ESTIMATE BY ANALOGY This story is like that story, so it s estimate is what that story s estimate was Rally So5ware Development, Inc. 6

7 What influences the size of a story? Effort Complexity Doubt Rally So5ware Development, Inc. 7

8 Complexit y Effort Doubt Complexity Effort User Story 1 Doubt Effort Complexity User Story 3 Doubt User Story 2 8

9 5 Complexity Effort Doubt User Story 1 Complexity 13 Doubt Effort 5 Effort Complexity Doubt User Story 3 User Story 2 9

10 Velocity vs. Capacity Velocity is the long- term measure of the amount of story points completed per itera>on Capacity is the amount of ideal hours available to work on a story s tasks Available Hours for Itera>on VISH JEFF MIKE LAKSHMI Velocity is used to es>mate what we can finish by the release date Capacity is used to es>mate what we can finish by the iteraeon deadline 10

11 What does this look like in release planning? Story Points and Velocity for Planning Releases PRIORITIZED RELEASE BACKLOG Size in Story Points User Story A 8 User Story B 5 User Story C 2 User Story D 20 User Story E 40 11

12 Fixed Date Release Planning Highest Priority Stories On Top Will Have Note: the business knows the most important stories will be delivered to aid planning release ac>vi>es At our Slowest Velocity, We ll Finish Here Might Have At our Fastest Velocity, We ll Finish Here Won t Have Adapted from Mike Cohn 12

13 Or, Fixed Scope Release Planning Total Story Points Desired 120 Fastest Velocity 24 Slowest Velocity points 24 points/itera>on = 120 points 20 points/itera>on = Time & Cost EsEmate Adapted from Mike Cohn 13

14 What does this look like in iteraeon planning? Task Hours and Capacity for Planning Iterations ITERATION BACKLOG Size in Task Hours User Story A, Task 1 6 User Story A, Task 2 4 User Story A, Task 3 6 User Story A, Task

15 Story One Task EsEmate Owner Code the UI 6 Mike Code the middle >er 8 Vish Create and automate tests 4 Lakshmi CAN WE COMMIT TO THIS? Ideal Hours Available in This Itera>on Available Commihed 15

16 Story Nine Task EsEmate Owner Code the UI 8 Jeff Code the middle >er Create and automate tests CAN WE COMMIT TO THIS? Ideal Hours Available in This Itera>on Available Commihed 6 Mike 3 Lakshmi 16

17 Next Steps Learn to es>mate Dura>on, Size and Velocity for Good Release & Itera>on Planning for the Agile Es>ma>ng Exercises Guide Check out these other Agile Planning topics: Release Planning Itera>on Planning 17

Vision, Roadmap, and Release Planning

Vision, Roadmap, and Release Planning Supplemental Materials for a Product Owner Jessica Komarek and Sara Alterisio 5 Levels of Agile Release Planning Vision Roadmap Release Iteration Daily What, Who,