location_city Washington schedule Oct 15th 04:15 - 05:00 PM place Ballroom A people 23 Interested

Have you sat through a retrospective that feels like Deja vu? Didn’t we already come up with a plan to fix this thing we are talking about, AGAIN! Are you in yet another blame/complain session with no apparent way to fix the complaint? Time and again this happens in retrospectives and before you know it, the team thinks they should cancel them altogether because they aren’t effective. Fortunately, there are clear steps you can take to fix this and make your retrospectives highly effective.

In this session we will cover the common patterns that typically lead to ineffective retrospectives. The downsides to the team when retrospectives are ineffective. Then I will give you a very effective format to follow along with some different techniques to help get your retrospectives to be very effective.


Outline/Structure of the Workshop

  • Introduction (2 mins)
  • Common signs or reasons retrospectives are ineffective (10 mins)
    • Finger pointing retro
    • Half the group on devices retro
    • One loud voice retro
    • Boring, drone retro
    • Marathon retro
  • Provide downsides of ineffective retrospectives
  • Provide effective format for each retrospective regardless of technique
  • Demonstrate how to effectively start off a retrospective
  • Provide retrospective techniques
  • Table top exercise to identify which retro technique to use based on current team dynamics
  • Wrap up

Learning Outcome

  • Participants will be able to identify common patterns that make retrospectives ineffective via familiar examples
  • Participants will understand the downsides to ineffective retrospectives via material presented
  • Participants will gain skill to make retrospectives more effective via table-top demonstrations and material presented by speaker

Target Audience

Scrum Masters, Developers, Product Owners, Project Managers, Program Managers, Testers, Product Developers

Prerequisites for Attendees

No prerequisites


schedule Submitted 2 years ago

Public Feedback

    • 10 Mins
      Lightning Talk

      In this lightning talk, we explore the 5 attributes to look for in a ScrumMaster:

      • Knowledge - Deep knowledge in Agile and Scrum
      • Experience - Deep experience with Scrum teams and in Agile environments
      • Coaching - Deep understanding of Coaching concepts and techniques
      • Facilitation - Deep understanding of Facilitation concepts and techniques
      • Servant Leadership - Deep understanding and desire to enable success for the teams and the organization

      From there we look at the ScrumMaster's progression for removing impediments and addressing issues:

      • Did we talk about it in the Retrospective?
      • Did we discuss the impact?
      • Did we identify root causes?
      • Did we come up with solutions?
      • Have we tried the solutions?
      • What were the initial results?
      • What are next steps from here?

      We use the steps above to ensure:

      • Our teams are not making the same mistakes time time after time
      • Our teams are not having the same issues arise time and time again
      • Our teams are not stagnating but rather are getting better over time

      This session will arm session attendees with what to look for in a ScrumMaster and discuss how the SM uses the impediment progression to ensure we have a continuously improving team.

    • 45 Mins

      Want to find the perfect Product Owner? It's easy, all you have to do is find one with the time to do the job, the power to make decisions, the knowledge to make smart decisions, the interest in doing the job, and the Vision to build the right product. Easy, right?

      Via a story, the session will start by exploring 5 key attributes of being a Product Owner:

      1. Bandwidth
      2. Power
      3. Knowledge
      4. Interest
      5. Vision

      After that discussion, we do an exercise to identify what a Product Owner does day to day. The debrief will identify the balance a Product Owner must have in working with stakeholders, end users, customers AND working with the Scrum team AND product backlog refinement. We will also touch on client/vendor relationships and identify if the PO should come from the client or the vendor (and how technical should the PO be).

      The session concludes the attendees being given a Product Owner persona scoring template. The attendees can use this template to score their Product Owners and we will discuss how to identify their Product Owners areas of strength and gaps areas.

    • Maria Fafard

      Maria Fafard - The Secrets of Coaching for Scrum Masters

      45 Mins

      You are a passionate and a dedicated Agilist. You have heard that in order to truly empower and motivate Agile teams and individuals, you might need to learn how to function as an Agile coach, but you are not sure where to start. What does Agile coach do exactly? What is the difference between a Scrum Master and an Agile coach? How can you elevate your coaching skills? And how can you become an Agile coach when you grow up?

      Join us to learn how to grow your coaching competencies, differentiate yourself among your peers and take performance of your teams to the next level. I will be sharing the story of my own journey from being a Scrum Master to being an Agile Coach and what I learned along the way.

      The speaker is a ICAgile Certified Professional in Agile Coaching (ICP-ACC) and Agile Team Facilitation (ICP-ATF), an ACC (Associate Certified Coach), a Certified Professional Facilitator (CPF), and a graduate of Georgetown University Leadership Coaching program.

    • Matthew Holtry

      Matthew Holtry - Why Your Next Scrum Master should be a Peace Studies Major

      45 Mins
      Experience Report

      As an undergrad, when I declared my self-designed major to be a combination of Peace Studies and Information Technology, I remember my friends asking me, "What are you going to do with that? Mediate conflict between computer nerds?" Now, as an Agile Coach and Scrum Master, I find myself regularly doing just that (and I love it)!

      While it can certainly be helpful for a Scrum Master to understand your AWS architecture, it is far more important for your Scrum Master to understand your organization's people architecture. They need to know how things are supposed to get done and how things really get done. They need to know how to create psychological safety inside the team while protecting them from interactions outside the team that may undermine that safety. Most importantly, they need to understand how the people in the organization "fit" together and how to mediate the inevitable conflicts that will arise when these parties have opposing goals.

      In this interactive session leveraging real stories from the trenches, I will show how the non-technical, liberal arts Scrum Master can help your teams thrive by understanding an organization's people architecture to effectively anticipate, uncover, and mediate conflict between opposing parties in a productive manner.

      No matter what you studied in college, you are welcome and encouraged to attend this talk!

    • Adrienne Rinaldi

      Adrienne Rinaldi - Coach the Coach | The Coaching Backlog

      Adrienne Rinaldi
      Adrienne Rinaldi
      Agile Coach
      CapTech Consulting
      schedule 2 years ago
      Sold Out!
      45 Mins

      You’re a new coach. Now what? This session will help you get started on an agile transformation assignment with a coaching backlog. This session will inform new coaches on “where to start” as an Agile Coach. The session will begin agile transformation challenges followed by common agile impediments, conditions for success, an agile readiness checklist and a coaching backlog including Epics, Features and Stories.

    • Brian Sjoberg

      Brian Sjoberg - Want to Deliver Quicker with Higher Quality? Stop Starting, Start Finishing!

      Brian Sjoberg
      Brian Sjoberg
      Agile Coach
      Excella Consulting
      schedule 2 years ago
      Sold Out!
      45 Mins

      Are you struggling with delivering a potentially releasable working product every iteration? Ever wonder what one of biggest reasons we have difficulty getting things done at the individual, team and organizational level are? Do you keep doing something even though you know it reduces your productivity and lowers quality? We are going to run an exercise that highlights one of the major culprits that you have all experienced and probably continue to experience. The exercise will likely ignite a little (or big) fire in your belly that will help you become more productive and improve the quality of your work. From this, we will discuss ways to improve this at the individual, team and organization levels.