
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-02-2019 05:04 AM
The way our organization is set up, we have the need to have several Sprints per team at the same time. But, this is not allowed. Has anyone run into this and found a good solution? We've just been creating more and more assignment groups and the management of all these groups just to organize sprints is a nightmare.
Mickey Cegon
Solved! Go to Solution.
- Labels:
-
Agile Development

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-03-2022 04:13 AM
Hi,
The main purpose of the sprint is to manage the workload of a specific team to be able to manage these concurrent priorities. By having 1 team have multiple sprints to manage simultaneously takes away this very important benefit of using sprints(agile methodology)
I would suggest that you remain with OOTB 1 sprint per team for the team to manage its workload and use other tools to give other stakeholders the views they need (Releases, APW, Project Workbench, etc...)
Thank you,
Patrick

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-02-2019 07:55 AM
Greetings Mickey,
I believe you could disable the rule that prevents a group from having more than one sprint active at a time. It looks like this is called 'Cannot add new current sprint if exists'
Disabling this: may have some roll-up/reporting issues, as the system expects only 1 sprint active at a time for a given group.
Why do your groups have multiple different sprints at the same time?
-Andrew Barnes
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-09-2020 08:46 AM

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-09-2020 08:52 AM
We have teams that are "shared services" to many areas, and may have efforts being worked on by the team for other areas, that will be released as a part of a larger release by the different areas. So, the stories for area A need to be in a different sprint than the stories for area B, but could be released by these areas at the same time. So, the sprints overlap.
Mickey Cegon

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-12-2021 08:25 PM
I have the same issue. I have a team/group of integration developers that are working on separate sprints that overlap for different products/projects. I guess I could split the team up into smaller teams but that would be harder to manage.