• Skip to primary navigation
  • Skip to main content
  • Skip to primary sidebar

Agile Buddha

Demystifying Agile, Getting to its Core

  • Our Blog – Agile Buddha
  • Agile Workshops and Certifications
  • Agile Commune – Join Here!
  • Webinars
  • Contact
  • About Us
  • Show Search
Hide Search

Root Cause

5 WHYs: Positive Root Cause Analysis To Find Good Practices

by Avienaash Shiralige 3 Comments

In my earlier article I shared my opinion about using 5 WHYs to find root causes. What I really missed to point was, it is not just applied to find root cause to problems, but it can be used to find root cause to good things that are happening on the team.

In sprint retrospectives we usually pick some problem that occurred, try to figure out why it happened, and then understand how we could prevent this problem from happening again in the future. Our root cause analysis meetings are usually always on “What is That Not Going Well”.

5 Whys Postive Root Cause Analysis

Now let’s apply 5 WHYs thinking to this question…

[Read more…] about 5 WHYs: Positive Root Cause Analysis To Find Good Practices

5 Whys: Sprint Failed – Team Did Not Deliver Committed Work

by Avienaash Shiralige 9 Comments

Applying 5 Whys is a good way to address the problems that you are facing on your teams.  This thinking is very simple, just ask WHY multiple times till you reach to root cause. You can read more about 5 Whys here.

5 whys agile teamSome benefits of using this Lean technique are:

  • Helps identify root cause of a problem
  • Determine the relationship between different root causes of a problem
  • Very simple to use without any statistical analysis
  • Very useful when problems involve human factors or interactions

Asking 5 times WHY generally leads you to a root cause. In some cases you may reach in fewer iterations and in some it may take more than 5.

Now let’s apply this technique to our problem on hand.

Problem: Team failed in their sprint as they were not able to complete all the work committed.

[Read more…] about 5 Whys: Sprint Failed – Team Did Not Deliver Committed Work

Primary Sidebar

LikeBox

Tags

5 Whys Acceptance Criteria Adoption agile Agile Culture Agile Estimation Agile Offshore Agile Teams agile testing Agile Thinking Agile Transformation Agility Appraisals ATDD Automation Backlog Grooming BDD Big Picture business analyst Capacity Planning case-study code quality Collaboration Daily Scrum DevOps distributed agile Distributed Scrum Estimation Good Practices kanban kanban-mythbusters lean Metrics Planning Poker Prioritisation product owner Scrum ScrumMaster Sprint Sprint Demo Sprint Retrospective Story Point Story Points Sustainable Pace User Story

Categories

  • Agile
  • Agile Leadership
  • Agile Testing
  • Agile Transformation
  • ATDD
  • BDD
  • Continuous Inspection
  • Culture
  • DevOps
  • Distributed Agile
  • Estimation
  • In Conversation with Tim Ottinger
  • Java
  • Jira
  • Kanban
  • Lean
  • noprojects
  • Patterns
  • Presentation
  • Product Owner
  • Scaled Agile
  • Scrum
  • Software Metrics
  • Testing
  • Testing Practices
  • User Story

Copyright © 2025 · Malonus Consulting LLP

  • Email
  • LinkedIn
  • Twitter
  • Facebook
  • Privacy Policy