How to continuously improve your team dynamics using Retrospectives?

One of the key constructs of Agile is imbibing the 'Kaizen' model of continuous improvement and customize it for the product side of the delivery and the process side of team environment. The best part of Agile is using 'Retrospectives' at its core where teams use the formal meeting to understand what can be done better and what we are doing well.

This session is to harness other ways of conducting or facilitating retrospectives that would make it even more engaging and deepen the sense of purpose along with the relationship established with the team.

First one would be to use Johari Window's construct to widen the shared understanding and reduce the blindspots for not only the team members  individually but reduce the vulnerabilities within the team.

Second one is to use Futurespectives to set a vision for the product/program using design thinking tools and elevate the understanding of the  goals and objectives in order to bring alignment between business, IT and operations stakeholders.

Third part of the workshop would be to identify anti-patterns in agile practices and how to smell the first whiff and nip those practices quickly. This would be done using retrospective as a tool to identify the root cause for anti-patterns

 
1 favorite thumb_down thumb_up 1 comment visibility_off  Remove from Watchlist visibility  Add to Watchlist
 

Outline/structure of the Session

All the three exercises would use the structure of understanding how to use the tool, practical tips to use them and participants would be given a few scenarios in the public domain and expect to apply the techniques.

Detailing only Johari Window for ease of understanding. At the beginning of the session ask the groups to divide themselves in a group of 8 each

Johari Window is psychologist's powerful tool to get a window within the thought process. To bring the same model into a retrospective, there are several forms it which it can be run.

A. Identify a phrase that they can easily align with. And they could explain the reasoning for it <-- All team members identify for each other also.

B. Qualitatively talk through the strengths and weakness at individual, team and product level from each team members needs

Present a project situation and ask each group using the given Johari Window Retro tool kit to provide their thoughts and ask one of the team members to summarize in the end.

Learning Outcome

Following are the learning outcomes

1. Provide a sense of clarity of what is the purpose of doing retrospective

2. Help all the participants to be geared with the knowledge of various techniques that can be applied

3. Only way we can change is by improving our product, process, team and self. Reflect on which is the main focus on each retrospective session and make the most use of this session in their Agile DAY.

Target Audience

Agile practitioners, Business Analysts, Product Owners, Development managers, Leaders

schedule Submitted 9 months ago

Comments Subscribe to Comments

comment Comment on this Proposal
  • Ravi Kumar
    By Ravi Kumar  ~  9 months ago
    reply Reply

    Hi Gayathri,

    I am a little confused going through the outline and the learning outcomes. I think there's potential if you can share experience and techniques on using Johari window and connecting that to agile principles for driving effective retrospectives.

    1. Provide a sense of clarity of what is the purpose of doing retrospective >> I think most participants attending Agile India know the purpose of the retrospective. Not an outcome

    2. Help all the participants to be geared with the knowledge of various techniques that can be applied: The outline does not talk about the various techniques. Can we just limit this to Johari window

    3. Only way we can change is by improving our product, process, team and self. Reflect on which is the main focus on each retrospective session and make the most use of this session in their Agile DAY: Not an outcome.

     

    Can you please update the proposal with links to some of the video/talks and any write up on this topic?

     

    Best,

     

    Ravi

     

    Best,

     

    Ravi


    • Liked Vishweshwar Hegde
      keyboard_arrow_down

      Vishweshwar Hegde - Mindfulness: Cultivating Agile Minds

      20 mins
      Talk
      Intermediate

      Agility starts with Mind. It’s about open, curious, energetic mind constantly looking for doing better things and in better ways. Such Agile Minds manifest in proactively sensing market/customer opportunities/needs early, quickly adopting to changes  to create new value in the changing contexts, continuously learning, exploring & experimenting new things. It requires courage, self-drive and taking people along. If we notice, all these characteristics are distilled in Agile Values & Principles.

      But how to develop Agile Minds? Typically our education system and corporate trainings  are predominantly IQ oriented; whereas Agile Mind is about Emotional Intelligence (EQ) – self awareness, self regulation, self motivation and empathy. EQ is an essential ingredient for a culture of self-organizing, collaboration and servant leadership – which are the tenets of good Agile culture. Mindfulness is a practical & effective toolset to cultivate EQ and create Agile Minds. 

      Being a Mindfulness practitioner, this talk will cover my experiences of consulting & coaching on Mindfulness in organizations driving Enterprise Agility.