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; } } }

Impact of consolidating Team during sprint

Jennifer Baum

For multiple reasons, I have two teams that I need to consolidate into one new team. I'm wondering how this will impact current work assignment to the "old" two teams.

Should I create one brand new team and add the new team members or reuse one of the existing teams and add the users from the soon to be defunct team?

How does this impact work currently assigned?

Accepted answers

Mark Segall

Hi @Jennifer Baum and welcome to the community!

The "cleanest" approach would be to archive the existing projects for each team and move remaining backlog items from each project into a new project and start from scratch. This gives you posterity for everything prior to the consolidation and a fresh starting point for going forward.

All comments

Mark Segall

Hi @Jennifer Baum and welcome to the community!

Jennifer Baum

@Mark Segall - Thanks for the reply.

This seems like a large lift. If the members are moved on to one of the existing teams, can we just track that as when sprint X started, that is when that team's velocity increased?

Is there any impact to completed/done items?

Mark Segall

The only real impact will be any filters that are looking at specifics like project, or issue key (e.g. looking for a group of specific epics) that were specific to the initial project. This would have a cascading impact on historical data presented on dashboards, Confluence-Jira macros, etc.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud

team-management