During the Sprint Retro everybody in the team writes up the perceived issues on post its. We collect them on the white board, choose the most important ones, for which we try to identify the root cause(s) right there on the board. Then we come up with potential measures to tackle each of the causes. From the measures we choose two or three of the more feasible ones for the next Sprint.

Now my problem: Some time later in the day, somebody cleans the white board.

So here's my question: Is there a recommended format or a procedure or check list for documenting the sprint retrospective. Not only the outcomes (i.e. measures to be tried in the next sprint), but also the other measures (for trying later), the problems and root causes. Best would be in a format that could be used as additional input for the next retro ...

My question: Is there

• a recommended format or
• a procedure or
• a check list

for documenting the sprint retrospective? Not only the immediate outcomes (i.e. measures to be tried in the next sprint), but also the other measures (for trying later), the problems and root causes.

During the Sprint Retro everybody in the team writes up the perceived issues on post its. We collect them on the white board, choose the most important ones, for which we try to identify the root cause(s) right there on the board. Then we come up with potential measures to tackle each of the causes. From the measures we choose two or three of the more feasible ones for the next Sprint.

Now my problem: Some time later in the day, somebody cleans the white board.

Hence my question: (see above) 

Best would be in a format that could be used as additional input for the next retro ...