\uD83D\uDCCB Overview
Reflect on past work and identify opportunities for improvement by following the instructions guidelines for the Retrospective Play.
A retrospective should be run at the end of each product development sprint.
| Page Properties | ||||||
|---|---|---|---|---|---|---|
|
Results
Were the results as expected?
Were the KPIs hit?
What key actions led to the outcomes being as desired, or not as desired?
Product process and guidelines
Were the guidelines followed? Why or why not?
What worked from the guidelines and process? What didn’t?
Note:
If results were less than desired and guidelines were not closely followed, it will be recommended that next sprint the team follows the guidelines closely. Impact on results will be measured
If results were good and the guidelines were not closely followed, the process that was followed should be recorded so we can learn from this and improve our own process and guidelines
\uD83D\uDCAD Retrospective
| Info |
|---|
Add your Start doing, Stop doing, and Keep doing items to the table below. We'll use these to talk about how we can improve our process going forward. |
Start doing | Stop doing | Keep doing |
|---|---|---|