My friend @Peter Jessen wrote a great article about the implications of moving a Team here: https://community.atlassian.com/t5/Jira-Align-questions/What-are-the-implications-of-moving-a-team-from-1-train-to/qaq-p/1339252
A lot of the points he raised in that article about a team also apply to an entire Program.
There are many good reasons to restructure the portfolios, solutions and programs, especially as you discover more about how your teams work together to deliver value to your customers. (There are bad reasons too! Constantly reshuffling teams makes it difficult to build any sort of momentum, team cohesiveness, and predictability.)
A couple key considerations:
- Try to make changes on PI boundaries. That way, you can keep and learn from any metrics you gathered in previous PIs.
- Take the opportunity to clean up your Jira backlogs. In many cases, it is best to create new Jira projects and boards for the teams that are moving and only move the relevant Jira issues into the new projects.
In general, the best practice is
- Set up the new program in Jira Align (and we recommend a new project in Jira
- Set up each of the teams in the new program
- Set up the teams' backlog in Jira (move only the necessary issues to the new project)
- Update the Jira project and board mapping in Jira Align with the new programs
- When you're all set and things are working as you wish, deactivate the old teams and programs in Jira Align (so they don't show in drop-down lists).
- If you added new Jira projects and aren't using the old ones any more, remove them from the Jira Align project list so the connector doesn't keep checking.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.