impediments in scrum

IMPEDIMENTS IN SCRUM

Overview

Impediments Impediment: anything that slows down, distracts, interrupts the team or a team member while performing activities aiming to reach the Sprint goal

Personal Impediment Team Impediment Organizational Impediment

Why is it important that we raise impediments? Why don't team members raise impediments? How can we overcome these issues?

"I Have No Impediments"

IMPORTANCE Impediments are very important in Scrum Productivity can be improved by working and resolving these problems

The Scrum Impediment Cycle › Capture

› Track

› Triage

› Resolve

› Report

› Learn

Examples of Organizational Impediments

Silver bullet thinking and superficial adoption Assuming Agile Is All About Developers Unrealistic Promises Assumption that Book Learning is Enough Local vs Global Optimization Single-Function Groups Lack of Training Misguided Cost Savings and Synergy Efforts Failure to Remove Organizational Impediments

Typical impediments to keep a careful eye on

Broken builds

› Issues with the ‘tools of the trade’

› Other projects

› Unplanned company events

› Unreliable supplier / 3 party

›Ungroomed product backlog

› Absent product owner holding up key decisions

Your examples of IMPEDIMENTS

Scrum Master and Impediments

Scrum Master remove impediments or coach teams into removing them?

As part of coaching of scrum teams, when an impediment crops up, Scrum Master should help the team find their own way to remove the impediment

References

http://www.scrumshortcuts.com/blog/planning-metrics/implicating-impediments/ http://www.scrumalliance.org/articles/409-i-have-no-impediments http://www.scrumshortcuts.com/blog/planning-metrics/scrum-

metrics and-reporting-measure-what-you-manage/

Contacts

Francesco Attanasio Mail: francesco.attanasio@yahoo.it Twitter: LeanScrumMaster