Impediments – Charlotte December Course

I am an advocate of a public impediment list.  The ScrumMaster must always be working on the top impediment until the Team is perfect (and it is never perfect). The value of that can be seen when the Team has doubled (or increased) their productivity or velocity. The Team must be creative and aggressive in […]

Agile Contracts

Jeff Sutherland did a presentation at Agile 2013 that I think everyone should read and think about.  And read and think about again. Here is the slide deck: http://jeffsutherland.com/Agile2008MoneyforNothing.pdf

Agile Contracts – Question 1

Adela asks this question: Imagine we have a brand new project. And we must bid on it, and we want to use the agile-scrum method.  How should that work? This is a good question.  I will answer it quickly here. Too quickly.  I have partly answered it in my book, Agile Release Planning. And partly […]

What if Scrum is not working for you?

I was speaking to a smart guy who had taken (some while ago) my CSM course.  We were both waiting at the Cluj (Romania) airport. He made me think about this problem. The first thing to say is: Scrum is not a panacea.  It requires hard work.  Often people expect Scrum to magically make things […]

Impediments – Charleston

We just completed a CSM course and Agile Release Planning workshop in Charleston.  Here are some of the impediments they identified. They have duplications and they are not in any particular order.  In my opinion, the list should also include automated testing, better continuous integration, and better automated integration/regression testing.  These were issues discussed later […]

The CSP is in demand…

We have a problem in Scrum. First, we do well to call it an opportunity rather than a problem.  We have more opportunity sitting on the table that we have not yet grabbed.  Scrum, in general, can help us get a LOT more improvement than we have gotten. There are many root causes behind this […]

ScrumButt Test (6): Estimates created by the Team

Another installment on the ScrumButt Test. So, the next item on the test says: “The Product Backlog has estimates created by the Team.” Why is this important and what does it mean?  Let’s consider the meaning first. So, normally in Scrum estimates mean estimates of relative size/complexity in Story Points. See Mike Cohn’s book: Each […]

What does it mean to be ‘Ready’?

Jeffry Hesse wrote this blog post. [Link now broken.  Sorry!] It inspired me to write the post below. The new Scrum Guide says that PBIs (product backlog items) must be well-understood and granular enough for Sprint Planning. PB Refinement is the process we use to get them to Ready. Those are not quotes, but that […]

Impediment List – Charlotte Class Nov 2013

Here are the impediments the Charlotte class identified.  Each impediment may be useful to you. Too little transparency No finalized requirements No communication SME Availability Missing Required Technology Resistance to a common goal Unrealistic expectations Outside pressures Vague requirements Lack of resources Lack of money Bad estimates Hiding problems Not crying wolf soon enough!! Conflict […]

Impediment List – Montreal Class

Here are the top impediments identified by the recent Montreal class.  There may be some similarities, (a different person might be trying to say essentially the same thing, but for his team).  Maybe your Team will recognize some good things to work on: Team too small Under-staffed Loss of communication (with) customer, stakeholders Not dedicated […]