Estimation of issues in Story Points
Hi, I want to tell you how the Scrum Assistant plugin helped our team.
Many team members are asking questions:
- How to understand that we are going to the sprint goal?
- What is our average work speed?
- And how do we evaluate our work and plan a backlog?
In order to answer all these questions, I advise you to start using the practice of evaluating the elements of the backlog in Story Points. You can use any scale, but the Fibonacci number series is most often used.
It was very important for us that at the time of the Sprint launch our team had estimates for all elements of the backlog. Since this is not provided in the basic version of JIRA, we decided to install a free (at the moment) Scrum Assistant addon. The add-on does not allow you to start a sprint if not all tasks are evaluated, as suggested by the pop-up window.
After completing the sprint planning, to track the achievement of the sprint goal, we use the sprint burndown chart. If in the process we decide to add new unappreciated issues to the sprint, Scrum Assistant will also warn us about it.
We are always sure that everything we do has an estimation!
After completing several sprints, the team accumulates static data on the average number of burned story points. This information can be seen on the Velocity diagram.
Knowing your average work speed, you can always plan your work for the future.
Before the start of using this addon, (on average) only 40% of sprint issues were estimation, after installing the Scrum Assistant, this figure increased to 100%.
Our project manager is very happy! 😀