Have you heard the term “post-mortem” documentation? Simply you want to keep your lessons learnt for anyone else in need in the future. 

I refer in one of my webinars to Stones on Agile Roadmap. It is visibility and transparency wall which should bring a bit of fun to work with issues and help with self-pro-activeness of the people.

Once the Stone is Gone from the road, I recommend to keep it visible next 2 sprints and celebrate a bit the success. During these 2 sprints time frame, you might document what was the issue all about. It should not be any long story or boring dense text. Important is again, the informative value and quick lesson learnt from the documentation.

There is no blame within the documentation process. Typically you will organize the meeting where this template or document should be finished.

Your Postmortem template which you might save e.g. on Confluence might look like:

Postmortem owner: …………………………………………………………………………………

Connected to Stone / Issue: ……………………………………………………………………..

Overview & What happened: …………………………………………………………………….

Root Causes: ………………………………………………………………………………………….

Solution: …………………………………………………………………………………………………

Keep in mind that your issue description, root cause and solution should be open, honest and fully describing the situation.

The major message from postmortem document is to let others learn quickly and if anytime in the future the similar or the same Stone will appear, colleagues should be ready to help and solve it much quicker.

You don’t have to write the document for every Stone which you’ve worked on. Maybe BIG and MIDDLE Stones are good candidates to save lessons learnt as they have significant impact on your company.