You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Three Scrums for the Java-kings under the web,
Seven for the Python-lords pulling out their hair,
Nine for Cobol Code ever on the ebb,
One for the Scrum Master on his desk chair
In the Land of Jira where Projects lie.
One Scrum to rule them all, One Scrum to find them,
One Scrum to bring them all and in Agile bind them
In the Land of Jira where Projects lie.
One of my constant struggles as a project manager is with managing resource constraints across multiple projects that use people from the same pool of resources. In most cases, the project team will be made up of developers, testers, product owners, and engineers that are assigned to multiple projects with competing priorities. In my experience, many Scrum teams are made up of a core group of people dedicated to that project with other subject matter experts (SMEs) entering and exiting the Scrum team as needed to perform specific tasks during the Sprint. Likewise, at the program level the program manager wants to set the priority on issues in Jira across the program, not necessarily from project to project. Managing these expectations and constraints is easy enough, if you set up a Scrum of Scrums to guide the individual Sprints across the projects.
First, the Scrum-of-Scrums will need to include all the issues from all of the projects it will manage using a filter.
The important thing to remember here is that boards reside within projects, so pick one project that will last across the duration of all the projects in the program. This helps make sure that people can find the board when the smaller projects get completed and are closed out.
Sprints can now be created using issues from all the projects in the program and the Program Manager and Scrum Master can prioritize the issues in the new “program backlog” that was created with the new Scrum of Scrum board. Product Owner and Scrum Master can also work together to adjust priorities within the project backlogs using Scrum boards created for each individual project.
Scott Theus
Rising StarAgile Governance and Training Manager
Signet Jewelers
Cleveland, Ohio
180 accepted answers
3 comments