STORY POINTING Ragini Eguvolla, PMP, ITIL V3, 6σ GB

WHAT IS A USER STORY?• Description about what the customer wants • Provides an alternative vision for managing the

requirements of the software• It should be written based on the client perspective

BENEFITS OF USER STORIES• Writing User stories

increases the collaboration between the team members

• Helps to determine the timeline and efforts of each iteration

• Avoids miscommunication

USER STORY FORMAT

User – Roles for which the story is written forAction – This is the task that user should be able to performPurpose – This is the goal or result that is achieved from the action

ACCEPTANCE CRITERIA• Every story should include

the requirements, that determines how the team is going to develop and test the story

• The done criteria can be changed during the iteration based on the effort changed per story

• The story can be treated as completed only when the team accomplish the done criteria

ESTIMATING THE USER STORIES

T-SHIRT SIZING

Extra SmallSmallMediumLarge Extra Large

PLANNING POKER ESTIMATION

Estimates based on the “bigness” of a story. Influenced by• How hard the story is• How much of it there is

STORY POINTS

“In a good shoe, I wear a size six,but a seven feels so good, I buy a size eight.”–Dolly Parton in Steel Magnolias

STORY POINTS SIZE

Effort Uncertainty Complexity

STORY POINTS ARE RELATIVE

• Story point is a arbitrary measure used by Scrum teams. This is used to measure the effort required to implement a story and the complexity, uncertainty involved

• Estimation is just that: an estimate. Not a blood-oath

STORY POINTS

STORY POINTS

STORY POINTS AND TIME ESTIMATES

Remember the Mantra Points for Stories ; Hours for Tasks

VELOCITY• Velocity is a measure of the amount of work a

Team can tackle during a single Sprint and is the key metric in Scrum

• It is calculated by summing the number of story points assigned to each user story that the team completed during the iteration

VELOCITYIteration

Committed Completed

Iteration 1 15 10

Iteration 2 15 20

Iteration 3 10 10

Iteration 4 20 20Velocity 15

Iteration 1 Iteration 2 Iteration 3 Iteration 4

15 15

10

20

10

20

10

20

Velocity

Committed Completed

VELOCITY

VELOCITY CORRECTS ESTIMATION ERRORS

As a team begins making progress through the user stories of a project, their velocity becomes apparent over the first few iterations Exercise : Suppose a team estimates a project to include

200 points of work. They initially believe they will be able to complete 25 points per iteration, in how many iterations can the project be completed?

They will finish in 8 iterations However, once the project begins their observed velocity is

only 20. Now, how many iterations are required to complete the project?

They will finish in 10 iteration Without re-estimating any work they have correctly

identified that the project will take 10 iterations rather than 8

VELOCITY

THANK YOU Ragini Eguvolla, PMP, ITIL V3, 6σ GB