You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
We have created a plan in Advanced Roadmaps which we are trying to autoschedule but there is some behaviour we don't understand where a 3 story point story is being auto-scheduled across 2 2-weekly sprints (4 weeks in total) even though the full capacity of 8 story points is available in one sprint and we are using scrum with a sprint size of 2 weeks. It is also giving the following warning for the story: "More than one sprint is needed to finish this issue. Break your story down further so that estimate is reduced, or decrease the scope of the sprint, until this issue fits into the sprint. Then, recalculate your plan."
This is not happening consistently to other stories in other sprints for the same team. Some stories of 8sp are being scheduled correctly in one sprint and utilising capacity for one sprint.
We have set up a Team with 1 member and an available capacity of 8 story points. The story which is being auto scheduled is 3 story points. There are no other stories in this sprint. The story has no sub-tasks.
As a test we reduced the size of the story to 0.1 story points to see if the autoscheduler would keep it within a sprint - that works - the warning then disappears and it is scheduled correctly within one sprint.
I don't understand why with 3sps it thinks it is too big for one sprint.
We are using a scrum board with 2 weekly sprints underneath this plan.
We are using the Fibonacci series for sizing stories: 1, 2, 3, 5, 8 but some very small tasks we have assigned a size of 0.1 as we need to track then but they don't utilise much capacity from the team.
Due to this behaviour, it is assigning more sprint capacity than is actually required to complete the story and pushing dates to the right.
Thanks for your help and suggestions