Category Archives: impediments

Sample Impediments (RDU)

Just did a course in Raleigh-Durham.  Here are some impediments the group identified…. Lack of people Turnover in staff Unclear scope Requirements changing too much Cutting corners Lack of communication with customer Bureaucracy – pessimistic stakeholders Poor morale Manage by fear Budget (insufficient) Lack of visibility Lack of management skill Dependencies (other projects) Traceability (lack […]

Read More »

PO Impediments – Charlotte May 2013

Several things to say about impediments: Few teams have a public impediment list. They should. Few teams are aggressively attacking impediments, as I see it. (I guess this depends on what one means by aggressive. I mean full time alienation of impediments. Mercilessly.) We must use impediments, and continuous improvement to get higher velocity in […]

Read More »

Public Impediment List: “We don’t want to see the bad news.”

The Scrum Guide does not mention it, but I strongly advocate a public impediment list. The simple idea is: visual management, and single piece flow off the ‘top’ of the list.  That is: Make the team’s impediments visible and visual.  Prioritize them. And then actively work them each day.  With at least one meaningful impediment […]

Read More »

Blue Pill and Red Pill

During a course in Romania, a participant asked me: “don’t you think you are setting false expectations? Scrum may help, but it will not help that much. This sets false expectations and disappoints people.” Good comments. Good concerns. I don’t agree that we are setting false expectations; although I think some issues must be addressed. […]

Read More »

The importance of a real team

Scrum requires a real team. The word ‘team’ is often used, often in different ways.  So, let us define it. According to “The Discipline of Teams” by Katzenbach and Smith, this is what you should look for: 1. A meaningful common purpose that the Team has helped shape. 2. Specific performance goals that flow from […]

Read More »

Public Impediment List – Again

I wrote the following post to a Scrum group. Perhaps you will find it interesting. It is lightly edited. And it is in response to another person’s post. *** Let’s talk about the impediment list more. Along the way I will mention some of the problems I see in real life. I find that most […]

Read More »

Who should fix Impediments?

In the Certified ScrumMasters LinkedIn group, Michael asked: Who should fix impediments, the SM or the Team? His answer was: Both. And then he discussed.  This topic has drawn a fair number of comments.  Here is one of mine. *** 1. Michael is right. Who should fix the impediments and how much the Team should […]

Read More »

We must have working software at the end of the Sprint!

This is a common failing (we don’t have working product or working software at the end of the sprint).  Jeff Sutherland has said this is the biggest problem in the Scrum community — too many teams don’t have working software at the end of every Sprint. If we include cases where 1 or more PBIs […]

Read More »

Public Impediment List !!! – 2

There is a good Scrum trainer who thinks that a public impediment list is not important.  So, if he can misunderstand, then we all can. Here is a better explanation of why it is important, I hope. I find the lack of a public impediment list is a prime indicator of a lack of focus […]

Read More »

Getting higher velocity! Take 2

I posted yesterday these listed below would lead, or at least could lead, to higher velocity (higher productivity) in your new product development teams: * Better retrospective meetings * Better impediment lists * Better business cases to management * More effective action (get approval and implement one ‘fix’ until you get results) * Better use […]

Read More »