User Story Estimation
I think the most difficult and confusing step in Scrum is estimation. Since software development is combination of science and art and we are almost always developing something new , it becomes very hard to estimate efforts in Hrs.
Estimating a USer story in Story points is better way of estimating things. If done properly, it saves lot of time/effors while negotiating with Product Owners on what stories should go in Sprint Backlog..
Instead of using a a tradionatial Fibonacci sequence for estimating user story points, It is better if we estimate efforts by multiplying Size and complexity . It is easier to approximately estimate the size( for eg 2 days vs 5 days) and complexity .
I will be presenting various guidelines for estimating size and complexity. I will be showing you simple tools/methods to identify if your estimates are proper and their best practices.
Outline/structure of the Session
What is estimation
1) Effort=Size * Complexity.
Guidelines for calculating Size
Guidelines for calculating Complexity.
Distribution of Efforts
How to calculate Vilocity
- Proper estimation techniques.
- Best practices for estimating.
Developments teams and Scrum Masters