That's a shame, if I have one large task that spans multiple sprints, I would like to be able to have some subtasks in each sprint.
Right now, the closest I can get to that is to just keep moving the large task from sprint to sprint. But this distorts the "work remaining" calculations of the current sprint if I know some of it will have to be moved to the next sprint.
One of the key ideas of scrum is to release a working software after a sprint. It requires all tasks (stories) in the sprint to be fully completed, along with their subtasks. If you have a large task, that consists of many smaller parts, and it's too big to deliver in one sprint, that means you have an EPIC, not a task, my friend :)
Epic has the same issue though. You can't have multiple sub-tasks or Jiras under the same epic in different sprints. I am not sure why Atlassian doesn't respond properly to this very common scenario. The way you would need is..
-- some top level "soft Epic" that has no concept of it's own sprint, but just a grouping of different sub-tasks or jiras.
-- different sub-tasks can be in different sprints if necessary, and the planning board will show the soft Epic (may be JIRA software needs a new type) and all the sub-tasks that belong to each sprint in the corresponding Sprint.
This does need special handling. I can use labels, but labels don't aggregate the total combined effort of all the sub-tasks or jiras.
Atlassian, can you please reply?
Large tasks spanning multiple sprints should be Epics. Looking at Agile Scrum this is what they are meant for.
We use Epics for large stories spanning multiple sprints, stories for the work breakdown going into the sprint, and sub-tasks are reserved for the individual to further break down a story if wanted/needed.
This way large tasks can span multiple sprints, we can follow the progress using the epic report, we can plan stories intertwined with others and we can support individual per-story work breakdown as neeed.
Maybe you can use this approach too to achieve what you want.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Can a new-to-agile team survive and thrive in a non-agile culture? If so, what advice would you give to those trying to be agile in a non-agile culture? What's the key(s) to success? Share your thoug...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs