Building a Team Backlog: The Power of Retrospectives
- 1. AT7 Session 6/6/2013 2:15 PM "Building a Team Backlog: The Power of Retrospectives" Presented by: Kanchan Khera & Bhuwan Lodha McKinsey & Co. Brought to you by: 340 Corporate Way, Suite 300, Orange Park, FL 32073 888‐268‐8770 ∙ 904‐278‐0524 ∙ sqeinfo@sqe.com ∙ www.sqe.com
- 2. Kanchan Khera McKinsey & Company A portfolio manager at McKinsey & Company and an avid agile enthusiast, Kanchan Khera believes that agile is a way of life and a very powerful concept with the pure intent of making successful products and happy people. She sees huge untapped potential in agile that could change the way we think and work. Kanchan has extensive experience with agile teams in varied roles, has spoken at conferences worldwide, and is considering writing a book about her journey building high performing teams. Kanchan enjoys painting, listening to music, traveling, and problem solving. She hates doing daily chores or following routines. Contact her at @k_khera. Bhuwan Lodha McKinsey & Company A product manager at McKinsey & Company, Bhuwan Lodha is a certified Scrum Product Owner and Pragmatic Marketing certified product manager. Bhuwan has extensive experience working with agile teams and projects of various sizes at companies like SAP and Nokia. Throughout his career, he has had the opportunity to build great teams and market winning products. Bhuwan says that “Being agile is similar to having common sense in the modern world—it's essential but often underrated.” A speaker at agile conferences worldwide, he is working on a book about high performing teams and agility. Bhuwan enjoys reading, traveling, and following trends in the hi-tech industry. Contact him at @bhuwan.
- 3. Building a Team Backlog: The power of retrospectives Bhuwan Lodha | Kanchan Khera @bhuwan | @k_khera We are here to share our experiences on building team backlogs And making retrospective sessions enjoyable and effective And would love to learn from your experiences as well… 1
- 4. Retrospective Looking back on, or dealing with past events or situations <another contextual statement here> y pre-spectives <may be another slide on p p comes here> 2 ONE WORD 3 Give us the ONE WORD that comes to your mind about retrospectives (in your teams)
- 5. 4 Watch video at https://vimeo.com/49589446 Most of us understand the IMPORTANCE of retrospectives… So what’s missing? 5
- 6. So here is our take on the key challenges.. 1. Recipe is unclear 2. Spice is missing 3. I the Kitchen i ht? 3 Is th Kit h right? 7 Challenge #1 – Unclear Recipe 8 No clear framework for retrospectives
- 7. Introducing a new framework Choose your style Team Backlog Great Team Action items Continuous Improvement 9 Build a team backlog for a great team Retro # Action Item Owner Status Effort Impact 1 1 Setup build monitor Rahul Impediment Large Medium (8 pts) 1 2 Block weekly standing time with sponsor team Veena Pending Small Large (12 pts) 1 3 Complete first 4hr training session on Selenium Rahul, Pete Done Large Large (12 pts) Sprint 3 2 4 Get better headset for Veena Biju Done Medium Medium (5 pts) Sprint 3 1 5 Set up leave calendar for the team Abhishek Done Small Medium (5pts) Sprint 4 2 10 Priority # 6 Have team lunch Rahul Pending Small Medium (5 pts) Average velocity of impact : (12+5+5)/2=11 Impact sprint
- 8. Measuring impact: Great Team s Team’s journey from Good to Great 25 20 15 Impact 10 5 Good 0 Sprint 1 Sprint 2 Sprint 3 Sprint 4 Sprint 5 Sprint 6 11 Working with a team backlog Who owns the backlog Team backlog is owned by somebody on the team or a scrum master - keeps track of progress - helps team steer action items to closure - helps team prioritize Leveraging Retrospectives - Every retro has first 5 min dedicated to talk about the action items it - And last 5 min to plan and prioritize on next action items identified 12
- 9. Working with the team backlog Play it like a game Start early and set a rhythm Have clear roles, who is doing what Make rules (sample) - No Laptops - No two retrospectives sound the same - Only on Fridays - On Time or Ice Cream 13 Working with the team backlog The 5 Whys technique to get clear action items Flurry of leaked b Fl f l k d bugs Technical issue Very little automation testing Lack of skills (selenium) Lack of training for Selenium No one talks about trainings 14 Manager does not believe in trainings People issue
- 10. Challenge #2 We do it the same way.. over and over again y g SPICE is missing… 15 Here are a few reference spices I hate.. I love.. Rate yourself Happiness meter Hey, Stranger! Focus Focus Focus ! Appreciation only What did I learn? The Big Picture 16 Is this our best?
- 11. I Hate.. I Love.. Text Suitable for teams that have a lot of emotions which do not come out in traditional retro sessions 17 Rate Yourself Text Suitable for teams which are complacent and need to define the next level 18
- 12. What did I learn? Text Suitable for teams which are too involved in the project work. Need to get the spirit of learning imbibed 19 Focus Focus Focus Text Suitable for teams which need to focus deeper on certain topics (For example, testing, collaboration etc.) 20
- 13. What’s your favorite flavor? 21 Challenge #3 The RIGHT Kitchen Retrospectives do not fly far unless the organization nurtures a culture that supports them 22
- 14. All this works because we have teams with motivated individuals, wanting to take on a journey from being Good to GREAT… THANK YOU… bhuwan_lodha@mckinsey.com kanchan_khera@mckinsey.com 23