Team Retrospektive - Versionsgeschichte

Simon.dueckert am 14. November 2017 um 19:48 Uhr

2017-11-14T19:48:37Z

← Nächstältere Version		Version vom 14. November 2017, 21:48 Uhr
Zeile 1:		Zeile 1:
	~~{{piktogramm_methode}}~~
	A '''Team retrospective''' is a regularely conducted meeting to reflect on the last 4-6 weeks of a project. It's been developed within the project management method [[Scrum]] where it's used to reflect a sprint.		A '''Team retrospective''' is a regularely conducted meeting to reflect on the last 4-6 weeks of a project. It's been developed within the project management method [[Scrum]] where it's used to reflect a sprint.


	==Goals==		==Goals==

Kerstin.buecher: /* Weblinks */

2007-03-05T07:44:36Z

Weblinks

← Nächstältere Version		Version vom 5. März 2007, 09:44 Uhr
Zeile 71:		Zeile 71:

	==Weblinks==		==Weblinks==
			*[http://video.google.com/videoplay?docid=-7910406883328902493 Google-Video "Agile Retrospectives"]: Vortrag von [[Diana Larsen]] und [[Esther Derby]]
	*[http://www.sprint-it.de/scrum-checklists/ Scrum Retrospective checklist] Source of most of this content (this version) (Free Download of pdf)		*[http://www.sprint-it.de/scrum-checklists/ Scrum Retrospective checklist] Source of most of this content (this version) (Free Download of pdf)
	*[http://~~video~~.~~google~~.com~~/videoplay?docid=-7910406883328902493 Google~~-~~Video "Agile Retrospectives"~~]: ~~Vortrag~~ von ~~[[Diana Larsen]]~~ und ~~[[Esther Derby]]~~		* [http://www.sprint-it.com sprint-it]: Anbieter von Schulungen zu und Begleitung von Team Retrospektiven

	==See also==		==See also==

Kerstin.buecher: /* See also */

2007-03-05T07:44:10Z

Kerstin.buecher: /* See also */

2007-03-05T07:44:01Z

Kerstin.buecher: /* Weblinks */

2007-03-05T07:42:10Z

Weblinks

← Nächstältere Version		Version vom 5. März 2007, 09:42 Uhr
Zeile 73:		Zeile 73:

	*[http://www.sprint-it.de/scrum-checklists/ Scrum Retrospective checklist] Source of most of this content (this version) (Free Download of pdf)		*[http://www.sprint-it.de/scrum-checklists/ Scrum Retrospective checklist] Source of most of this content (this version) (Free Download of pdf)
			*[http://video.google.com/videoplay?docid=-7910406883328902493 Google-Video "Agile Retrospectives"]: Vortrag von [[Diana Larsen]] und [[Esther Derby]]

	==See also==		==See also==

Kerstin.buecher: /* Goals */

2007-03-05T07:38:49Z

Goals

← Nächstältere Version		Version vom 5. März 2007, 09:38 Uhr
Zeile 6:		Zeile 6:
	* Shared understanding of what has happened.		* Shared understanding of what has happened.
	* Learn from past experience to improve the productivity of the team.		* Learn from past experience to improve the productivity of the team.
	* Continuously improve the productivity of ~~Elektrobit~~ (~~as it'll become a~~ [[Learning Organization]].		* Continuously improve the productivity of the organization ([[Learning Organization]]).

	==Roles==		==Roles==

Kerstin.buecher am 5. März 2007 um 07:38 Uhr

2007-03-05T07:38:03Z

Neue Seite

{{piktogramm_methode}}
A '''Team retrospective''' is a regularely conducted meeting to reflect on the last 4-6 weeks of a project. It's been developed within the project management method [[Scrum]] where it's used to reflect a sprint.

==Goals==
* Shared understanding of what has happened.
* Learn from past experience to improve the productivity of the team.
* Continuously improve the productivity of Elektrobit (as it'll become a [[Learning Organization]].

==Roles==
* Moderator (in case you're working with scrum that's the Scrum Master)
* Project Team

==Checklist==
===Meeting Preparation===
* Participants are invited:
** Scrum Master resp. Moderator (depends on [[Scrum]] yes/no)
** All project team members
** (Optional) Product Owner
* Additional facilities:
** Text markers for all participants
** Post-its
** Red and green sticky dots
** Whiteboard and flip chart
* A flip chart with the Prime Directive
* A time-line over at least 3 connected flip charts
* A flip chart with “What Went Well”
* A flip chart with “What could be Improved”
* A flip chart with “Who is in Control” divided in 2 areas “Team” and “Organization”

'''Prime Directive:''' Regardless of what we discover, we must understand and truly believe
that everyone did the best job he or she could, given what was known at the time, his or her skills
and abilities, the resources available, and the situation at hand. (''Norm Kerth'')

===Meeting Moderation===
* Present the goal of the meeting
* Present the Prime Directive
* Mark the start and the end date of the Sprint on the time line
* Explain to the participants how to work with Post-its.
:'''Note:''' Working with Post-its: Write only ONE event on each Post-it.
* Hand out Post-its and ask everyone to write on them all significant events of this sprint; Timebox: 5 min.
* Each participant in turn adds his Post-its to the time-line and explains in two sentences the story behind each event
* Hand out Post-its and ask everybody to write on them “What went well”; Timebox: 5 min.
* Each participant in turn adds his Post-its to the flip chart “What went well” and explains it
* Hand out Post-its and ask everybody to write on them “What could be improved”; Timebox: 5 min.
* Each participant in turn adds his Post-its to the flip chart “What could be improved” and explains it
* For each item on the “What could be improved” flip chart:
** ask the team “Who is in control of this impediment?”
** move the Post-it to the corresponding column on the flip chart “Who is in control”
* Prioritize both lists with the team
* Run a wrap-up of the meeting:
** Each participant gives a short reflection about the retrospective

===Meeting Results===
* The “Who is in control” flip chart is visible to everyone in the organization
* The impediments related to the organization
** are added to the Impediment Backlog (if working with Scrum)
** are taylored into tasks that are put on a S.M.A.R.T. task list (if not working with Scrum)
* The impediments related to the team
** are added to the Product Backlog (if working with Scrum)
** are taylored into tasks that are put on a S.M.A.R.T. task list (if not working with Scrum)

'''Impediment Backlog''': An Impediment Backlog lists any issues that have to be
solved within or concerning the team. The Scrum Master makes sure that Impediment Backlog
items are assigned and worked on.
(For more information on Scrum and Scrum wording see [[Scrum]].)

*
: The results should be published at your Wiki project page.

==Weblinks==

*[http://www.sprint-it.de/scrum-checklists/ Scrum Retrospective checklist] Source of most of this content (this version) (Free Download of pdf)

==See also==
* [[project retrospective]]
* [[Projekt Debriefing]]
* [[Scrum]]

==Contact==
* [[Simon Dückert]]
* [[Kerstin Bücher]]

[[Category:Method]]

← Nächstältere Version		Version vom 5. März 2007, 09:44 Uhr
Zeile 79:		Zeile 79:
	* [[Projekt Debriefing]]		* [[Projekt Debriefing]]
	* [[Scrum]]		* [[Scrum]]
	* [http://www.sprint-it.com sprint-it]: Anbieter von Schulungen zu und Begleitung von Team Retrospektiven

	==Contact==		==Contact==