Multiple themes in the larger organizational backlog
An organization that has fully embraced the Agile principles will create multiple themes across the company to enhance collaboration. Projects are mapped to themes as part of a larger backlog. This backlog can be used to quickly recognize if project rankings within themes or even individual themes themselves should be modified. Themes can be modified within prioritization as the needs of the business evolve over the course of the defined timeline.
Features in a lower theme or project can be moved into a higher ranked effort if dependencies are noted. This will help to minimize technical debt to reduce re-work.
Agile project portfolios at the theme level will require the skills of an Agile portfolio manager who is highly skilled in delivering scalable portfolios.
A separate product owner will be required for management of the feature backlog within a theme. One or more scrum masters will be required to manage sprint teams within a theme. The Agile program manager will host a weekly Scrum of Scrums meeting to obtain status and manage issues across active themes.
Recommended Further Reading
The following materials may assist you in order to get the most out of this course: