Monthly Archives: August 2013

At first, when Scrum and when Waterfall?

When your company is first starting Scrum, how do you decide which projects use Scrum and which ones do it ‘the old way’?  (Let’s assume the old way is a form of waterfall. You are waiting to transition them from waterfall, later.)  Assuming for now (for a transition period) some projects must remain in waterfall. […]

What are impediments?

An impediment is anything that is slowing down the Team.  (The Scrum Team)  Anything! In PMP words, it is any kind of issue. And it may include risks as well, but typically only high probability risks that are likely to occur fairly soon. (I typically also recommend a simple risk log for each Scrum team […]

When would I not want to do Scrum?

This is a slight variant on the question I asked before. I wanted to add a few things that I did not say before.  You still might want to do a project despite some of the things I will mention, but I have gotten impatient as I have gotten older. So, when? Some things I […]

When should you NOT use Scrum?

I was asked this question in a class recently.  (When should I not use Scrum?)  I gave an answer, but I want to give a better answer, or at least a different one. To be fair, it is a hard question. And a hard question for me. My personal answer, which I gave, is I […]

Creativity and Process

Here is a good quote: Now I have to tell you something, and I mean this in the best and most inoffensive way possible: I don’t believe in process. In fact, when I interview a potential employee and he or she says that ‘it’s all about the process,’ I see that as a bad sign […]

The ScrumButt Test (3): Enabling Specifications

The third line in the ScrumButt Test is: “The Sprint starts with an Enabling Specification.” What does this mean? The first practical goal was to eliminate the analysis paralysis and delay associated with waiting until the specification was “complete”. On the other hand, too many agile teams are trying to be effective when ‘no one […]

For Quick Decisions, Depend on Deadlines

In Saturday’s (8/2/2013) Wall Street Journal, Dan Ariely suggests that to reach a decision, and often just to make progress, you need deadlines.  Deadlines ‘force’ people to take action. This is what we have known with Scrum for years.  So, we have time-boxes all over the place (and I recommend using them more than just […]