After building the Agile board, we thought about expanding the Agile toolbox for developers. And one of the strength of Agile beyond sprint planning and iterations is retrospectives.
During retrospectives developers gather and discuss how the overall development flow is going and highlight the pain points that should be worked on in order to improve development efficiency or make their day-to-day life easier.
Organizing retrospectives can be a bit of pain as everyone need to take time off their work to sit down and discuss. Which is why teams don't do it as often as they should.
No more lengthy retrospective meetings. We are thrilled to introduce Keypup Retrospectives.
Developers are finally able to provide feedback remotely, at their own pace, without interrupting their work. If you want to know how remote retrospective works using Keypup, read on.
1. Schedule your first retrospective 📆
Retrospectives are easy to prepare, easy to run. You are allowed to schedule retrospectives at regular intervals, preferably along with each sprint.
The scheduling options are as follow:
- Retrospective start date: This is the date and time for the first/next retrospective.
- Frequency of occurrence: How often should retrospective happen. You can select every 1/2/4/8 weeks at present. You should align the frequency with your sprint duration.
- Feedback window: The maximum amount of time team members have to submit their feedback from the moment a retrospective is started.
It is important to note that the frequency of occurrence also drives the reporting period over which retrospectives apply. If you select 2 weeks then when a retrospective starts, we will ask developers to provide feedback on all pull requests which were merged in the 2 weeks preceding the retrospective.
In case of doubt, feel free to review the calendar preview located below the scheduling settings.
For each upcoming retrospective, it will highlight the start date, when the feedback closes and the period covered.
Once you are happy with your schedule, just hit Save and you will be set!
2. It's retro time ⏰
When a retrospective starts, each developer receives an email or chat notification asking them to fill their retrospective.
They can also access their retrospective by clicking Retrospectives on the side menu then Fill on the current retrospective.
In both cases, they will access a page displaying feedback forms for all pull requests they have authored and allowing them to quickly comment and give opinions on specific topics related to their work.
Feedback is anonymous. So everybody is free to speak out and provide valuable feedback. Keypup does not provide developer-level granularity in retrospective reports.
Each section on the feedback page is saveable. No rush here, you don't have to fill your retrospective in one go you can do it at your own pace.
Feedback is also editable until the retrospective closes. One can always come back and change their ratings/comments if needed.
3. Retrospective results 🥁
When a retrospective closes, an email is sent to the whole team with some highlights.
From there, you can click the embedded link to access the full report on Keypup.
One can also access the results by clicking Retrospectives on the side menu, then View Results on the last retrospective. It's time to check the result dashboard!
The full report fleshes out the overall mood of the team and provides a break down for each Core Vital. This is what a full report looks like 👇 Looks nice, isn't it?
The Overall Satisfaction and Core Vitals are rated from -100 to 100. Scores below 0 indicate a generally unfavorable opinion while scores above 0 indicate a more favorable one.
Below the statistics you will also find a summary of comments provided by the team, grouped by mood.
The history of retrospectives is always available for later. So if you feel like you need the inspiration to improve a given project, simply look at past retrospectives and you should get plenty of ideas.
We built this new feature for all the remote teams that struggle to prepare retrospectives and collect usable data. We hope that this feature will enable teams to work more efficiently and to focus more on their development priorities. Have a try and let us know what you think.