I agree, I tend to use fibonacci for refinement and sprint planning. I find T-Shirt sizes more useful for high-level estimation and releases, but some teams also use them for sprints.
Hi, Let's suppose your next Product Goal consists of 10 stories of 3 points each. That is a total of 30 Story Points. Now, the velocity of your Scrum Team is 6 points per 1-week Sprint. That means the two most important User Stories should be delivered by the first Sprint, and so on. As a quick forecast, the Product Goal may be achieved in about 5 weeks. However, during these Sprints, new ideas will appear with users' feedback and the Product Backlog is expected to grow. When a team estimates, according to studies, the tendency is to underestimate, so depending on the certainty the Product Goal may take more time, for instance, 10 weeks. See the cone of uncertainty. Was my answer useful? How is your experience?
@@IgnacioJulianPaz Thanks a lot for the answer! So as I understand now, we should know the weekly velocity of our team in points before we begin planning. But what if I'm new or just about to implement scrum?
@@Vicinfi when your team does not have historical velocity, you need to make a forecast. There are many techniques, but I just like to encourage the team to discuss how much work they think they can do in the first Sprint. Some questions I can do: How many stories of size 1 like these examples you think you can get done in one Sprint? How many stories of size 3 like this and that one you think you can get done in one Sprint? After pulling some stories from the Product Backlog, do you think you can get all of them done by the end of the Sprint?
Tried both playing poker and T-shirt sizes. I found Fibonacci playing poker to be more accurate and measurable.
I agree, I tend to use fibonacci for refinement and sprint planning. I find T-Shirt sizes more useful for high-level estimation and releases, but some teams also use them for sprints.
If we agree on the estimate, how do we translate it into actual timing to complete the task?
Hi, Let's suppose your next Product Goal consists of 10 stories of 3 points each. That is a total of 30 Story Points. Now, the velocity of your Scrum Team is 6 points per 1-week Sprint. That means the two most important User Stories should be delivered by the first Sprint, and so on. As a quick forecast, the Product Goal may be achieved in about 5 weeks. However, during these Sprints, new ideas will appear with users' feedback and the Product Backlog is expected to grow. When a team estimates, according to studies, the tendency is to underestimate, so depending on the certainty the Product Goal may take more time, for instance, 10 weeks. See the cone of uncertainty. Was my answer useful? How is your experience?
@@IgnacioJulianPaz Thanks a lot for the answer! So as I understand now, we should know the weekly velocity of our team in points before we begin planning. But what if I'm new or just about to implement scrum?
@@Vicinfi when your team does not have historical velocity, you need to make a forecast. There are many techniques, but I just like to encourage the team to discuss how much work they think they can do in the first Sprint. Some questions I can do: How many stories of size 1 like these examples you think you can get done in one Sprint? How many stories of size 3 like this and that one you think you can get done in one Sprint? After pulling some stories from the Product Backlog, do you think you can get all of them done by the end of the Sprint?