Archives

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. […]

Read More »

What are impediments? Definition of Impediment

Definition of 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 Certified […]

Read More »

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 […]

Read More »

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 […]

Read More »

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 […]

Read More »

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 […]

Read More »

The ScrumButt Test (2): Working Software

The second line in the ScrumButt Test says: Software must be tested and working by the end of each iteration. This is the second of three items that confirms the team (project) is “iterative”. There is a series of small tests (within the ScrumButt Test) for whether the team is really doing Scrum (in my […]

Read More »

Do we need an Impediment List? Yes!

Yes, we need a public impediment list. Every Team does. Why? One argument against is that all impediments should be eliminated immediately.  Yes, if this were possible, this should be done.  But I think that assumes an incorrect view of what impediments are. Yes, it is true some impediments only appear from time to time. […]

Read More »

Impediments (or symptoms of) – Montreal Class July 2013

Below is a list of ‘failure modes’ for projects, as identified via the experience (in waterfall, whatever, agile or scrum) by the people in the Montreal July 2013 class.  These are not in priority order.  They suggest certain impediments to add to the Public Impediment List for your team. Lack of communication Too many impediments […]

Read More »

Starting with Scaling

Question: “We are starting Scrum. We have the kind of projects that require scaling. But how do we start with Scrum and have some scaling?” Answer: The basic framework of Scrum does not attempt to answer this question.  It assumes you will use lean-agile-scrum principles and values, and devise your own specific solution to this […]

Read More »