Why estimate the project in Story points, a note to clients

No project can go very long before someone starts asking “When will you be
done?” The best approach for estimating stories would be one that:

• allows us to change our mind whenever we have new information about a
story
• works for both epics and smaller stories
• doesn’t take a lot of time
• provides useful information about our progress and the work remaining
• is tolerant of imprecision in the estimates
• can be used to plan releases

An approach that satisfies each of these goals is to estimate in story points. A
nice feature of story points is that each team defines them as they see fit.

Source- Mike Cohn's book

Comments

Post a Comment

Popular posts from this blog

Scrum Answer to Top 10 Software Project Risks

Source: (The Standish Group, 2011) Lack of top management commitment Scrum demands commitment from the top management through the assignation of a full-time cross-functional self organized team. The team is protected and can take their own decisions about the project with the support of the top management. Failure to gain user commitment In Scrum, the team constantly show working software to the users, which increase the commitment and feedback. Misunderstanding the requirements Scrum knows that is not possible to fully understand all the user requirements. In each iteration, the team work in the more important and clear requirements. As the software is developed, the team get better insights about the project goals and have more clarity about the following requirements. Lack of adequate user involvement Constantly working software makes the users more involve in the process. Lack of required knowledge/skills in the project personnel In Scrum, the teams are cros
Read more