Problem Detection and Resolution
Core Concepts
Problem detection and resolution in Agile relies on transparency and fast feedback. Key tools include daily standups (to surface impediments), sprint retrospectives (to identify process problems), and metrics like cumulative flow diagrams (CFDs) and cycle time. Root cause analysis techniques (5 Whys, fishbone) help address underlying issues. The goal is to resolve problems quickly and prevent recurrence. Candidates must understand the difference between a problem (deviation from plan) and an impediment (blocker).
Traps
A frequent trap is treating symptoms rather than root causes. For example, if a team is consistently late, the answer might be to analyze cycle time and remove bottlenecks, not to add pressure. Another trap is ignoring problems because “we’re Agile and will adapt”-Agile requires proactive problem-solving. Also, beware of answers that escalate problems without first attempting team resolution.
Worked Example
A team notices their CFD shows a growing “in testing” column. Using the 5 Whys, they discover that test environments are often unavailable. They resolve the root cause by automating environment provisioning. This demonstrates problem detection (via CFD) and resolution (root cause fix).
Rule of Thumb
When a problem arises, ask “Why?” five times to find the root cause, then fix the system, not the people.