One of the strength of Agile beyond sprint planning and iterations is retrospectives.
During retrospectives engineers 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.
This is no more a problem. With Keypup Retrospectives, engineers are finally able to provide feedback at their own pace, without interrupting their work.
> Schedule your first retrospective
Retrospectives should be scheduled at regular intervals, preferably along each sprint.
From the side menu, head to Retrospectives then go to the Scheduling tab.
Switch the retrospectives to enabled then fill in your scheduling preferences.
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 engineers 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!
> It's time for your retrospective
When a retrospective starts each engineer 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. Keypup does not provide engineer-level granularity in retrospective reports.
Each section on the feedback page is saveable. One does not have to fill their retrospective in one go and can do it at their own pace.
Feedback is editable until the retrospective closes. One can always come back and change their ratings/comments if needed.
> 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.
The full report fleshes out the overall mood of the team and provides a break down for each Core Vital.
The Overall Satisfaction and Core Vitals are rated from
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. So if you feel like you need inspiration to improve a given project, simply look at past retrospectives and you should get plenty of ideas!