Add retrospective template.

work-process.md

@@ -188,6 +188,49 @@ After each sprint, we do a retrospective. We think about:
 We also add a note on how many Story Points we assigned, how many were done and the distribution between the departments and types of User Stories.
 
 Last Retrospective agenda should be going through the [cancellation reasons of our VIP users](https://github.com/niteoweb/support/blob/master/EBN/cancellation-analysis.md) (Agency plan and above). Since they are our primary customers, we want to know why they're leaving and see if there are any actionable reasons.
+
+Before each Retrospective scrum master creates a new issue with the following content:
+
+```
+# Retrospective Checklist
+
+- [ ] Decide who is taking notes and who will write the report (usually this is the scrum master).
+- [ ] Start recording the meeting.
+- [ ] Go through the demos.
+- [ ] Every Nitean talks about "What was good", "What was bad" and "What we could do differently".
+- [ ] Go through the user cancelation list.
+
+# What went well during the sprint?
+...
+
+# What went wrong during the sprint?
+...
+
+# What could we do differently to improve?
+...
+
+# Other comments.
+...
+
+Planned:
+
+- Committed Story Points: X
+- Marketing & Operations: X
+- Feature: X
+- Bug & Cleanup: X
+
+Done:
+
+- Committed Story Points: X
+- Marketing & Operations: X
+- Feature: X
+- Bug & Cleanup: X
+
+[Screenshot of the burndown chart]
+
+```
+
+This template serves as a checklist for Sprint Retrospective. After the meeting scrum master briefly writes a report and this template helps him with that.
 
 ## Scrum