Behind the scenes of retrospectives

schedule Nov 21st 10:45 AM - 12:15 PM place More hands-on learning (Pyxis Room)

Ben Linders said: "if you want to solve the problems that you are having, and deliver more value to your customers, you have to change the way you do your work. That is why agile promotes the usage of retrospectives: To help teams to solve problems and improve themselves!" 

In this workshop I will walk you through the reasons, concepts, phases, tips and tricks of agile retrospectives and everything that happen behind the scenes. We'll share the space and learn together how to make this event a great one in a practical, engaging, fun and interactive manner.

Are you ready for the challenge?  

 

 
2 favorite thumb_down thumb_up 4 comments visibility_off  Remove from Watchlist visibility  Add to Watchlist
 

Outline/structure of the Session

Intro

Section one (The Why):

- Context

Section two (The What):

-  What about it? What it takes? What we need to make them stick?

- Phases of an agile retrospective

Section three (The How):

- Designing + Prepare

- Running an agile retrospective

- Documenting + sharing

- Inspecting + adapting

Outro

Learning Outcome

1) What an agile retrospective is all about

2) A model or two to design and prepare retrospectives

3) One or two techniques to facilitate retrospectives with teams

4) One or two ways about running retrospectives with teams

5) One model or two to help you document and share the

6) Tones of questions and a lot of curiosity about the subject

Target Audience

Lean/Agile practitioners

schedule Submitted 1 year ago

Comments Subscribe to Comments

comment Comment on this Proposal
  • Cherifa
    By Cherifa  ~  11 months ago
    reply Reply

    Hello

    can you tell me what is so special about this presentation and how can you convince me it is not the same as the ones I heard before on retrospective. people tend to repeat the same thing over and over again. I want to know what are the key differenciators for your presentation to be exceptional and help me get some tips on how best to improve the way I am taking a team through retrospective.

    • Jesus Mendez
      By Jesus Mendez  ~  11 months ago
      reply Reply

      Hi Cherifa, 

      It took me a while to get back to you given some personal transitions but here I'm to answer your question back. I don't think that I need to convince you, that the workshop that I'll deliver will be different to those onces that you've already heard in the past. What I can guarantee you instead, is that I'm unique and no one explains things exactly like I do. What I will add to the equation will be my own experiences, treating agile retrospectives as a whole and not only focus on the running face of it. I will walk you guys through the Preps, During and After retrospectives, and give you some tips and tricks about how to make the best out of it for the team. The main focus of the workshop will be on how to help you help the team to keep it up and running. 

      I'll do my best, that I can promise!

      Cheers,

      Jesus 

  • Paul J. Heidema
    By Paul J. Heidema  ~  1 year ago
    reply Reply

    Sounds great! Will participants get a handout or something similar by the end of the workshop?

    • Jesus Mendez
      By Jesus Mendez  ~  1 year ago
      reply Reply

      Hi Paul, thank you for your question.

      The answer is yes, there will be. I will also offer a follow up mechanism for those participants interested in continue improving their journey.

      Cheers,

      Jesus


  • Liked Chris Murman
    keyboard_arrow_down

    Chris Murman - Things Are Broken: A Case Study In Moving Tooooooooo Fast

    Chris Murman
    Chris Murman
    Sr. Agile Consultant
    Solutions IQ
    schedule 1 year ago
    Sold Out!
    45 mins
    Case Study
    Intermediate

    “Move fast and break things.” — Mark Zuckerberg

    Mobile is no longer a hobby for companies. In that world, speed is the key. My company embraced the principle of “welcoming changing requirements, even late in development.” It’s allowed us to grow, and we have accomplished some amazing things.

    It’s also caused some challenges for teams. They felt the pain of this pace, and our clients were frustrated by delayed releases.

    This presentation describes a 3-month case study I ran to measure things like team communication, productivity, and quality while implementing Scrum for the first time. The results were convincing, and allowed us to learn what happens when you value speed more than anything else.

    I hope you’ll join me in seeing how we learned to work smarter instead of harder.

  • Liked Sue Johnston
    keyboard_arrow_down

    Sue Johnston - The Geek's Guide to People - Shifting from Output to Impact

    45 mins
    Workshop
    Beginner

    The stereotype of technical professionals as inarticulate, socially inept geniuses inventing problems to solve is unkind and inaccurate. Yet the Dilbert image persists. So do jokes like the one about the engineer sentenced to death on the guillotine, who watches the instrument of death malfunction, then tells the operators how to fix it.

    Why do people make fun of engineers and those with their mindset? Do people wired and trained to analyze and solve problems and focus on the mechanics of a situation frustrate those whose brains are wired differently? And how does the engineer’s way of dealing with individuals and interactions - that first value of the Agile Manifesto - sometimes get in the way of team collaboration and productivity?

    In this interactive session, we'll show a little empathy for engineers and other analytical folk whose neurological wiring makes them seem different from the rest of humanity. We'll also explore how those with the engineering mindset can develop their own empathy and consciously adopt behaviours that amplify their value to their teams and organizations, make them more effective leaders - and make their own lives easier by positioning themselves for understanding.

    Join Sue in a lively exploration of what can happen when engineers and technical professionals shift their mindset from solving problems to creating impact.
    You will leave this session with an appreciation of:

    • How to make your ideas meaningful to others by taking their perspective
    • How shifting your language from "What?" to "So What?" helps people connect the dots
    • Why giving up the need to be smart may be the smartest thing you ever do
    • Techniques you can use to take someone else's perspective.
  • Liked Maurizio Mancini
    keyboard_arrow_down

    Maurizio Mancini / Martin Lapointe - How to Reboot your Agile Team: The Secret Sauce!

    45 mins
    Talk
    Intermediate

    Why do so many organizations struggle to put in place mature Agile teams that can apply proper Agile principles and deliver awesome products? Some people will say, “Agile is hard” as an excuse to not do Agile or to become frAgile. Well we think we have developed the “Secret Sauce” to rebooting any Agile team that just doesn’t seem to be maturing and we want to share it with you!

    If you are thinking of scaling Agile across a large organization, then this talk is a must to attend to help ensure your teams have the right foundation. Organizations wanting to scale Agile must have a solid foundation of mature Agile teams who embrace the Agile values and have the right Agile mindset.

    Over the years, as we have done Agile transformations in different organizations, we have seen common patterns that keep repeating. The most common pattern we found in our experience is that teams are frAgile. Too many either pretend to be Agile or don’t even know Agile is not a methodology, so organizations question the value of using Agile.  Very often the confusion and frustration that comes with thinking that a team is Agile when they are not Agile, brings people right back to their old habits of command and control. Creating successful mature Agile teams is not sorcery, you need to discover the secret sauce!

    In this talk, we will reveal our secrets on how to create a successful Agile-Scrum team in 5 sprints. Attendees will learn how we applied our secret sauce as we experimented with more than 30 teams and we refined the know-how. This recipe has proven to be successful in different organizations and teams delivering different types of products. Our Creative-Destruction approach goes through a human change process we labeled The Intervention Plan. The 5 steps are:

    • Step 1: Run in the rain
    • Step 2: Thunderstruck
    • Step 3: Cry over the M&M’s machine
    • Step 4: Open-up and look at the sun
    • Step 5: Removing the training wheels

    And by using these 5 steps, attendees will discover the 5th Agile value!

  • Liked Jade Stephen
    keyboard_arrow_down

    Jade Stephen / Samantha Lightowler - From dysfunction to cross-function in 8,593 easy steps: Team building at the CBC

    45 mins
    Talk
    Beginner

    When it comes to scaling Agile, there is no one size fits all solution. Frameworks like Scrum and XP prescribe roles, events, artifacts, and rules that make it very clear how interaction should take place within a team. When we begin to add more teams to the mix, communication between teams becomes more complex. This complexity threatens to reduce our transparency and damage our culture. How can we share information, build our culture and work together, all while keeping with Agile values?

    During this session Sam Lightowler and Jade Stephen will take an in depth look at the successes and failures of CBC Digital Operations when it comes to cross-team collaboration and information sharing. We will discuss what meetings and techniques have helped us build a one-team-one-product mindset, a sense of community, and a culture of Collaboration, Learning and Improvement. We will also discuss what we have tried in the past and how learning from those experiments helped us evolve into the agile-friendly and unified team that we are today.

     
     
  • Liked Mark Levison
    keyboard_arrow_down

    Mark Levison - Agile Leadership Beyond the Basics

    90 mins
    Workshop
    Executive

    You're a Manager or Executive not a ScrumMaster - what is the role of Leadership in an Agile Organization? You've seen the Dan Pink video on Motivation and are mystified as to how to help.

  • Liked Jeff Kosciejew
    keyboard_arrow_down

    Jeff Kosciejew / Andrew Annett / Ardita Karaj / Ellen Grove / Jeff "Cheezy" Morgan / Lee Elliott / Sue Johnston - What we've learnt as Agile Coaches

    90 mins
    Case Study
    Advanced

    Join a panel of experienced Agile Coaches for a discussion and Q&A of their experiences as coaches. Each of the panelists has a different background, and a unique journey into their role as an Agile Coach. Along the way, they've each built up a wide and diverse set of skills, from their careers, interactions, and experiences. 

    What have some successes been?
    How do we even define success for ourself, as an Agile Coach?
    More importantly (and hopefully more entertaining), will be some of the lessons learned... We'll explore what was tried, but had a surprising and unexpected outcome. 
    And, we'll discuss some of the ways experienced coaches continue to learn, share, grow, and develop everyday!

  • Liked Kalpesh Shah
    keyboard_arrow_down

    Kalpesh Shah - Standup Poker: How We Hacked Our Daily Stand-Up & Our Teams Mindset !

    45 mins
    Talk
    Beginner

    One the most significant ceremony of any Agile Team is Daily Standup where the team members get together and plan for their day. But quite often the daily standup turns into a zombie status update meeting where team members come together to blurt out their updates and walk away to their desk without ever maximizing the benefit of that meet up.

    In this session I will share a case study of how we created a simple experiment that turned into Standup Poker and revolutionized our Daily Standup. This technique helped us uncover true insights of teams progress and got the team talking about strategic planning and plan to remove any impediments as a "team" on daily basis to accomplish their sprint goal and commitments.

    We learnt that when team members started using this technique, hidden impediments and dependencies started to emerge and team members organically started to re-plan and prioritize their work to accomplish the Sprint Goal. Product Owner also found great value in this technique as this helped them see the teams true progress and engage with the team to re-prioritize user stories and even take a story out of the sprint if required. Scrum Masters started to observe a trend in the confidence level over the span of the sprint and brought that information to Sprint Retrospective to discuss and brainstorm ways to improve and keep the confidence levels high throughout the sprint. The discussions and observations due to Standup poker resulted in teams committing better and more confidently during Sprint Planning and got into the rhythm of always accomplishing their sprint goal, but more importantly they started improving everyday and got into "continuous improvement" mode.

    The content, exercise and message of this session highlight the agile principles of individuals and interactions over process and tools and fostering the mindset of continuous improvement.

    In this session we will share examples, stories and experiences from trying the Standup Poker and how this simple technique converted a bunch of individuals into a TEAM !!!

  • Liked Jesus Mendez
    keyboard_arrow_down

    Jesus Mendez - IT has embraced agility ... what about the rest of the business?

    60 mins
    Experience Report
    Intermediate

    3.5 years ago Seedbox Technologies decided to embrace agile methodologies as its way to develop web based products, get them out faster, survive and thrive competition.

    It's all started in a traditional fashion:  external consultants were hired to teach employees the agile mindset and how to use agile methodologies like Scrum and Kanban when developing web based products. Project Managers got trained and became Product Owners, experienced Scrum Masters were hired to get development teams to their highest level of performance as fast as they could, developers got trained and developed experience around their team development processes, engineering managers supported agility across the company, and stakeholders directly involved in product development got invited to collaborate with software development teams through agile processes, once they got fully implemented.

    That's right, Engineering got agile quite right but by doing so:

    • What happen with the rest of the organization?
    • What about peoples mindset?
    • Is them vs Us or vice versa? 
    • Are they able to collaborate, inspect and adapt like the engineering teams and people related to agile projects do?
    • How do we get everyone in the organization to communicate when we don't share the same vocabulary?
    • How do we fill the gap and avoid old management treats get in the way of the companies transition to something bigger than just the teams?
    • Shall we wait until they realize that we all need to change or shall we help them get there?
    • How do we use are know-how to turn this mess into a big opportunity for the organization to grow?
    • Do we need help?

    Well, if this experience report gets accepted, I will share what I've learned about:

    • The challenges & flaws that we faced when transitioning from team based agility to organizational agility
    • Some of my reflections as an inside observer
    • How to use the lessons learned as a wake up call
    • What can be done to help the organization to thrive

    Let's walk together through a nurturing experience report that might ignite your sens and get you inspired to give the extra mille! 

     

  • Liked Mike Bowler
    keyboard_arrow_down

    Mike Bowler / Ellen Grove - Running with the Mob: Extreme collaboration with Mob Programming

    60 mins
    Workshop
    Intermediate

    Mob programming is collaboration taken to the extreme, eliciting the best from every member of the team. In this session, you will experience the dynamics of mob programming and learn how to use this technique successfully in your own environments.

    After mobbing with over two dozen teams, we've seen definite patterns emerge, that we'll discuss here.

  • Liked Mike Bowler
    keyboard_arrow_down

    Mike Bowler / Ellen Grove - Putting the Moose on the Table: Make your retrospectives more effective using LEGO SERIOUS PLAY techniques

    90 mins
    Workshop
    Intermediate

    In order for teams to step into high performance. it's critical that they develop the practice of having effective conversations about what is and isn't working. Yet in practice, the retrospective meeting is often the least-valued of the agile events: team members feel that their retros are boring, repetitive, and superficial.


    In this workshop, we will teach participants how to design and deliver a really useful retrospective using LEGO SERIOUS PLAY. We'll cover the basics of this powerful facilitation technique, and give advice about how to build your own SERIOUS PLAY kit using pieces easily available at the local toy store. We'll also offer practical suggestions for how to design a retro that gets everyone talking (and building), and results in the team agreeing on action.


    The participants will leave with a powerful retrospective technique that they can immediately use with their teams.

  • Liked Paul J. Heidema
    keyboard_arrow_down

    Paul J. Heidema - Vital Behaviours of Successful Scrum Masters and How to Make Them Stick

    90 mins
    Workshop
    Intermediate

    Agile failure is most felt by Scrum Masters. Why do so many fail to properly support their teams? Why do so many fail to inspire meaningful change in the level of leadership? Why do so many fail to guide transformation in their organisations?

    In this workshop, we will harness the knowledge and experience of the participants! 

    Influencer Book

    Why?
    Because everyone can contribute to the learning of the entire group. It will dynamic, full or energy, and joyful - woohoo!

    Who can benefit the most from the session and the power of harnessing the group?

    • Scrum Masters that are struggling to do this role well
    • Leaders that are not seeing the results needed for an effective Scrum team through a weak/unskilled Scrum Master
    • Agile coaches that are coaching Scrum Masters without meaningful or consistent results
    • Project managers trying to make the transition to becoming a successful Scrum Master

    This workshop will use concepts and the model from the book "Influencer"

    Prepare to work together to discover the Scrum Master vital behaviours!

    Many people are taking on the mantle of Scrum Masters across agile teams around the world. Unfortunately, many of them have come from more traditional work structures that don't develop effective Scrum Masters. There is a misconception about the purpose of a Scrum Master. Often the Scrum Master becomes the facilitator or the project manager. This has to stop. Effective leaders, agile coaches, and Scrum Masters take advantage of vital behaviours in supporting scrum masters or by building mastery within these behaviours.

    Influencer - the model

    During this workshop, participants will go through a series of exercises to identify the purpose of a Scrum Master, how we can measure success, identify potential vital behaviours, learn from others to determine the vital behaviours, and then create a sound influence strategy to enable effective Scrum Masters and the work that they do. This workshop will use concepts and the model from the book "Influencer" (by Joseph Grenny et all) which details the three (3) keys to a successful change initiative and uses the six (6)  sources of influence.

    Prepare to work together to discover the Scrum Master vital behaviours!