DAKI Sprint Retrospective Format
We continue to visit different sprint retrospectives, with this week checking out the DAKI retrospective format.
What is the DAKI sprint retrospective?
This retrospective format is a great way to identify specific behaviors, patterns, and activities that your dev team feels should be dropped, added, kept, or improved. This format is a great way to understand any differences in the perspectives of team members and help to get everyone on the same page. It can help your team to gain insight into how things can be improved or changed to re-energize your team and refocus your goals.
The four categories in this format are:
● Drop: What can be left behind in the coming projects? What isn’t working well and needs to be dropped?
● Add: As a project goes on, new challenges will arise. This calls for new ideas and innovative action plans to keep up. These are things that should be added to fill in for what has been dropped.
● Keep: These are things working well and should continue to be done during the course of a project.
● Improve: These are things already being done, but that can be tweaked to increase productivity. Things that can be improved upon, but not completely dropped.
In order to hold this type of retrospective meeting, a team can meet (virtually or in person)and brainstorm ideas for each of the above categories. They can then group those ideas into categories and vote on each idea, taking into account that some ideas will be repeated and that those ideas will probably be most important. Then, have discussions on each of the important ideas for each category and create a strategic plan to implement them.
When should the DAKI agile retrospective format be used?
This is a great retrospective format to use toward the end of a project so that you have more to reflect on and to understand the progress that has taken place from the beginning of the project to the DAKI sprint retrospective meeting.