User talk:Richardatherton

Welcome to Agile Retrospective Resource Wiki! We hope you will contribute much and well. You will probably want to read the help pages. Again, welcome and have fun! Robbowley (talk) 06:18, 11 May 2016 (PDT)

“Guess Who?” a retrospective from a different perspective

A guest post from Dr Marcin Remarczyk [1] on a new retrospective technique encouraging empathy…

Retrospectives are increasingly a common element of agile ways of working and part of every Scrum Master’s toolbox. And whilst their effectiveness and benefits are widely recognized, it is worth experimenting with different flavors of applied formats and facilitation techniques. In this blog, I share a recent experience from retrospectives conducted with a team in the media industry where the idea has been to look back from someone else’s perspective.

JUST IN CASE YOU HAPPEN NOT TO BE AN AGILE EVANGELIST …

Those of you who are long-time converts and religiously follow the Agile Manifesto, are well aware of the 12th Agile Principle: “At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly”. Typically, Agile teams use retrospectives to continuously improve their ways of working. The key aspects of a retrospective are to “inspect” – how the latest iteration or “Sprint” (mini-phase of perhaps a few weeks) has gone; and to “adapt” – to decide on what and how they want to improve their processes. The facilitator must be equipped with a repertoire of techniques, recognizing which are most suitable in light of the current state of the team.

What I want to share with you touches exactly upon this area. I recently facilitated a retrospective with a medium size team in the media industry. Whereas often retrospectives are centered on the “how I felt”, “what did I like” and “what did I not like”, I have enriched this format by shifting the perspective from “the self” to “others”.

NAME FROM A HAT

Essentially, the challenge was to put ourselves into the shoes of another colleague. To achieve this, I asked the team to put their name on a Post-It note and throw it into a hat. Then, with the hat full of names, draw one Post-It out. Naturally this meant that everyone in the team drew either a colleague or themselves. To keep it simple, I asked the participants to imagine being the person they drew and think about that person’s experience in from two perspectives, namely “what went well” and “what could have been better”. And for each of these two, they had to write down two to three things on separate Post-Its. This could be anything from “felt fully integrated within the team and developed myself further” to “felt under-utilised throughout the Sprint”. Completing this task within 5-10min, each team member placed their stickies notes on a board divided into the two above categories, but not mentioning the individual’s name they were introducing. Once described, I then asked the team to “Guess Who?” the person was represented by the Post Its. Once each individual was revealed, he or she could validate, disagree or add any comments to complete the picture. After that we clustered the Post-Its into common themes, and, in a final step, translated these clusters into actionable tasks with owners.

THE INCREASED POWER OF TALKING ABOUT EACH OTHER

Having spoken about the mechanics to allow you to replicate this approach and test it with the teams you work with, it is worth highlighting the benefits of this way of facilitating a retrospective. It boils down to the emotional effects of hearing from others about how we felt. It creates the right tension between seeing our own view validated and a possible gap between what we feel and how we appear to others. Learning from this can be substantial if team members open up fully to what they hear. We experience that others do notice us and our feelings which is likely to increase the team cohesion and inclusiveness. We feel heard and supported which is important especially when dealing with the challenges we face. It can also help us to become more self-aware by recognising that sometimes our behaviors or simply our body language can send signals which may discourage others and/or create a negative aura around us. In particular, if not intended, we can take measures to address these behaviours and learn to deal with our obstacles in a more positive and pro-active manner, thus reducing the effect on other team members. But why don’t you go ahead and use your next retrospective to try this out yourself.

Dr Marcin Remarczyk is a London-based Business Psychologist and an Associate Director at Cognizant Business Consulting[2].

A Lego Retro

How do you know you’ve made it as a Change Agent? When your client starts paying you to play with Lego 😉

On serious note, I recently a facilitated an Agile Retrospective with Lego as the medium. (A retrospective is a regular meeting that a project team holds to discuss what has been successful over a prior time period, what could be improved, and how to incorporate the successes and improvements in future.)

The team had just completed a two-week Sprint (set period for a iteration). I kept it simple with the following format:

LEGO SERIOUS PLAY RETROSPECTIVE FORMAT

1. Intro and warm-up model (10 mins) 2. Build a model to represent the last Sprint (10 mins) 3. Share about your model (10 mins) 4. Build a model to represent your ideal Sprint (10 mins) 5. Share about your model (10 mins) 6. What can we commit to as individuals or as a team to do differently based on what we’ve learnt? (10 mins)

WHAT DID I LEARN?

Rasmussen[3], a leading expert on Serious Play, describes how the scientific literature holds that the primary motivation for play is emotional. One stark example of this emotional quality of play was one fairly senior team member built a beast dragging weights on lengths of string. She shared how she had felt burdened over the last Sprint (previous two-week period), how she felt that she’d carried the whole team. I had never experienced this individual open up with anything like such depth.

It brought to mind those adult cartoon shows such as Family Guy. It seems that when we represent our world as childish or symbolic figures, with that degree of separation, we can handle much darker topics. Head on, if I’d asked this individual to share how they were feeling (such as with the ‘Glad, Mad, Sad’ format), I doubt we’d have got such a profound response.

Also, by us studying the Lego model, and not just listening to the person’s words, I felt that we could feel their pain more easily – it made it easier to empathise.

WHAT TO TRY NEXT TIME?

In this version of the Retro, each team member created their own individual ‘Ideal Sprint’. In future, I’d like to experiment with teams creating a shared model of an ideal Sprint.

“Guess Who?” a retrospective from a different perspective

A guest post from Dr Marcin Remarczyk [4] on a new retrospective technique encouraging empathy…

Retrospectives are increasingly a common element of agile ways of working and part of every Scrum Master’s toolbox. And whilst their effectiveness and benefits are widely recognized, it is worth experimenting with different flavors of applied formats and facilitation techniques. In this blog, I share a recent experience from retrospectives conducted with a team in the media industry where the idea has been to look back from someone else’s perspective.

“Guess Who?” a retrospective from a different perspective

A guest post from Dr Marcin Remarczyk[5] on a new retrospective technique encouraging empathy…

Retrospectives are increasingly a common element of agile ways of working and part of every Scrum Master’s toolbox. And whilst their effectiveness and benefits are widely recognized, it is worth experimenting with different flavors of applied formats and facilitation techniques. In this blog, I share a recent experience from retrospectives conducted with a team in the media industry where the idea has been to look back from someone else’s perspective.

JUST IN CASE YOU HAPPEN NOT TO BE AN AGILE EVANGELIST …

Those of you who are long-time converts and religiously follow the Agile Manifesto, are well aware of the 12th Agile Principle: “At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly”. Typically, Agile teams use retrospectives to continuously improve their ways of working. The key aspects of a retrospective are to “inspect” – how the latest iteration or “Sprint” (mini-phase of perhaps a few weeks) has gone; and to “adapt” – to decide on what and how they want to improve their processes. The facilitator must be equipped with a repertoire of techniques, recognizing which are most suitable in light of the current state of the team.

What I want to share with you touches exactly upon this area. I recently facilitated a retrospective with a medium size team in the media industry. Whereas often retrospectives are centered on the “how I felt”, “what did I like” and “what did I not like”, I have enriched this format by shifting the perspective from “the self” to “others”.

NAME FROM A HAT

Essentially, the challenge was to put ourselves into the shoes of another colleague. To achieve this, I asked the team to put their name on a Post-It note and throw it into a hat. Then, with the hat full of names, draw one Post-It out. Naturally this meant that everyone in the team drew either a colleague or themselves. To keep it simple, I asked the participants to imagine being the person they drew and think about that person’s experience in from two perspectives, namely “what went well” and “what could have been better”. And for each of these two, they had to write down two to three things on separate Post-Its. This could be anything from “felt fully integrated within the team and developed myself further” to “felt under-utilised throughout the Sprint”. Completing this task within 5-10min, each team member placed their stickies notes on a board divided into the two above categories, but not mentioning the individual’s name they were introducing. Once described, I then asked the team to “Guess Who?” the person was represented by the Post Its. Once each individual was revealed, he or she could validate, disagree or add any comments to complete the picture. After that we clustered the Post-Its into common themes, and, in a final step, translated these clusters into actionable tasks with owners.

THE INCREASED POWER OF TALKING ABOUT EACH OTHER

Having spoken about the mechanics to allow you to replicate this approach and test it with the teams you work with, it is worth highlighting the benefits of this way of facilitating a retrospective. It boils down to the emotional effects of hearing from others about how we felt. It creates the right tension between seeing our own view validated and a possible gap between what we feel and how we appear to others. Learning from this can be substantial if team members open up fully to what they hear. We experience that others do notice us and our feelings which is likely to increase the team cohesion and inclusiveness. We feel heard and supported which is important especially when dealing with the challenges we face. It can also help us to become more self-aware by recognising that sometimes our behaviors or simply our body language can send signals which may discourage others and/or create a negative aura around us. In particular, if not intended, we can take measures to address these behaviours and learn to deal with our obstacles in a more positive and pro-active manner, thus reducing the effect on other team members. But why don’t you go ahead and use your next retrospective to try this out yourself.

Dr Marcin Remarczyk is a London-based Business Psychologist and an Associate Director at Cognizant Business Consulting[6].