nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How can I track what was done inside the sprint if I move the incomplete tasks to next sprint?

Rebeca Luna

Should I clone the task and move just the cloned one to next sprint keeping the original inside the closed sprint?

Is there another way I can easily see the work done by sprint? Because even not finished the task I need to know all job done inside the sprint.

Comments

Mirek

A story is issue that could be defined as a simple task or initiative that requires many tasks. You can break down stories into sub-tasks and thanks to that know what was done in a specific sprint. Overall when you close a sprint you will get a Sprint report where issue not resolved (because things might be overestimated, or simply not done) will be included (that it was in progress) and later will be moved to the next sprint automatically. There is not need to clone or doing other stuff to track progress. Doing this will introduce more confusion to your reports.

Rebeca Luna

The problem in doing this is: supposing I have one story with 3 subtasks where 2 are complete and 1 in progress, when I close the sprint, Jira is putting the story back to backlog with all subtasks inside it. But 2 of them were complete in the sprint before. I don't need to have them inside a new sprint again because looking to it, seems they were done in the current sprint when they don't and it confuses the estimates as well. This is my point.

Kelly Albrecht

Completing a sprint with in progress stories, with some subtasks done and others not, will let you move what's not done into the Backlog. The story goes back, because with subtasks still open, it is not done yet.

The reasoning behind this is that subtasking is just a way to breakdown a story, but subtasks are not considered tasks on their own. While some subtasks were in fact completed in a sprint, they are really just part of their Story task, which if all of its subtasks are not done, then it is not done. A sprint will show an in progress story's completed subtasks for context no matter which sprint they were completed in.

You might consider trying to break your epics in to smaller stories so that any and all of a story's subtasks will get completed during a sprint.

You could also consider whether your larger stories would make more sense as Epics. Then what are now subtasks would be stories themselves, within epics, and would behave more like you expect from sprint to sprint.

Mirek

@Rebeca LunaI would not say it is a problem, more like a way of handling tickets and breaking them down into so much small stories that they could be done in a sprint based on your team velocity. Sub-Tasks are more like for people assigned to them ability to track progress outside of initial estimation. Those should not be estimated using story points and not included in the report. No matter if a Story have subtasks or not it will be move to another spring, so from this perspective nothing change. Everything is for improvement. Overall Scrum idea is to improve in every sprint, be agile and react on faster, deliver more..

Rebeca Luna

Hi Kelly,

My main problem is more about underestimated tasks. So the sprint is always breaking and many cases like this happening. I know we need to improve estimation, velocity, etc.

But i'm struggling to move the story for next sprint with subtasks done which for me doesn't make sense once some subtasks were completed in the previous sprint.

We are still using the hours for estimate. I'm not sure if changing it to points would help us to complete the tasks.

Kelly Albrecht

Have you explored the Remaining estimate and time spent setting as can be seen in this article?

https://confluence.atlassian.com/jirasoftwarecloud/configuring-estimation-and-tracking-764478030.html

Rebeca Luna

Yes, we use remaining estimate and time spent.

But my main point is how to organise Jira without loosing the track of what was done inside each sprint.

So if I complete 2 subtasks of the 3 I've planned, what should I do with this card? If I pushed the entire card to next sprint, I can see in the sprint report the card was moved, but that card had complete work done inside it.

So, how can I know if I am moving a card which I didn't even start or cards that have work already done inside it?