I have always gravitated towards data because I enjoy identifying patterns to tell a story. I am also a passionate Agilist, playing the role of change agent in Agile Transformations. Therefore, my natural inclination has always been to couple the two together to drive change.

I like to think of collecting team data as just another feedback loop in an Agile environment. After all, the people doing the work know best! Therefore, why not collect data points from teams to identify areas for continuous improvement throughout the organization? I have had some success in this area, but unfortunately this approach has not always lead to the desired outcome.

Like everything else that could be used for good, data can also be leveraged for evil. I have learned the hard way that if an organization lacks an Agile mindset, and does not foster an environment of safety, trust, and experimentation, collecting team metrics can actually lead to more harm than good. However, once the prerequisite of safety is established, data no longer becomes your enemy as a change agent, but your ally, and a powerful tool in your Agile coaching toolbox.

I have had both success and failures in this areas. Join me for this interactive session where I share my experiences and help answer some of your questions on using data to drive change.


Outline/Structure of the Experience Report

  1. Levelset
    1. Revisit the Agile mindset and the intent of Agile; happier employees, delighted customers, and better business outcomes
  2. Agile Adoption Timeline
    1. Purpose:
      1. Highlight once the Agile mindset is acquired by the organization and leadership, there is an acceleration to better business outcomes
      2. This section sets the stage for the correlation between the Agile mindset and use of data in change initiatives
  3. Define Data Collection and Analysis
    1. Another Feedback Loop in an Agile environment that enables organizations to uncover organizational patterns they may not know exist
  4. Experience Report: The Failure
    1. Share the context and experience in which data utilization in a change initiative backfired and lead to more harm than good
    2. Examples & Takeaways
    3. Tie takeaways back to Agile mindset and Agile adoption timeline
    4. Advice for organizations who have not acquired the Agile mindset
  5. Experience Report: The Success
    1. Share the context and experience in which data utilization in a change initiative was very powerful and helped lead to better business outcomes
    2. Examples & Takeaways
    3. Tie takeaways back to Agile mindset and Agile adoption timeline
    4. Advice for organizations who have acquired the Agile mindset.
  6. Summary

Learning Outcome

  1. The Agile mindset is one that focuses on happier employees, delighted customers and better business outcomes
  2. Acquiring the Agile mindset is the turning point for an organization's Agile transformation.
  3. Collecting data in an Agile environment is an additional feedback loop used to make decisions and identify organization constraints.
  4. Command and control environments, Agile in name only, lack safety and trust. Utilizing data to drive change in these environments can lead to more harm then good.
  5. Agile Leadership environments contain safety and trust. In these environments, data becomes a change agent's ally.
  6. Aggregating data points to tell a meaningful story helps Agile coaches and leadership to uncover organizational constraints and coaching needs.
  7. Agile team fluency, safety, and happiness are leading indicators of better business outcomes.

Target Audience

Internal FTEs with the desire to drive positive change and a focus on happier employees, delighted customers, and better business outcomes.

Prerequisites for Attendees

All participants should have the desire to learn, challenge the materials, and be prepared to be interactive.


schedule Submitted 3 years ago

Public Feedback

    • Colleen Johnson

      Colleen Johnson - End to End Kanban for the Whole Organization

      Colleen Johnson
      Colleen Johnson
      schedule 4 years ago
      Sold Out!
      45 Mins
      We often look to our engineering teams first to drive efficiency and speed to deliver but as we optimize the flow of our development processes we quickly create pressure in the organizational workflow with the activities that feed into and out of product delivery.  Product definition struggles to keep pace and establish a queue of viable options to pull from.  Marketing efforts begin to pile up as features release faster than we can share the news.  All of this stems from optimizing only one part of the overall system.  In this talk we will look at how to scale Kanban practices to the entire organization to provide the visibility, flexibility and predictability to make every part of the business truly agile.  
    • Mathias Eifert

      Mathias Eifert - Agile Essentialism – Getting past rule-based Agile

      45 Mins

      Are you sometimes overwhelmed by the never-ending stream of Agile teachings you’re supposed to know and have at your fingertips to address every possible situation in the proper Agile way?

      Sure, Agile is a “mindset” and you’re supposed to “own your process” but the reality is, that’s not how we teach or learn or usually even talk about Agile. Instead, we are bombarded with ever more retro formats, technical practices, prioritization techniques, facilitation tips, and other snippets of wisdom that we should all know before we can be considered good Agilists. And if your job title is Scrum Master or Agile Coach, the range of things you’re expected to master only expands.

      In this session, Mathias Eifert will share how he found his footing in a vast sea of loosely connected Agile rules, processes, techniques and tools by recognizing that a small number of fundamental concepts can help with finding answers that are “good enough” as a starting point to tackle most new contexts or problems. Together, we will examine how many established Agile approaches can be traced back to these essential concepts and hopefully help each attendee a little further along on their journey from rules-based Agile to fundamental understanding.

    • Paul Boos
      Paul Boos
      IT Executive Coach
      schedule 4 years ago
      Sold Out!
      45 Mins

      So you are considering getting a coach to help you in your transition to Agile. Or perhaps you are an Agile practitioner considering becoming an Agile coach. What do these Agile coaches do? What makes them different?

      This session will enter the foyer of the house that describes what coaches do and considerations one can have when they think about coaching (including hiring one). Prepare to be challenged and to learn a bit of what it takes to be or work with a coach; it has little to do with courses or certifications, though they may help. In covering what coaches do, one can now begin to think along the lines of what the skills one may need to improve.