| Context | An organization has many Scrum Teams working on different Product Backlogs. |
| Problem | No top-level-priorization of Product Backlog Items. The investment into an important project is limited by the number of Scrum Teams working on their respective Product Backlog. For individual Product Backlog Items, priorization only works within projects and important Product Backlog Items might be delayed. |
| Forces | too little/too much centralization |
| Solution | Create a Company Backlog Integrate all Product Backlogs into a global Company Backlog and assign a single person to be the Product Owner of that backlog (e.g. a Chief Product Owner). When using epics and themes, the Company Backlog becomes clearer and supports regular priorization reviews by senior management. |
| Resulting Context | ROI for the organization is increased as the most important requirements are implemented first. |
Dieser Artikel wurde von Andreas Heilwagen am 11.11.2011 um 13:32 gepostet und unter Scrum eingeordnet. Sie können Kommentaren über den RSS 2.0-Feed folgen. Das Posting steht unter der Creative Commons-Lizenz wenn nicht anders vermerkt.
