Organization Retrospective

is part ofPortfolio Cycle
is organized byOrganization Scrum Master
Attendees:Cluster Product Owner Group, Cluster Scrum Master Group, Cluster System Engineer Group
Adapted artefacts:Organization DOD, Organization Improvement Backlog
Inspected Artefacts:Portfolio Cycle Backlog

The Organization Retrospective offers the Organization Scrum Master (OSM) the opportunity to review the working methods of the organization, represented by the Portfolio Owner (PFO) and the Cluster System Engineer Group (CSEG) , as well as improvements to the Identify and plan how to work for the coming cycle . The Organization Retrospective takes place between the Portfolio Review and the next Portfolio Planning and is based on the results of the Cluster Retrospectives , mostly from the Cluster Scrum Master Groupwere processed. An upper limit of four hours is set for this for a quarterly cycle. The Organizational Scrum Master (OSM) ensures that the meeting takes place and that all participants understand its purpose. The OSM ensures that the meeting is constructive and productive and teaches everyone to stick to the time frame (time box). Due to its responsibility for the P4 process, the OSM takes part in the Organization Retrospective as an equal member. It is carried out to …

  • to review how the past Cycle was in terms of the Clusters, teams, relationships, processes, infrastructure and tools involved;
  • identify the most important and possible improvements and put them in order; and
  • prepare a plan for implementing improvements in the way the organization works.

The Cluster Scrum Master Group is working to improve the organization’s development processes and practices so that the Clusters can work more effectively and satisfactorily in the coming cycle. In every Organization Retrospective, the Cluster Scrum Master Group works out ways to improve result quality by adapting the processes accordingly or by defining-of-done, provided these changes are appropriate and do not conflict with product or company standards. At the end of the Organization Retrospective, the CSMG should have identified improvements for the coming cycle.

In the Organization Retrospective, the Cluster Scrum Master Group also checks the workflows between the Cluster (e.g. using value stream mapping) and adjusts the areas of responsibility of the Clusters and, if necessary, also the cluster structures within the Organization.

The Cluster Scrum Masters take the suggestions and measures with them into their clusters.

Process of the Organization Retrospective

Mostly, the Cluster Scrum Masters bring problems, impediments and improvements from their Clusters with them to the CSMG, which they have collected in the Cluster Retrospectives of the Clusters. These are collected and prioritized in the Organization Improvement Backlog. During the working hours of CSMG, the highest priority improvements are analyzed and processed during the current Portfolio Cycle. In the Oragnization Retrospective, changes are then jointly decided and implemented.

For the determination of further problems, disabilities and ideas for improvement at the Cluster level, the TSMG uses the same methodological approaches and questions as at the team level, e.g.

  • Glad, Sad, Mad
  • Keep, change, puzzled
  • Good, problems, questions
  • Start, stop, keep, more, less

The Delegation Poker game is particularly suitable for negotiating the delegation of responsibility to the CSEG


Further suitable links:

Events Roles Groups Artifacts
Team Retrospective


Cluster Retrospective


Portfolio Planning

Organization Sync

Portfolio refinement

Portfolio Review

Portfolio Owner

Portfolio Architect

Organization Scrum Master

Cluster Product Owner Group

Cluster System Engineer Group

Cluster Scrum Master Group

Organization Management Circle

Portfolio Backlog

Systems & Applications

System Platforms & Variants

Organization DoD

Organization Improvement Backlog