We are currently helping out at a client, and I found myself in the ScrumMaster role ๐Ÿ™‚ It’s been a while! They run one week sprints and their teams are 1 or 2 people and they change every month or so. This seems to work for them on the most part. I need to run a retrospective for two teams at the same time. One team of 2 people and one team of one. As I haven’t been able to clone myself as yet, this needed to happen together, but allow each team to reach their own improvement point.

The Plan:




How did this work in reality?

The person on the team of one was off sick, so the retro ended up being just for one team of two – this made it a bit easier to facilitate and interact with the team.

The rest of this feedback came from the Plus/Delta exercise. It shows how important it is as a facilitator to get feedback from your team.

This team usually does the same retro every week (same activities), so the different activities felt a bit weird to them. I’m a bit surprised I fell into this trap, I do know better ๐Ÿ™‚ If your team is used to doing something only change one activity at a time, changing everything makes them feel a bit unsettled and uncomfortable.

They enjoyed the first exercise (Check In) but felt it didn’t lead anywhere – so perhaps a Diverge section that flows from it will be better.

They enjoyed the questions as it made them really think. They did miss not having a timeline activity to remind them of what happened over the week of their sprint.

They liked getting to one action that is very solid and they know will do. They are used to having a list of goals they want to achieve during the sprint.

Thank you Concetta and Wilhelm!