Retro Masala


Published on

Published in: Technology
1 Like
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Retro Masala

  1. 1. RETRO MASALA (Experience report) Agile Cambridge 2012Bhuwan Lodha | Kanchan Khera @bhuwan | @k_khera
  2. 2. We are here to share our experiences on making retrospectives enjoyable and effective And would love to learn from your experiences as well…1
  3. 3. Give us the ONE WORD that comes to your mind about retrospectives (in your teams)2
  4. 4. Watch video at
  5. 5. Most of us understand the IMPORTANCE of retrospectives… So what’s missing?4
  6. 6. Watch video at
  7. 7. So here is our take on the key challenges.. 1. The Spice is missing 2. Recipe is unclear 3. Is the Kitchen right?6
  8. 8. Challenge #1 We do it the same way.. over and over again MASALA is missing…7
  9. 9. Here are a few MASALA references I hate.. I love.. Rate yourself Happiness meter Hey, Stranger! Focus Focus Focus ! Appreciation only What did I learn? The Big Picture8 Is this our best?
  10. 10. IHate.. I Love.. Text  Suitable for teams that have a lot of emotions which do not come out in traditional retro sessions9
  11. 11. Rate Yourself  Text  Suitable for teams which are complacent and need to define the next level10
  12. 12. What did I learn?  Text  Suitable for teams which are too involved in the project work. Need to get the spirit of learning imbibed11
  13. 13. Focus Focus Focus  Text  Suitable for teams which need to focus deeper on certain topics (For example, testing, collaboration etc.)12
  14. 14. What’s your favorite flavor?13
  15. 15. Challenge #214 No clear framework for retrospectives
  16. 16. Introducing a new framework Choose your style Team Backlog Great Teams Action items Continuous Improvement15
  17. 17. Start early: Start retro from sprint 0, as early as possible Set a Rhythm Have clear roles, who is doing what Play it like a game, make clear rules (sample) - No Laptops - No two retrospectives sound the same - Only on Fridays - Speak up or Dance - On Time or Ice Cream16
  18. 18. Snapshot of a team backlog Order Action Item Owner Status 1 Setup build monitor Rahul Impediment 2 Block weekly standing time with Veena Pending sponsor team 3 Complete first 4hr training session Rahul, Pete Done on Selenium 4 Get better headset for Veena Biju Done17
  19. 19. The 5 Whys technique Flurry of leaked bugs Technical issue Very little automation testing Lack of skills (selenium) Lack of training for Selenium No one talks about trainings Manager does not believe in trainings People issue18
  20. 20. Challenge #3 The RIGHT Kitchen Retrospectives do not fly far unless the organization nurtures a culture that supports them19
  21. 21. A Case Study About the team Team size: 5 • Highly skilled • Not aligned • Low collaboration • Co-located About the product: • Not launched since 2 years • Highly demanding sponsor • Legacy code20
  22. 22. Retrospectives in this team • Happened every 2 weeks • No Action points were noted • Same points were discussed in almost every retro – No change • The purpose of doing retrospectives was unclear • PO or SM conducted the retrospective21
  23. 23. How we made it effective and interesting • Introduced team backlog- action items translated into change • Conducted different retrospective flavors I love-I hate, Appreciation only, Rate yourself • Instead of “what went wrong in last sprint” we asked “most boring thing which you have done in last sprint” • Withheld trust and listened to every feeling22
  24. 24. All this works because we have teams with motivated individuals, wanting to take on a journey from being Good to GREAT… THANK YOU… kanchan_khera@mckinsey.com23