location_city Gatineau QC schedule Nov 23rd 11:30 AM - 12:30 PM IST place Room - Mont-Bleu

Whether it's a minor typo on a page, a major failure causing a severe outage of a system or anything in between, the software industry is fertile ground for examining problems and their causes. From the problems that plagued HealthCare.gov to defects that allowed some lucky people to purchase airline tickets for almost nothing from United airlines, we hear a constant stream of issues with software systems.

With our society becoming increasingly dependent on software, we need to "up our game" with respect to tracking down problems with they happen, ensuring that defects are caught before entering the wild, and are prevented from occurring in the first place.

Root Cause Analysis is a process that enables this form of continuous improvement and uses techniques borrowed from other engineering disciplines. The aviation industry, for example, constantly seeks to improve due to the dire consequences of any failures in that domain.

This interactive workshop will explain when and how to use Root Cause Analysis (RCA) to investigate problems and determine actions that will ensure that those problems can never happen again. Using real world examples the attendees will explore simple, lightweight RCA practices as well as a more involved example using fault tree analysis.


Outline/Structure of the Workshop

  • 10 minutes - Introduction
  • 10 minutes - Overview of Techniques
  • 30 minutes - Facilitated fault tree analysis of an example software failure
  • 10 minutes - Debrief and Questions

Learning Outcome

As an attendee of this workshop, you will learn the purpose and mechanics of conducting and leading sessions to determine the causes of significant issues that have affected your work.

The workshop will focus on using simple root cause analysis for smaller problems, and the fault tree analysis technique for a larger, more complex example.  You will explore as many aspects of a failure as practical, and will identify possible corrective actions that need to be taken in order to prevent a similar failure in the future.


Target Audience

All roles

schedule Submitted 6 years ago

  • Mike Lowery

    Mike Lowery - Coaching flow - Moving past resistance

    Mike Lowery
    Mike Lowery
    Sr. Agile Specialist
    schedule 6 years ago
    Sold Out!
    60 Mins

    “They are resisting the changes I am trying to implement!” It’s a common refrain when people don’t embrace a change with the speed or enthusiasm desired. Do you keep pushing, give up or call in the big guns? How you respond to resistance can doom the change to failure, or boost the chance of success.
    As coaches, we introduce new ideas in many different contexts. Relying on positional authority (our role as coach), or calling on outside authority (the managers who hired us) isn't likely to get those ideas a fair hearing.
    In this talk, Mike will help you see resistance from a new perspective. By understanding how much influence you have, what forces are interacting around you and seeing different ways to re-frame your issues you can still get your message across without “inflicting help” on others.

  • Glenn Waters

    Glenn Waters - 8 (Agile) Testing Success Factors

    60 Mins

    In many Agile environments testing is either pushed to the end of a Sprint or is handled in a separate Sprint. This “mini-waterfall” approach to testing can be the root cause for a number of problems, including stress for the testers, delays in getting to Potentially Shippable Product Increment, missed testing, and team interruptions.

    During this session we will look at 8 practical techniques that teams can try to help them deliver higher quality products. We will be using Jenga blocks as a tool to explore the techniques that can be used to improve quality.

  • Mike Bowler

    Mike Bowler - Moving Towards Continuous Delivery: Getting there from here

    60 Mins

    Continuous delivery is the capability to release new features or changes at any time, dictated only by the needs of the business and not restricted by technical limitations. Some companies use this to deploy dozens of times a day, others release less often.

    The benefits of continuous delivery are fairly obvious today. Companies that have the ability to release on demand have a distinct advantage over their competitors who can’t.

    The challenge is planning the journey. Given where we are today, what steps should we be taking? What measurements should we be tracking now to know if we’re moving in the right direction? What do we need to change in our process to make this happen?

    In this workshop, we will explore several milestones and measurements for continuous delivery to allow participants to create a roadmap for their specific environments.

    Mike has been helping a variety of companies move towards continuous delivery, from startups to the Fortune 500 and brings that experience to the discussion.