Category Archives: Key problems

Selling the Benefits of Scrum

Two other CSTs (scrum trainers) made some comments in a Google Group, which got me thinking.  They reminded me of an exercise I normally do in my Scrum classes. Every class is different, but imagine a class that is mixed. Some people are new to Scrum, some have a few months experience, some have 9-24 […]

Read More »

Leading Fearless Change

What is the hardest thing about Scrum?  (Maybe in life.) Probably, it is that we must lead change. Getting people to change is difficult. In Scrum, for example, we are trying to change people. The initial big change and then always continuous change. And removing impediments typically requires change. First, we change them to a fully […]

Read More »

Are there Project Managers in Scrum? No (but…)

Scrum has only 3 roles: Product Owner, ScrumMaster and Implementer. Who is responsible for ‘the project’?  Well, that would be the whole Team. What do we do with George, who was a Project Manager (PM)?  Well, we have to talk to George.  Maybe he would make a great ScrumMaster or a great Product Owner.  Or […]

Read More »

Our Favorite Scrum Mistakes

Ah, Valentine’s Day! A day for a simpler love than “love your enemies.” Even the simple love is quite complex.  Well, as long as one is not besotted like Romeo below the balcony. Or Juliet above. When one is besotted, then love is truly simple. Other days, it is not. Or so I am told. […]

Read More »

Agile Release Planning is not about the Plan

Here is one key observation about release planning from the past week and a half. I have been working in France.  I have worked with 3 different companies, and a bunch of great people. In the third class, we did a 2-day workshop.  The Workshop was mainly about agile release planning, using the real work […]

Read More »

Six Myths of Product Development

Here is an HBR article : Six Myths of Product Development.  By Stefan Thomke and Donald Reinertsen. Here are the fallacies (or myths) in one list: High utilization of resources will improve performance. Processing the work in large batches improves the economics of the process. Our plan is great; we just need to stick to […]

Read More »

What cocktail parties teach us

The title above is the title of an article today in the Wall Street Journal.  The subhead is: “Brain Is Wired to Focus on Just One Thing; Which Tasks Are Easier to Combine” It’s all about how we humans are built to focus. Multitasking is, well, inhuman.  A few monkeys can pretend to multitask, but […]

Read More »

2011 State of Agile Survey

Below is the 2011 Survey by Version One.  The state of agile.  One might like yet better participants in the survey, but still I think it is generally indicative of the main trends, because many participated. http://agileconsortium.pbworks.com/w/page/51511217/2011%20State%20of%20Agile%20Survey  Some key points to me: * We have a long way to go * Too many people “rolling […]

Read More »

Scrum teams and living in packs

My experience with people doing Scrum is that we tend to take the “man is rational and isolated” hypothesis too easily.  Often it is not a thoughtful choice, just the implicit assumption of the way we are thinking or the way we speak. Isolated and individualistic are key words. If you believed in them, you […]

Read More »

More about distributed Scrum – one example

Let’s talk about distributed Scrum using one example. There are so many situations and variations for distributed Scrum.  And, hence, many different suggestions, depending on the situation. One example Imagine you are the head of technology, in the US.  Imagine you have customers in the US, and your business people are in the US, and […]

Read More »