Andon Cords in Development Teams: Our Experience of Driving Continuous Learning through a Culture of Experimentation

schedule Sep 23rd 10:00 - 10:45 AM place Ballroom C people 10 Interested

Summary

In this session, you’ll learn about one team’s struggle to improve collaboration and how they sought to shorten cycle time by carefully crafting an experiment with an Andon Cord. The Andon Cord is a Toyota innovation designed to empower front-line employees to recognize issues, initiate a stoppage of work, and work together as a team to quickly identify a path forward. The emergency cable strung above assembly lines became a symbol of the Toyota Way, and has widely been copied throughout the auto industry and beyond.

You’ll be introduced to metrics that show a surprising correlation between collaboration through Andon Cord pulls and Cycle Time!

 
 

Outline/Structure of the Talk

Context & Culture of Experimentation

We’re working on a program at USCIS, a federal agency. Within our product, we have 3 scrum teams, each ranging from 6-10 team members. Some of our golden metrics include:

  • Frequently deploying to production, 10+ times daily
  • Code commit to production in 20-30 minutes
  • Average time to acknowledge an incident ~1 minute

Our project has a phenomenal culture of experimentation. Our team has always believed that when we create an experiment with a well-formed hypothesis, and it has a good chance of failure and a good chance of success, we’ll be able to generate more information to learn from. Our conversations are constantly around asking questions like “what did we do well, what didn’t we do so well, and what did we learn?”

Andon Cord Experiment

Our team created a hypothesis that by having a visual indicator when someone needed help or had an issue, then (1) the team would quickly identify solutions to issues, instead of feeling stuck for extended periods of time and (2) we’d strengthen feedback loops when someone felt stuck or needed. The success of this experiment was to be measured by (1) evaluating an increase in flow by seeing a decrease in Cycle Time, (2) discussing during a future retrospective if they felt collaboration had increased, and (3) addressing issues as they arise, instead of waiting until the “right time”.

The Results

On July 25, 2018, our In Development cycle time was at its peak (11 days in progress). At this same time, we hadn’t pulled the Andon Cord in over 3 weeks. On average, it was taking our team longer to complete a story In Development than it was to complete a 10-day sprint. We saw noticeable improvements to the experiment after the team did some inspection and adaption – specifically, the team created more psychological safety around pulling the cord by (1) changing the verbiage of when to pull the cord to be “whenever someone needs the opinion of the team” and (2) adding a dancing tube man when the cord is pulled to add excitement. Six weeks later on September 6, we were averaging 1.267 Andon Cord pulls per day and our In Development cycle time had decreased to 2 – an 82% decrease.

Looking back at a year’s worth of data, our In Development cycle time was greater than 5 days…

  • 4% of the days when we averaged more than or equal to .5 pulls per day
  • 37.2% of the days when we averaged less than .5 pulls per day
  • 78% of the days when we averaged less than .1 pulls per day

Psychological Safety

Surprise! We all thought developers and engineers wanted uninterrupted time to work. The Andon Cord is all about unplanned interruptions. But psychological safety can be fostered for this by (1) protecting and ensuring that the team – not management – has ownership of the when and why for an Andon Cord pull and (2) that pulling the Andon Cord is fun (our team has fun red lights, a dancing tube man, and developers are rewarded with a Joe Buck, a fake dollar named after one of our devs, each time they pull the cord).

In addition to our team using the Andon Cord, the other two scrum teams within our product have now adopted it as a practice, and there’s also an Andon Cord across all three teams – used when there’s an “all hands on deck” issue to address.

Bring it Home: Implementing an Andon Cord

1. Coach your teams on the importance of experimentation. Use a resource like the Celebration Grid as an example to illustrate how the most learning happens when there’s an equal chance of failure and success.
2. Teach your teams about the Andon Cord – talk to them about how Toyota uses it. Let them know how other development teams use it and how it’s influenced their work and collaboration.
3. Ask, don’t tell your teams what they want to do next with this new information.
4. Provide freedom for your teams to create an experiment that resonates with them. Show patience, but continue to evaluate what worked, what didn’t, and what should be improved or continue.
5. Have fun. This is not an experiment that shames someone who didn’t know the answer to something, nor is it a finger-pointing exercise to figure out who broke what. Rather, it’s a fun way to showcase how the whole is greater than the sum of its parts.

Learning Outcome

Relating to the DevOps 3 Ways

1. Flow: Learn how you can improve flow by decreasing cycle time by increasing collaboration – and how you can visualize this correlation to your teams.
2. Feedback: Learn what an Andon Cord is and how you can use it to strengthen and amplify feedback loops within your teams.
3. Continuous Learning and Collaboration: Learn how a culture of experimentation can enhance psychological safety within your teams, ultimately contributing towards continuous improvement.

Target Audience

Anyone interested in shortening feedback loops on their teams and/or working groups!

schedule Submitted 4 months ago

Public Feedback

comment Suggest improvements to the Speaker

  • 45 Mins
    Talk
    Beginner

    Have you tidied up your personal life with Marie Kondo and are now wondering how to achieve the same effect in your work life? Do you have the feeling that the most valuable product backlog items (PBIs) are getting lost under a mountain of old stories, bugs, and tasks? Maybe you know a change is needed, but feel completely overwhelmed about where to start? If so, join us to learn how to make your product better through the life changing magic of tidying up your backlog.

    We’ll start by exploring the costs of a large, cluttered product backlog and share a short quiz you can use to gauge the current state of your own backlog. Next, we’ll cover how we’ve adapted the KonMari method and introduce five easy steps you can take to get started in your tidying process. We'll share real-life examples along the way, calling out potential pitfalls to avoid (don’t become a storage expert!), and illustrating how story mapping may be the magical backlog equivalent to Kondo’s “vertical folding” technique. By the end of the session, you’ll know the specific next steps to take so that you too can realize the many benefits of a tidied-up product backlog: improved visibility, increased self-organization, and easier decision-making.

  • Liked Mark Grove
    keyboard_arrow_down

    Mark Grove / Julie Wyman - What’s REALLY Going On? An Observational Skills Workshop

    45 Mins
    Workshop/Game
    Beginner

    Imagine you are asked to sit in on a team’s sprint review and retrospective. The team has been having difficulty forming and the Scrum Master has asked you to observe the team dynamics during these two sessions. Are you simply going to watch what’s going on or is there more you can do? Perhaps you are seeing interactions and team dynamics at play without truly realizing what you are observing. And when you do observe, are you injecting your own biases into those observations? Observation is a powerful tool, but one which we may not take advantage of to its true potential. After all, what exactly should we be observing, anyway?

    By learning how to expand our observational skills in a non-biased and non-judgmental manner, we can gain a deeper understanding of team dynamics and interactions allowing us to offer more meaningful and impactful support, coaching, and empathy. Because there are many observational aspects that pass us by, the best way to become more observant is through deliberate practice. So, let’s practice together with a group exercise in a fun and safe setting!

    In this highly interactive workshop, we’ll start by sharing tools and tips to make you a better observer. Then we’ll ask for a small group of volunteers (“builders”) to be observed performing a brief task. The remaining attendees will practice applying the observation techniques, and, after the builders finish, will share their observations in small groups. We’ll conclude with a full-group debrief and discussion of the key takeaways and opportunities to improve our effectiveness and observations.

    If you’re looking for new ways to connect with your team, to enhance your agilist toolkit, or simply participate in an informative and interactive workshop, this session is for you!

  • Liked Craeg K Strong
    keyboard_arrow_down

    Craeg K Strong - Kanban Antipatterns: What You Don’t Know Can Hurt You

    45 Mins
    Workshop/Game
    Beginner

    In this interactive workshop we will examine multiple examples of Antipatterns observed in real-world Kanban boards. In each case we will identify the issues and discuss ways to improve the situation. We will review a number of better alternatives and see how the improvements map to the core principles of Kanban such as visualization, managing flow, and making policies explicit. Brand new to Kanban? Learning by example is a great way to get started! A long-time Kanban veteran? Come to see how many antipatterns you recognize and help firm up our Kanban Antipattern taxonomy and nomenclature!

    Kanban is an extremely versatile and effective Agile method that has seen significant growth in popularity over recent years. Kanban’s flexibility has led to widespread adoption to manage business processes in disparate contexts such as HR, loan processing, drug discovery, and insurance underwriting, in addition to Information Technology. Like snowflakes, no two Kanban boards are alike. The downside to this flexibility is there is no well-known and easily accessible library of patterns for designing effective Kanban boards. Like Apollo engineers, teams are expected to design their board starting from first principles. Unfortunately, sometimes teams get stuck with board designs that may not provide the visibility and insight into their workflow they hope to see. Worse, some designs actually may serve only to obscure the situation. Working within the limitations of an electronic board can exacerbate the problem even further. Is all hope lost? Certainly not!

    Let’s learn more about effective Kanban system design by examining what to avoid and why. Learning by example is effective and fun!

  • Liked Thomas Stiehm
    keyboard_arrow_down

    Thomas Stiehm - Shifting Security Left - The Innovation of DevSecOps

    Thomas Stiehm
    Thomas Stiehm
    CTO
    Coveros, Inc.
    schedule 3 months ago
    Sold Out!
    45 Mins
    Talk
    Beginner

    DevSecOps uses application security practices that have been around for a while. The innovation of DevSecOps is incorporating security into the daily workflow of the team rather than leaving them to the end of a release like many legacy processes do. Shifting security left is made possible by the ability to automate many aspects of security testing and verification. DevSecOps leverages DevOps practices to make application security a first-class citizen in the practices of modern software product development. DevSecOps starts with a culture change mindset of cross-functional teams creating software through collaboration and fast feedback cycles.

    The security in DevSecOps starts before the code is written by using techniques like threat modeling and risk analysis to help figure out who might want to attack you and how they might do that. This often ignored security practice can be enabled by following the DevSecOps practices of having a cross-functional team involved in the process from the beginning, including security professionals.

    Next, DevSecOps maps application security practices into the build pipeline for a project in order to provide quick feedback about the security posture for any change made to the software. By using automation to allow the team to move quickly while maintaining confidence in the health of the code base, DevSecOps extends that health check to include application security checks. While automation can be used to make security data collection easier it is important to understand what security practices still require a human being.

    This talk focuses on how, when, and where practices should be incorporated into a build pipeline to get the most value out of your security practices through automation. It explores what manual security work still needs to be done by a person and how to maximize value while minimizing the effort of human beings.

  • Liked Mathias Eifert
    keyboard_arrow_down

    Mathias Eifert - Complexity is the Enemy! How Agile Practices Allow Us to Operate in a VUCA World

    45 Mins
    Talk
    Intermediate

    One of the key advantages of Agile over plan-driven approaches is that an Agile mindset acknowledges our ever-diminishing ability to usefully predict the future and focuses our efforts on managing change instead of trying to suppress it. This “new reality” has become pervasive enough to drive its own buzz word – VUCA, which stands for Volatility, Uncertainty, Complexity, Ambiguity. But beyond the hype lies a truth that Agile leaders need to understand and embrace – that certain problems really do respond differently to our attempts to manage and solve them. Why does this matter? Because problem contexts that defy straightforward cause-and-effect expectations significantly impact productivity while simultaneously presenting much higher risks to success. Even worse, applying leadership approaches that aren’t matched to the problem context dramatically increases the danger of catastrophic failure.

    In this session, we’ll examine how the Cynefin framework helps us make sense of what kinds of problems we’re dealing with and how we should approach them. We will then look at ten ways in which Agile frameworks, approaches and technical practices help us manage or even reduce complexity and one where they fall short. You will walk away with a deeper understanding of how - and why - the things we do as agilists increase stability and reduce risks for our teams.

  • Liked Lisa Cooney
    keyboard_arrow_down

    Lisa Cooney - The Art of Developmental Feedback

    Lisa Cooney
    Lisa Cooney
    Principal Agile Coach
    Axios
    schedule 3 months ago
    Sold Out!
    45 Mins
    Talk
    Beginner

    People don't like being told what to do, especially knowledge workers. Yet in many work settings we give feedback that is directive in nature. What would it be like to receive feedback that, instead of making us ashamed of our failures, helped us to learn and grow? What would it be like to give feedback that enabled deep and sustained learning and growth in another person, while still being perfectly honest?

    During this talk you will learn about Developmental Feedback, which enables the giver of the feedback to be clear and speak truth, and enables the receiver of the feedback to absorb it without defensiveness, and with a sense of invitation to learn and grow. You will learn about a variety of feedback types, how to have a "shared sensemaking conversation," what Impact Feedback and "The Story I Tell Myself" feedback actually are, and review sample dialogues. We will explore the conditions necessary for effective developmental feedback conversations, such as psychological safety and timeliness. You will emerge with a practical tool you can use with anyone (not just at work) to speak your truth while respecting the other person’s humanity, leading to lasting change and deeper relationships.

  • Liked Mark Koenig
    keyboard_arrow_down

    Mark Koenig - Continuous Modernization

    Mark Koenig
    Mark Koenig
    Scrum Master
    Excella
    schedule 2 months ago
    Sold Out!
    45 Mins
    Talk
    Intermediate

    Rather than engaging in an intense modernization effort followed by years of minimal maintenance, a better alternative often is modernizing a system continuously, balancing operations, maintenance, and renovation. Ideally you can improve, update, and upgrade the software system one piece at a time while it continues to operate, avoiding feature freezes and scary cut-overs.

    There are always trade-offs to be made, but some approaches better fit IT systems with long-lived missions. At a certain point, a whole-sale rewrite is the best option for replacing stale, decaying software before it leads to major headaches and eventual catastrophe. Big rewrites have big risks and big failures, however. Because of the stability and enduring mandates of some software systems, long-term investments in IT systems pay off and give room for smart maintenance strategies.

  • Liked Mindy Bohannon
    keyboard_arrow_down

    Mindy Bohannon - I’m a BA Girl in an Agile World

    Mindy Bohannon
    Mindy Bohannon
    Agile Business Analyst
    Excella
    schedule 2 months ago
    Sold Out!
    45 Mins
    Experience Report
    Beginner

    Have you ever worked with a Business Analyst (BA)? Is what a BA does on an agile project much different from what is done on a waterfall project? All analysts bring excellent communication, collaboration, and trust to their work on project teams. During this session we’ll review the roles a BA can play, a BA's responsibility on the development team, and the skills a good BA possesses. For fun, lets also talk about why an Analyst is part of the 3 Amigos and the complexity of communication channels. Generally speaking, let’s discuss how BAs participate in an agile project’s success and I’ll share some stories about my experience going from waterfall to agile, how I’ve interacted with the PO, and important things I think an Analyst should be involved in.

  • Liked Adam Parker
    keyboard_arrow_down

    Adam Parker - NoEstimates at Scale in the Federal Government

    Adam Parker
    Adam Parker
    Agile Coach
    Excella
    schedule 2 months ago
    Sold Out!
    45 Mins
    Experience Report
    Advanced

    Come learn how our 3 teams, operating in a LeSS-style scaled model, experimented with a NoEstimates approach to development work and then adopted that as our way of working for a year in the Federal government. Included in our story is a switch to Kanban, returning to Scrum, and eventually returning to pointing work. It has been a remarkable journey that I'm excited to share!

  • Liked Derek Huether
    keyboard_arrow_down

    Derek Huether - 10 Steps to Better Outcomes by Using Metrics

    45 Mins
    Talk
    Beginner

    This session is not intended to offer an exhaustible list of metrics or instructions on how to improve all systems. Rather, the intent is to provide a framework on how to ensure the quantitative and qualitative metrics you use are measuring the right things and how to apply them to a system of continuous improvement. Attendees will have a repeatable framework they can apply after leaving the session.

    The session is broken into two main parts.

    • Part 1: Identify the right (quantitative and qualitative) metrics that will help people and teams meet outcomes or goals.
    • Part 2: Create a cycle of learning and improvement that aligns people and teams to the outcomes or goals.
  • Liked John Tanner
    keyboard_arrow_down

    John Tanner - Using Metrics for Good not Evil or: How I learned to Stop Worrying and Love the KPIs

    45 Mins
    Workshop/Game
    Beginner

    Using metrics for punitive reasons is a problem as old as time. In software, this is further complicated by the fact that people rarely agree on why we are collecting metrics in the first place. In this session we will explore how we can use metrics for good instead of evil.

    By focusing on the goal of system improvement, rather than individual performance, we can begin leveraging data to make a positive difference in how we work while also delving into why we work the way we do.

    This session will include real-world examples of problems that organizations create for themselves by using metrics for the wrong intent. We will also discuss examples of good metrics and how they can be used to make our lives better.

  • Liked Katrina L. C. Tanner
    keyboard_arrow_down

    Katrina L. C. Tanner - Journey from Analyst to Product Owner to Scrum Master in less than a year

    Katrina L. C. Tanner
    Katrina L. C. Tanner
    Scrum Master
    Cvent
    schedule 3 months ago
    Sold Out!
    10 Mins
    Lightning Talk
    Beginner

    Not many people can say they have performed as an Analyst, Product Owner, and Scrum Master, much less in the same year, and sometimes at the same time.That has been my journey throughout 2018 and into 2019 thus far, as I made intentional decisions in pursuing my next best step, exploring where I really fit, and experiencing quite a few surprises along the way.

    As a CSM and CSPO, I navigated each role taking what I learned in the classroom and implementing it as a practitioner. Being very team AND operations oriented, I have always thrived when one of these were included in my job description. 3 companies, 3 roles, and 2 organizational restructures later, I have found a career that involves both. I learned what works and doesn't work for me and my teams, as well as, what I like and dislike compared to my strengths and weaknesses, especially among changes in organizational needs and structure.

    This short and sweet talk will be an overview of my journey and leave attendees with characteristics of each role to help them decide where they might fit in this agile world and tips on how to talk to your boss about your next step.

  • Liked Paul Boos
    keyboard_arrow_down

    Paul Boos - Agile Leadership 201: Enriching Management

    Paul Boos
    Paul Boos
    IT Executive Coach
    Excella
    schedule 3 months ago
    Sold Out!
    45 Mins
    Tutorial
    Executive

    The Agile Manifesto doesn't explicitly talk about what changes in management should happen and neither do the approaches. In fact, sometimes we hear the exact opposite from teams - "What do we need managers for..?" or perhaps "Can't they just get rid of all the impediments we have?"

    As a former manager and now as a coach, I find the words Servant Leadership sometimes doesn't resonate. It actually only paints part of the picture anyway. What we want are ways to enrich management so that they can do more for the organization and its teams. Let's discover what some of this enrichment might be.

  • 45 Mins
    Workshop/Game
    Beginner

    How do you get people to agree on priorities when they may have different objectives? You may be facing an issue now where stakeholders are pushing against each other in order to get their work done first. What would happen if we could create an open dialog among stakeholders and have them understand different perspectives and focus on the goals of the greater good instead of just their own? Let’s face it, proper prioritization is the difference between writing code and developing valuable solutions.

    In this simulation style workshop, you’ll learn practical methods for bringing stakeholders together and openly discuss their different priorities to agree on what’s most important overall. You will see first hand how a combining group discussion with proven prioritization methods such as Weighted-Shortest Job First and (WSJF) and Must Have, Should Have, Could Have and Won’t Have (MoSCoW) work.

  • Liked Nicole Spence Goon
    keyboard_arrow_down

    Nicole Spence Goon - Peaks or Valleys? The power of Scaling Agility in the alphabet soup of Government agencies

    Nicole Spence Goon
    Nicole Spence Goon
    Agile Coach
    Excella
    schedule 2 months ago
    Sold Out!
    45 Mins
    Experience Report
    Beginner

    Do you feel like Agile Scaling has become a goal rather than the means to an end for your organization? To determine where you stand on the Scaling spectrum, ask yourself a few soul-searching questions: Why do we need to scale? Is this the right time for us to scale? If you’ve checked these boxes, you may wonder “where do I go from here?”

    This talk will focus on 3 areas that emerged as common themes throughout my experience working on government Agile Scaling projects and ultimately influenced the trajectory of each agency's scaling journey:

    • Communicate vision consistently
    • Focus on your people genuinely
    • Create your own path intentionally

    I've seen successes and some struggles with Agile Scaling efforts in government agencies. Regardless of the agency acronym or the frameworks used, these key elements shaped their scaling outcomes.

  • Liked David Laribee
    keyboard_arrow_down

    David Laribee / Arushi Bhardwaj - Introducing the Dojo Model: Experiences from the Industry and within Fannie Mae

    45 Mins
    Experience Report
    Intermediate

    The Dojo movement is growing in popularity as an approach that helps enterprises transform into world-class product development organizations. Dojos represent a departure from the classic agile focus on delivery, bringing learning and a product mindset to the forefront.

    We'll share the emerging Dojo model by way of specific examples and mini-case studies. You will see how Dojos have taken shape at Fannie Mae and other large companies in the last several years. Think of this as a tour of the Dojo for two, main audiences: teams and leaders. Attendees will leave understanding how Dojos can benefit their group, portfolio, and/or organization.

  • Liked Itopa Sulé
    keyboard_arrow_down

    Itopa Sulé - What NOT to do when prioritization fails

    Itopa Sulé
    Itopa Sulé
    Lead Agile Coach, Canada
    Capital One
    schedule 2 months ago
    Sold Out!
    45 Mins
    Workshop/Game
    Intermediate

    One common mistake by new Agilists is to think that the product backlog is a linear list with the highest priority item on the top. As it's often the case, the reality is different. Prioritization is neither binary nor linear. Your team will be asked to work on several competing priorities, like meeting the new regulation while working on the next product milestone (the product is the company lifeline) - and your product owner will insist these are both top priority!!

    In this workshop we are going to explore different tools, to ensure that our teams are working on the highest value backlog items: from Eisenhower Method to Cost of Delay, CD3 and modified Weighted Shortest Job First (WSJF).

  • 45 Mins
    Talk
    Beginner

    On average Agile transformations get into trouble at about 14 months from the time they start. Have you ever wondered why?

    Is it because you started from 'the bottom up?" Or is it because you spend time, money, resources and people creating great teams and didn't pay attention to having a professional, empowered Product Owner organization?

    Agile transformations that target department level and not the organization have a very low success rate and you end up with an agile department enveloped by a traditional organization. That leads to dark work, decision delay and dysfunction.

    So, what can you do?

    Come and learn some of what I learned the "hard way" over 7 transformations.

  • Liked Dane Weber
    keyboard_arrow_down

    Dane Weber - Undercover Scrum Master

    Dane Weber
    Dane Weber
    Lead Consultant
    Excella
    schedule 2 months ago
    Sold Out!
    45 Mins
    Experience Report
    Intermediate

    After three years as a Scrum Master and Agile coach, I hit a wall coaching a team that did not want to try popular Agile engineering techniques such as TDD and pair programming. I had become a Scrum Master after four years working on the business analysis and account ownership side of things and could not speak from personal experience about engineering practices. In order to get some first-hand experience and to gain a new perspective, I chose to spend a year or two as a software developer on a Scrum team.

    The experience has been eye-opening. I experienced a tremendous cognitive load working with a wide array of technologies; this pulled my attention away from many of the collaborative and process-oriented activities I cared about as a Scrum Master. I was surprised to feel strong pressure to complete work quickly, cutting corners, even when the Product Owner and Scrum Master were not asking me to. When this pressure was explicit, it usually came from my fellow developers. On the other hand, there is real joy in writing code and seeing a system do something worthwhile that it wasn't doing before. My outlook has changed tremendously and is something I want to share with anyone who works with development teams, especially Scrum Masters and other coaches. I am still enjoying my time as a developer, but I'm looking forward to returning to coaching and incorporating this experience into my approach.

  • Liked David W Kane
    keyboard_arrow_down

    David W Kane - Amend the Agile Manifesto!

    10 Mins
    Lightning Talk
    Intermediate

    We all do it. In fact, I've done it already in this talk description. I've amended to title of the "Manifesto for Agile Software Development" to just "Agile Manifesto," and I suspect most of the you attending AgileDC 2019 have done this as well. In this talk I will argue that this truncation of the title of the Manifesto is more than an abbreviation of convenience, it is a sign that how we use the Manifesto in practice has moved beyond what was stated in the foundational document. For many folks Agile has significant importance and impact beyond software development. Just as our nation's Constitution has been amended over the years, I will propose amendments to the Manifesto in this talk.