Debriefing: Difference between revisions

From squad.gamelibra.com
Jump to navigation Jump to search
(Created page with "Debriefing == '''After the game is before the game!''' == === Step 1 === At the beginning of the debriefing, the facts are gathered: The most important stages of the game are recalled and positive as well as negative events within the project are addressed. === Step 2 === In the second step, the causes for these successes and failures are identified. === Step 3 === In the third step, learnings and optimization measures can be derived from this. Thi...")
 
No edit summary
 
Line 2: Line 2:
== '''After the game is before the game!''' ==
== '''After the game is before the game!''' ==


=== Step 1 ===
=== Step 1: Collect ===
At the beginning of the debriefing, the facts are gathered: The most important stages of the game are recalled and positive as well as negative events within the project are addressed.
At the beginning of the debriefing, the facts are gathered: The most important stages of the game are recalled and positive as well as negative events within the project are addressed.


=== Step 2 ===
=== Step 2: Causes ===
In the second step, the causes for these successes and failures are identified.
In the second step, the causes for these successes and failures are identified.
constructive feedback only!


=== Step 3 ===
=== Step 3: Learnings ===
In the third step, learnings and optimization measures can be derived from this. This knowledge is particularly important with regard to future games, because it avoids repeated errors and makes better use of the experience gained.
In the third step, learnings and optimization measures can be derived from this. This knowledge is particularly important with regard to future games, because it avoids repeated errors and makes better use of the experience gained.
Optional: It is best to record the conclusions drawn up in the team in a protocol, which is sent to all participants after the meeting or stored online (competitive topics).
Optional: It is best to record the conclusions drawn up in the team in a protocol, which is sent to all participants after the meeting or stored online (competitive topics).

Latest revision as of 10:25, 1 March 2023

After the game is before the game!

Step 1: Collect

At the beginning of the debriefing, the facts are gathered: The most important stages of the game are recalled and positive as well as negative events within the project are addressed.

Step 2: Causes

In the second step, the causes for these successes and failures are identified. constructive feedback only!

Step 3: Learnings

In the third step, learnings and optimization measures can be derived from this. This knowledge is particularly important with regard to future games, because it avoids repeated errors and makes better use of the experience gained. Optional: It is best to record the conclusions drawn up in the team in a protocol, which is sent to all participants after the meeting or stored online (competitive topics).