You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 6
Next »
- In case of relative estimation technique used
- Upon introduction of story points, as a starting point agree on ideal story as the one which takes half of the day for development, and half of the day for testing
- Introduce estimation techniques guide with reference story which can be used to measure other relative stories
- Make sure that level of complexity is common for the entire team including different streams
- Monitor and control estimation accuracy on the project, establish corresponding metrics to check deviations between original and actual time. In case of over or underestimation undertake proper corrective and preventive steps.
- Use planning poker while giving relative estimation
- Monitor and control that each team gives opinion on story complexity if there is no task for his/her stream in terms of this scope, in particular
- Revisit reference story once team size changes, tech stack is updated or when team becomes more familiar with technology or/and product
- Include required to deliver a product (not limited to development and testing).
- Calculate focus-factor to find out real time for the productive activities to plan sprints and tune velocity
- Every estimated task should go with the delivery cadence and should be closed during 1 sprint, if no - decompose it!
- In case of too many uncertainties with estimation, create time-boxed Spikes to make a research first
- Choose proper estimation technique based on historical data available, experts availability, scope known, team assigned, level of accuracy required, etc
|
Useful materials
Story Points Estimation
How to do effective project estimation during Pre-Sales