Is your team pointing the finger at one another? Does development hold responsible the business and is the business accusing development? Is everyone too busy pointing the finger to address the problems? Discover how to recognize blame and move beyond it to foster a safe culture. Come to this interactive talk to discover ways to change culture, leave with tools to help you initiate change immediately, and learn from observations and experiments from real experiences with various teams in different organizations in different size businesses.



Outline/Structure of the Workshop

  • Pair Sharing Blame
  • Impacts of Blame
  • Blame Culture
  • Introduction
  • Mindset
  • Silent Brainstorming Healthy Environment
  • Characteristics of Low Blame Environment
  • How to Cultivate
  • Techniques to Explore
  • Wrap-Up
  • Questions

Learning Outcome

  • Understand impacts of blame
  • Be able to identify blame
  • Understand blame is a complex problem with unclear solutions
  • Be able to identify characteristics of a healthy low blame environment
  • Leave with multiple techniques & tools to address blame in the work environment that
    • Improve Listening
    • Increases Safety
    • Accelerate Learning

Target Audience

management, team members, development, product owners, scrum masters, analysts, etc.

schedule Submitted 5 years ago

  • Jason Little

    Jason Little / April Jefferson - Creating Alignment for Agile Change

    60 Mins

    Sometimes people in organizations feel as though Agile has been pushed on them. They end up going through the motions, without any real sense of ownership of what they are doing. Instead of actually implementing meaningful changes, organizations end up doing "Agile in name only" by slapping Agile labels on existing processes. Then Agile is blamed for "not working". This isn't an Agile problem. It's an alignment and ownership problem. In this session, through theory and multiple real-world case studies, you'll learn how to co-create change by involving the people affected by the change in the design of the change.


  • Tom Bellinson

    Tom Bellinson - The Odd Couple: Process Management and Agile Design

    45 Mins

    Agilistas are often quick to dismiss any practice that looks like a remnant of the “waterfall days.”  Process management tends to be one of those end-to-end activities that looks, smells and tastes like a waterfall initiative, but don’t be fooled!


    Process management is a vital part of preparing the ground for a successful agile design effort.  There are certainly times when process is not so important to software design, but if you’re building business software, it is foundational.  In this environment, good process management doesn’t guarantee good design, but lack of it makes the probability of good design less likely.