Continuous Improvement Template

During my work as a Scrum Master and Agile Coach I attended lots of retrospectives by various teams. One thing I noticed quite a lot is that team members struggle to recall events that happened during the Sprint. This is even more the case for teams that are overburdened or stressed. This is quite a tragedy: Especially those teams could profit from changes. Changes in how they accept work, allocate it within their team, keep track of it and protect themselves against overload. However, it can’t be in the interest of the organization to have overloaded teams. In the long term they lack predictability of velocity not only due to illness and signs of burnout, but also because of technical debt that’s easy to dismiss if you have to take shortcuts all the time. A peak of assumed high performance is followed by a vale of tears.

However, those teams are in a vicious cycle as long as they don’t take a break and agree on real improvements. It’s not just that those teams are too busy to improve. For our brain it’s hard to notice and remember things while we are in a rush or act in panic. It takes calmness to be mindful.

Do you know such a team? Or are you even part of such a team or their Scrum Master? Here’s a suggestion on how to change this situation. It’s easier to keep track of things if you get them out of your head. To-do lists are a good example. This in mind, I created the Continuous Improvement Template. Maybe you want to start using it on your own. Or maybe you want to suggest in your next retrospective that everyone on the team starts using it. At least for one Sprint to validate the results. Download, print and hand it to your team members. Don’t forget to provide a pen, too. Now every time something noteworthy happens, even small things that could matter, take a short note in one of the columns that are:

  • Keep (doing something)
  • Less (of something)
  • More (of something)
  • Stop (doing something)
  • Start (doing something)

After jotting it down, you can go back into busy mode. It’s out of your head now. Next time you’re participating in your team’s retrospective, take your Continuous Improvement Template with you. Reflect on things that happened. Together, agree on a first little step to improve the situation. After that, print a fresh copy of the Continuous Improvement Template and keep track of events that verify the effectuality of your change or whatever comes across that could be an input for your next retrospective.

You can download the template here or view it below.

© 2016 by Thorben Egberts, – This work is licensed under the Creative Commons Attribution-NonCommercial-ShareAlike 4.0 License (international).

Related Posts

Warum vs. Wofür: 5-Why

Die 5-Why-Methode: Wo sie aufhört zu funktionieren und was stattdessen nützlich ist.

Mahara Hui 2017

Kurzbericht von der Fachtagung für Portfolioarbeit im Barcamp-Format.

1. Norddeutsches ScrumMaster-Gathering in Hannover

Kurzbericht von der Erstauflage des Events (nicht nur) für ScrumMaster.

Is X Allowed in Scrum?

Three Questions to Facilitate Decisions

No Product Owner, No Sprint Review?

What to Do, If There Is No Product Owner for the Sprint Review

Agile Building Games @ Spartakiade

LEGO Serious Play and LEGO Agile Games auf der Spartakiade in Berlin

Moving the Blog

I'm moving my blog from Ghost to Jekyll.

Unread Email Count

My most reliable personal stress metric.

Scum and FrAgile

Feel free to contribute with hashtag #Scum and #FrAgile.

Organizational Culture

What is organizational culture and why you should care about it.