You're hit with a problem, possibly repeatedly, and it's not clear what to do about it.  You know that Root Cause Analysis can help, and you know a Five Whys exercise is a good way to do that.  But how do you run a Five Whys?  There's more to it than putting everyone in a room and saying "Why?" five times, isn't there?

This session will prepare you to run your own Five Whys exercises, and to answer important questions like who to include, how to introduce the exercise, what to do when the group stumbles, how to deal with prematurely-offered solutions, and how to prepare for the exercise.

 
3 favorite thumb_down thumb_up 0 comments visibility_off  Remove from Watchlist visibility  Add to Watchlist
 

Outline/structure of the Session

  • When to run a 5 Whys
  • Who to include
  • Explaining it to new participants
  • Modeling good and bad causes
  • Depth over breadth
  • How much discussion is too much?
  • Save the solutions for last
  • Preparation and materials options
  • Following Up

Learning Outcome

Participants will be prepared to put together and run a Five Whys exercise.

 

Target Audience

Anyone who needs to do root cause analysis with a group (so, probably, you)

schedule Submitted 3 years ago

Comments Subscribe to Comments

comment Comment on this Proposal

  • 60 Mins
    Workshop
    Intermediate

    Trying to figure out Agile Release Planning?  We've done it and we've done it well.  Twelve teams - done! Twenty teams - done! Forty teams - done!  If your organiztion needs to tackle the enterprise release planning beast, you should attend this session.  Whether you are struggling with planning a large agile release planning event or simply trying to figure out how to improve your current agile release planning events, this session will provide nuggets of learning from planning teams with hundreds of people spread around the globe.  Many organizations have tried to conduct enterprise agile release planning and gave up because they could not overcome some of the basic obstacles like who to invite, where to hold the event, and how to keep everyone engaged.  

    If you are trying to figure out how to coordinate two teams or dozens of teams, this session will provide insights into what works and what doesn't.  You will gain expereince by practicing actual agile release planning exercises to help you prepare for your orgainzations next agile RP event.  The learning expereince starts with a presentation on the key steps to consider as you launch a large agile program.

  • Andrea
    Andrea
    Agile Coach
    Santeon
    schedule 3 years ago
    Sold Out!
    60 Mins
    Workshop
    Beginner

    Project success =  f (listening, feedback, intentionality, practices) 

    To make your agile practices and processes come to fruition, you need to cultivate an environment that promotes listening, learning, inquisitiveness, intentionality and top notch feedback that everyone is comfortable with. 

    Agile projects succeed when there are frequent high-quality reinforcing feedback loops. I will share communication models based on Clean Language questions of David Grove and the Systemic Modelling techniques of Caitlin Walker that can greatly increase clarity, sense of purpose and listening skills within your team and collaborative endeavors.  These include: Clean Questions, Clean Feedback, and Clean Setup.

    This is a hands-on, try it out, concrete practice session.

  • Liked John Sextro
    keyboard_arrow_down

    John Sextro - Coaching Affinity Estimation

    John Sextro
    John Sextro
    Agile Coach
    9 Principles
    schedule 3 years ago
    Sold Out!
    60 Mins
    Demonstration
    Intermediate

    Spend Less Time on Your Estimates

    Most teams would rather work to deliver value to customers than spend time estimating stories.  In order to spend less time estimating and more time delivering value to the customer, many teams have adopted “Affinity Estimation”.  Using “Affinity Estimation” many teams have significantly reduced the time required to estimate and I have personally been involved in sessions that used to take 60 minutes and are now taking 15 minutes.  By using “Affinity Estimation” to compare new stories to real stories that were recently completed, teams are able to quickly and confidently provide an estimate without lengthy discussions and worries of the unknown. 

    What to Expect

    The session will begin with a brief presentation highlighting everyday problems that coaches deal with when estimating stories.  Then, using volunteers from the audience, we will work through a series of exercises/games demonstrating the value of "Affinity Estimation" while teaching the audience and the volunteers how to coach these exercises for their own teams.

    All Teams are Not Created Equally

    This session will provide you with exercises that you can use for existing teams, as well as, new teams. 

  • Liked Philip Rogers
    keyboard_arrow_down

    Philip Rogers - Lean Coffee: Creative Uses of this Technique to Rapidly Surface Ideas and Encourage Team Collaboration

    Philip Rogers
    Philip Rogers
    Scrum Master
    NPR
    schedule 3 years ago
    Sold Out!
    30 Mins
    Workshop
    Intermediate

    Lean Coffee is frequently used in meetup and conference settings. The beauty of Lean Coffee is its simplicity, and it is this very simplicity which makes it an appealing choice in various Agile team contexts. Specifically, Lean Coffee is particularly good for ad hoc training sessions and for retrospectives. The focus of this workshop will be on the use of Lean Coffee in these two types of settings, where we will split up into small groups and practice using Lean Coffee to cover ad hoc training topics and to do a mini-retrospective.

     

  • George Paci
    George Paci
    Agile Coach
    Santeon
    schedule 3 years ago
    Sold Out!
    30 Mins
    Talk
    Intermediate

    Agile planning tools started simple: index cards, markers, and a table or wall. On many projects, for many reasons, these old stalwarts have been supplemented (or even replaced) by software solutions: Rally, VersionOne, Jira Agile, Trello, Trac, Scrumy, and literally dozens more, even BaseCamp. These tools have undeniable advantages over cardboard and ink in some aspects, but they're not superior in every situation.

    This session will highlight the pitfalls of centering planning meetings around software tools—even the best ones, like [your ad here]—and make a badly-needed sales pitch for index cards on a wall (compensating for Oxford's oddly anemic marketing effort). You'll see how cards can make better use of your team's time and brainpower, promote parallelism in meetings, and increase engagement by all participants.

  • Liked Shannon Ewan
    keyboard_arrow_down

    Shannon Ewan - The Art of Facilitating Agility

    60 Mins
    Workshop
    Intermediate

    From an agile implementation perspective, emphasizing the art of facilitation is an incredibly powerful tool for creating a culture of collaboration, and then leveraging that culture as a springboard to organizational transformation.  With strong facilitators at the gateway between business and IT, within IT delivery teams, and at key intersection points within an organization, the challenges to achieving organizational agility diminish. Strong facilitators bring forth the wisdom of teams and provide a container for self-organization. Facilitation is the cornerstone of servant leadership. 

  • Liked Mark Hammer
    keyboard_arrow_down

    Mark Hammer - “Want to be Agile Across the Extended Development Team? Collaborate!”

    60 Mins
    Talk
    Intermediate

    How can development organizations ensure building reliable systems, yet responsive to change? This is a fundamental question plaguing Agile organizations. The key is collaboration. Mark Hammer explores process changes and tools your organization can use to ensure high quality software, while maintaining the flexibility to respond to change. He highlights examples from large and small companies showing how simple changes can improve team performance, increase employee satisfaction and save the company money in expensive software fixes.

     The session highlights several key findings:

     1. PROCESS. Best practices for collaboration, focusing on what a collaborative culture looks like. How can managers foster collaboration? How can developers, testers and product managers work together to solve problems previously managed by just one of these groups?

    2. TOOLS. What tools can foster collaboration across these teams? And how can these tools be used to help teams adapt to new customer findings? I review several categories of collaboration tools, with special emphasis on tools that have impacted the ability of specific companies to collaborate and improve quality metrics and results.

    3. MEASUREMENT. Ways other companies have tried to measure collaboration and its impact on team performance, highlighting specific examples including companies that have put in place process and tools then measured their ROI against them.

     

  • Liked Howard Deiner
    keyboard_arrow_down

    Howard Deiner - Lean Thinking and What It Mean to the Agile Mindset

    60 Mins
    Talk
    Intermediate

    Long before the Agile revolution for software development began, industry had learned that efficient production of goods required intense attention to quality, teamwork, and continuous improvement. These themes of Lean Manufacturing (which was further refined into the Toyota Production System) were never part of the original formulation of the Agile Manifesto, and are rarely mentioned as part of the traditional Agile/Scrum recipe for teams transforming to the new “Agile” mindset.

    The reality is that the traditional Agile/Scrum recipe is actually a “dumbed down” version of the Toyota Production System, and makes it easier for organisations to grasp and start from. However, if organizations really want to achieve the goal of producing the software they need in a fashion that leads to High Performance Teams and Sustainable Engineering, they will need to understand the principles of Lean so they can incorporate them into their unique process. This session teaches the basics of Lean, and demonstrates how they apply to Agile development.

  • Liked Linda Cook
    keyboard_arrow_down

    Linda Cook / Chris Espy - First Things First - Creating Agile Team Charters

    60 Mins
    Workshop
    Beginner

    Many agile initiatives suffer from a feeble launch.  As Aristotle once stated “Well begun is half done”.  Performing the activities associated with developing a sound charter can help increase the likelihood of success for a team or organization .  

    Beginning with the end in mind, we use retrospective techniques to develop consensus around objectives, vision, and mission.  In this workshop we introduce the components of a good charter and how those components help focus the teammates toward a common goal.  In addition, the development of the recommended charter components ensures that key questions are succinctly answered during the kickoff of a team.

    Participants will learn the various types of charters and their recommended content.  During the workshop activity teams will develop a complete charter based  team of their choice or a provided case study.

  • Paul Boos
    Paul Boos
    IT Executive Coach
    Excella
    schedule 3 years ago
    Sold Out!
    3 Mins
    Talk
    Intermediate

    Creating an approach for change is difficult. There is a fine line between imposing an Agile adoption and creating a Transformation where people are collaboratively working together for the change. Based on my experience and in large US Federal Government organizations where imposed adoptions seem the norm, I’ve been working on combining many concepts into a transformation model that can work for large organizations that have ingrained cultures. This starts by helping the organization’s people take ownership and personalize what Agile means to them. Believe it or not, this can work.

    Intended for senior executives and their immediate staff (and the coaches that help them), the Taking Flight approach presents the importance of culture and how creating an organizational aspiration will help guide people. For large organizations, culture has been built up over decades and changing this is of the utmost importance to have an Agile Adoption stick. There are 3 main points I’ll address:
    - how to get people ‘onboard’ with a cohesive direction that they accept by collaboratively building their aspiration
    - how to develop and select strategies for incremental improvement towards the aspiration
    - how to realize changing from old routines into new ones aligned with the aspiration

    To help establish cohesive direction, I use an Aspirational model (your Guiding Star) to help organizations develop the direction they want to go. I show how the differences between an Aspirational model and an End-State. I explain that aspirations are inspiring and allow for a mindset change by not expressing the final state in terms of structure our expected metrics. From there, I discuss different techniques for assessing the current state of the organization and its people and developing strategies and actions for the necessary change management to move towards the organizational Aspiration; this is where the concrete steps come into play. Throughout this portion, I have the group try out various techniques for building an aspirational model and how to build the backlog of work to undertake the transformation. I introduce the Power of Habit as a means to help the organization undergo the necessary behavior changes. I close with a discussion to help the audience think around limiting change-in-progress and how to grow capacity to become more responsive to change.

    In this, you’ll get exposed to a few of many hands-on techniques that can be used to develop your Aspiration and execute on it. These are:

    • KrisMap
    • Business Model Canvas
    • Habit Loops
  • Liked Mark Grove
    keyboard_arrow_down

    Mark Grove / Jolly Rajan / Julie Wyman - Four Easy To Adopt Agile Metrics for Teams Just Getting Started

    60 Mins
    Workshop
    Beginner

    Using metrics to track agile team performance can be an important tool to reinforce the need for continuous improvement. Metrics can serve as valuable input during retrospectives, the daily standup, and sprint planning allowing teams to continuously adapt their practices and performance based on the observed patterns the metrics reveal. In our experience, many new agile leads and teams are not sure which agile metrics would be the best metrics to begin using. Some teams may be tracking various data points, but lack the skill and understanding of what the metrics are actually revealing and how the teams can use this information to self-improve.

    Our presentation/workshop introduces four "light-weight" agile metrics any team can easily adopt and begin using immediately. They are: Velocity, Comitted vs. Done, Sprint Build-up (Burn-up), & Cycle Time.

    We introduce each of these metrics and explain what each one measures, how to obtain the data, and when it should be updated. But most importantly, our presentation provides a workshop component where we provide sample scenarios for each metric. These scenarios represent possible real-life data patterns teams could experience. In the workshop, we ask the audience to work in small groups to consider what each scenario may be representing and what they would do, in the spirit of continuous improvement, to respond to these patterns. We also discuss with the audience how to use the metrics in tandem to help provide a more robust interpretation of team performance.

    We realize there are many agile metrics teams can adopt. However, for teams just starting out we recommend these easy to use yet powerful metrics to help teams monitor and assess team performance.

  • Liked Gary Pedretti
    keyboard_arrow_down

    Gary Pedretti - Agile Architecture and Modeling - Where are we Today?

    Gary Pedretti
    Gary Pedretti
    Owner
    Sodoto Solutions
    schedule 3 years ago
    Sold Out!
    60 Mins
    Talk
    Intermediate

    Application and Enterprise Architecture has been put through its paces in the agile world over the years: ideals (architectural work inside the development team, shortening the design-to-implementation loop as much as possible), misinterpretations ("We don't need no stinking Architects!" screamed the Keyboard Cowboys), and the inevitable backlash of misinterpretations, lack of craft, and the inertia of the status quo (Architectural Epics continuing to encourage a split between business and IT, command-and-control capital-"A" Architects).

    Where are we now? What have we learned? More importantly, what have we forgotten?

    Now more than ever, we need to go back to the core principles of agility and emergent architecture. Let's talk.

  • Liked George Paci
    keyboard_arrow_down

    George Paci - Lean Software Development: Principles and Tools

    George Paci
    George Paci
    Agile Coach
    Santeon
    schedule 3 years ago
    Sold Out!
    30 Mins
    Talk
    Beginner

    Lean Software Development, largely created and popularized by Mary and Tom Poppendieck, is a set of principles and tools for approaching software with a value-focused mindset.  Heavily influenced by Lean Product Design, itself the result of porting Lean Manufacturing insights over into the design realm, it can change the way you think about what you're doing and why.  Lean emphasizes the performance of the entire software-development system, and strongly cautions against optimizing pieces at the expense of the whole.


    This session will be a whirlwind tour through seven principles of Lean Software Development, and one thinking tool associated with each principle.  The common thread of focusing on value, instead of on requirements or process or utilization, ties the concepts together.