Skip to main content
There’s a lot of talk about transformation and some metrics around what we are lacking and need to do better. Do we also know what we do well and the good things about our work processes and environment that we want to keep? I’m concerned that if we don’t diagram this as a spectrum we risk running over those good things that we do in the course of transforming.

Running agile retrospectives at team levels could provide us with this feedback


DAKI – drop, add, keep, improve | Fun Retrospectives

DAKI is a great data gathering to foster the thinking around practices and the value the team get from it. It helps team members to understand each other ...

KALM – Keep, Add, More, Less | Fun Retrospectives

Activities and ideas for making agile retrospectives more engaging ... KALM (Keep, Add, More, less) is a retrospective activity that fosters the conversation to the ... Keep – something the team is doing well and you recognize the value on it.

5 Tips to Keep Getting Value from Agile Retrospectives - Ben Linders

Jan 21, 2016 - People often ask me what to do to prevent that teams get bored when doing agile retrospectives for a longer period. The short answer is: Make ...

Comments

Popular posts from this blog

Many organizations get vertical and horizontal confused. Their 'verticals' cross-cut the vertical stack and are really 'horizontals'.        scrum-teams-vs-traditionally-organized-teams

npackd for the masses

For the developer masses stuck on the newer flavors of Windows - npackd shows some promise. An apt-get like interface for installing/tracking typical tools on your workstation.  Silently, checks SHA1 and tracks versions for easy update/rollback.  Repository is growing. Finds already installed packages and can scan for additional.