Tackling sprints without enough tasks

[Agrendalath (Piotr Surowiec)]

@tikr

I might be missing something but it looks like SprintCraft is already factoring in remaining estimates when assessing the workload for the upcoming sprint: For each cell member, hours displayed in the first three columns (My Work, Reviews, Upstream) seems to include remaining estimates from tickets in the current sprint.

Correct. All remaining time from the current sprint and upcoming sprint is included in the calculations.

[ChrisChV (Christofer Chávez)]

@antoviaque

Anyone is welcome to review it – I have pinged in particular @tikr @ChrisChV @paulo @mtyaka as reviewers, as this affects some of the sprint planning and epic planning managers duties.

Thanks! I will take a look today or tomorrow

[antoviaque (Xavier Antoviaque)]

@tikr

I might be missing something but it looks like SprintCraft is already factoring in remaining estimates when assessing the workload for the upcoming sprint: For each cell member, hours displayed in the first three columns (My Work, Reviews, Upstream) seems to include remaining estimates from tickets in the current sprint.

@tikr Yes, but this is currently not very useful to assess the workload for the upcoming sprint, and needs improvements - see the discussions items above about this, and for example this point:

I also don’t think sprintcraft currently considers the time left in the current sprint when estimating capacity for the following sprint? Ie, in ongoing tickets, we should probably not consider that all the time will spillover in the following sprint, only the time left on tickets that exceeds the remaining hours in the sprint?

And this was just from a superficial review. Imho we need a proper discovery, including concrete attempts at reviewing the workload for the following sprint at the end of a sprint, and reviews by sprint planning managers of the outcome, to make sure we are able to tell whether we will have a workload issue,

[tikr (Tim Krones)]

@antoviaque @Agrendalath Thanks for the quick replies I think I have what I need to create the first set of follow-up tickets for SprintCraft from this thread now

[antoviaque (Xavier Antoviaque)]

FYI, the handbook PR is merged: Sprints - OpenCraft Handbook

I think everyone had a chance to review, and that the comments should have been addressed. But as mentioned on the merge request, if there are other reviews coming in in the next days, or points from existing comments that haven’t been correctly addressed, don’t hesitate.