Team Retrospective

is part ofIteration
is organized byTeam Scrum Master
Attendees:Team Product Owner, Working Team
Adapted artefacts:Team DoD, Team Improvement Backlog
Inspected Artefacts:Team Iteration Backlog

The Team Retrospective gives the team the opportunity to review themselves and to identify and plan improvements in the way they work for the upcoming iteration . It takes place between the Team Review and the next Team Planning. For a four-week iteration, an upper limit of three hours is set. The meeting is usually shorter for shorter iterations. The Scrum Master ensures that the meeting takes place and that all participants understand its purpose. The Scrum Master ensures that the meeting is constructive and productive. The Scrum Master teaches everyone how to adhere to the time frame (time box). Due to its responsibility for the P4 process, the Scrum Master takes part in the Team Retrospective as an equal member. The Team Retrospective is being held to …

  • to review how the past iteration was in terms of people, relationships, processes, infrastructure and tools involved;
  • identify the most important and possible improvements and put them in order; and
  • create a plan for implementing improvements to the way the team works.

The Scrum Master encourages the team to improve their development processes and practices within the P4 framework to work more effectively and satisfactorily in the upcoming iteration. In each Team Retrospective, the team 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 Team Retrospective, the team should have identified improvements for the upcoming iteration. The implementation of these improvements in the next iteration is the adaptation effort for self-examination of the team.

In the meantime, there are many methodological approaches and questions for the course of the Team Retrospective, 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 team.

There are many more ideas and suggestions under Fun Retrospectives or Retromat .

.


Further suitable links:

Events Roles Groups Artifacts
Team Planning

Team Sync

Team Backlog Refinement

Team Review

.

Cluster Retrospective

.

Organisation Retrospective

Team Product Owner

Team System Engineer

Team Scrum Master

Working Team

Community of Practice

Team Backlog

Inspectable Results

Team DoD

Team Improvement Backlog