Discover latest Indian Blogs Sprint Effort Estimation Skip to main content

Sprint Effort Estimation

# Little Savings

As one of the follower requested to write a post on the Scrum Estimation, I am writing this post.

Since every one knows the product owner creates the product backlog also known as user stories.
During the sprint planning, the picking up of the user stories will be easy if it has user story points or estimated work effort.

Estimation of work:

Before estimating the work, one has to define size/complexity of the each user story. 
The most commonly used technique is playing the Scrum Poker, which has the fibonacci series of numbers(1, 2, 3, 5, 8, 13...) and pick one number from series based on the complexity(Many apps are available in Google Store).


A team of Development & Product Owner is part of this. One should be acting as a moderator from Dev team, who will read out the user story.


Once the user story has read out, team should define the size or complexity of the user story, by picking one number from the fibonacci series and every one should expose the number at the same time.

If every one has a matching number, will continue to add the same number as complexity, which is an ideal case. but in real, the number doesn't match, then the team should highlight and discuss why the particular number has given for the user story, which will help to get the missed points. And again need to pick the number from fibonacci series to concur everyone with the same number. The finalized number added to the user story, which is called as "Story Point".

Once the complexity has been defined for the user stories, lets see how to plan for a Sprint.

Lets understand by the following simple example.

            User Stories                    Complexity
            User Story -1                   2 Story Points
            User Story - 2                  3 Story Points
            User Story - 3                  8 Story Points

Post the discussion, the complexity has been assigned to each user story as above.

Assume each complexity of 1 story point takes 4 hours.

User Stories            Complexity            No of hours
User Story -1                   2                            8
User Story - 2                  3                            12
User Story - 3                  8                            32
Total                                                            124 hours

So to complete total available stories, it will take 124 hours.

Assuming each individual productivity is 6 hours per day, which will consume 21 days to complete all the user stories, which is equal to 4 weeks(5 working days per week).

Now Sprint can be planned in 2 ways.

2 weeks equivalent to 2 Sprints
4 weeks equivalent to 1 Sprint

Little Savings - Sprint
Hope this post gave the basic idea on the effort estimation and also the sprint planning. Request to post your queries.