Keep the issues in same sprint

Peter Jackison
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
March 3, 2024

As RTE, I am moving all open issues from one sprint to another sprint every 2 weeks. one of 10 teams (under same project), does not want to move open / in progress issues to another sprint while I am moving other teams' issues. 

As all teams are bound under same project, how can I keep away this 1 team? is there any option.

2 answers

0 votes
Marc Koppelaar
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
March 5, 2024

Hi @Peter Jackison 

As @Walter Buggenhout is stating, are you running a single sprint related to all the teams or does each team has its own sprint?

A sprint per team would be best practice as this gives control on what each team is working on an has reporting based per team.

Based on burn up or down, velocity etc..

This will also give more insight in each trams performance and if there is need to guide and coach them if required.

0 votes
Walter Buggenhout
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
March 3, 2024

Hi @Peter Jackison and welcome to the Community!

There's quite a bit unclear to me about your use case here. From your description, it seems as if you are running a single sprint across multiple teams. On top of that, you seem to be taking the responsibility for running the team's work out of their hands - apart from a tooling question, I read lack of communication and ownership about ongoing work between the lines. But that may be just me taking assumptions to fill in the blanks ...

In an ideal situation, you would have a sprint per team, with each team being responsible for planning its own sprints. In an ART, these sprints should have the same start and end dates, so it becomes possible to keep aligned across the teams in your ART. When each team's velocity becomes predictable, the idea should be not to be moving open items to the next sprint all the time, but try not to overcommit. If all teams are working in the same sprint, you won't be able to get an idea of each individual team's velocity and their capacity to deliver. Maybe this one team is currently not updating the status of their work in real time, which might mean that the open items you move to another sprint are not really open. If that is the case, you should have a discussion about that with them.

Also, Jira helps you to move unfinished work to the next sprint automatically when you complete the sprint. It is not something you should do beforehand as indeed, items that could be finished at the very end of the sprint may disappear from view this way, while they are relevant for the team currently working on them.

Overall and in summary: the key here is all about communication. Rather than moving items around, talk to each other, find out where you can improve and make agreements on that. Together. As RTE, help people become autonomous while helping them see the bigger picture they contribute to.

Hope this helps!

Suggest an answer

Log in or Sign up to answer