Archive for September 2009

More on Kanban versus Scrum

September 30, 2009

David Koontz sent me a fun (and funny) take on Kanban versus Scrum.


Also, Roderick Lim Banda has produced a good article comparing several approaches to project management, and mapping them to different project attributes which they best address. See his thinking at


What is a ‘Scrum Nazi?’

September 24, 2009

My colleage Tarang Patel brought this term to my attention, and I find it fascinating. What, exactly, is a ‘Scrum Nazi?’

Not having heard the term in daily use, I can only speculate, but I infer that a Scrum Nazi is a fanatic who demands rigid adherence not only to a particular Scrum process, but to an ideology of Scrum that permits no disagreement regarding its superiority over all other project-management philosophies.

Every ideology has its fanatics, so it shouldn’t be surprising that this is true of Scrum, but I find something ironic about a rigid orthodoxy based around a lightweight framework that deliberately under-specifies how software development is to be managed.

I’ve never met a true Scrum Nazi in person, but a discussion with some people at one company some time ago made clear to me that a “Scrum uber alles” mindset does exist.

These folks, many of whom had a strong background in Scrum, were in the process of setting up a new office. They had put together a set of requirements for the office, and a to-do list for various tasks that needed to be accomplished to complete the move.

The odd thing, to me, is that they discussed planning the office move as a Scrum exercise, complete with user stories, epics, and release plans.

Why is this odd? It’s odd because Scrum is designed for cyclic development, wherein teams provide useful increments of new functionality (which have immediate value) for a product at short, frequent intervals. The schedule for Scrum projects is fixed, but the scope is allowed to change in order to meet the schedule.

In contrast, there is no product as such for an office move. Also, the work has a fixed scope that must be achieved, and is neither cyclic nor incremental in any useful sense. Finally, the schedule, while important, has more “give” in it than does the scope.

In short, an office move is an inherently waterfall-style project, not a Scrum-style project.

I mentioned these points to the folks at this company, in as mild a fashion as I could. While everyone was polite and civilized, it became clear that there were no points of agreement to be reached.

My attitude towards project management is that one should use the approach that makes the most sense, rather than apply the same approach to all projects. I suspect that the Scrum ideologues (surely a nicer term than Nazis) feel as they do because Scrum is the only technique they’ve seen used, successfully, on software projects, and have often seen waterfall approaches fail. To me, this is an example of learning the wrong lessons, in a way that leads to a case of, “If you only have a hammer, all problems look like nails.”

I love Scrum, and believe in it deeply for managing most software projects. However, I wouldn’t plan an office move, or a fancy dinner party, with Scrum.

I’d like to hear about your experiences with Scrum ideologues, and mis-matches between project characteristics and project-management philosophies that you’ve seen. Are these things common? I suspect the answer is “Yes,” but would like to know.

Kanban versus Scrum

September 14, 2009

Once upon a time, “Agile” was a new word. Somewhat later, “Scrum” was a new type of agile development. Now I’m reading more about “Kanban” as a new(er) type of agile development.

Henrik Kniberg has an interesting comparison of Kanban vs Scrum on his Web log. He does a very nice job of summarizing the difference. If I were to summarize his summary, I would say that Kanban essentially replaces the concept of time-boxing as the main constraint mechanism with that of limiting simultaneous tasks in a particular workflow state.

Scrum Sprints are planned, through collaboration between the Team, Product Owner, and Scrum Master. This planning is time boxed, just as the Sprint itself is time boxed. Given a particular team size, the execution of the Sprint is constrained by the duration of the Sprint, with requests implemented in rank order.

Kanban work is not time boxed. Instead, the team works through a steady stream of requests, prioritized as appropriate. The constraint is on the maximum number of simultaneous requests allowed per workflow state. Thus the team might have a limit of two “In Process” requests at any time.

My take-away is that Kanban and Scrum are both Agile.

I like Scrum more from the planning perspective, because it entails more planning (albeit short term). Like it or not (and most engineers don’t like it!), stakeholders outside the Scrum teams do want to have some concept of “plan” or “schedule.” The business as a whole has valid needs for such things.

I like Kanban more as a process for handling a stream of unpredictable requests, such as in tech support departments. Kanban’s emphasis on “pull” and absence of time-boxing appear well-suited for the interrupt-driven life style of tech support.

Scrum processes can handle tech support issues, but not instantly. Kanban processes can handle feature development over time, but provide less of a safety net in terms of working to a plan and having due dates.

That’s my take on Kanban versus Scrum. What’s yours?

Daily Scrum Meetings for Distributed Teams

September 8, 2009


The “Daily Scrum” meeting is a core practice in Scrum, and one of only three schedule-related practices (the others being the Sprint Planning and Retrospective meetings).

Scrum emphasizes the need to minimize overhead, since overhead takes time away from development. Team meetings entail significant overhead, since they pull all team members away from productive work. For this reason, we expect team members and others to collaborate as necessary, meeting informally two or three at a time, to resolve questions and issues.

However, informal collaborations don’t provide a common awareness of the project status across the team, and increase the likelihood that critical issues may not be handled quickly. For these reasons, Scrum prescribes a Daily Scrum meeting for the whole team, but keeps the meeting short.

The Ideal Daily Scrum

The Scrum Master facilitates the Daily Scrum meeting. His job is to get the team and Product Owner together, and get from each team member three pieces of information:

  1. What I’ve done since the last Daily Scrum
  2. What I plan to do before the next Daily Scrum
  3. What issues I know of that require assistance from someone else to resolve

The purpose is not to resolve issues in the meeting, but to acquaint everyone with the current status of the project, and to call out the need for collaboration to resolve issues. Issue resolution occurs after the meeting, when the people involved get together for the purpose.

An experienced team of six people can easily complete a Daily Scrum meeting in less than fifteen minutes.

Daily Scrum Meetings for Distributed Teams

Daily Scrum meetings are more difficult to arrange when team members are not co-located. Distributed Scrum meetings require teleconference facilities, including phone conference (at a minimum), Web conference, and video conference (if possible).

In the simplest case, a distributed Daily Scrum meeting is identical to the local version, except that the communication occurs over the teleconference system. Unfortunately, two factors can conspire to make Daily Scrums difficult:

  1. Time-zone differences
  2. Language differences

Coping with Time-Zone Differences

Time-zone problems are minor if the outlying participants have at least two hours of overlap in their standard work days. For mixed East-Coast / West-Coast teams in the US, for example, the time difference is three hours, and team members have five overlapping work hours in which to schedule meetings.

Trans-oceanic teams have more difficulty. Teams split across two sites separated by more than eight time zones have no overlapping hours, and there is no convenient way to arrange a Daily Scrum meeting. The practical ways to handle this are

  1. Pick a time that inconveniences one site (usually, the one with fewest members)
  2. Have separate Daily Scrums for sites, with Scrum Master recording both
  3. Replace short Daily Scrums with longer twice-weekly status meetings

The first option is the simplest, and most straightforward. The problem is that it makes life hard for part of the team every day.

The second makes life easier for most members, but jeopardizes the common awareness and quick response to issues.

The third also makes life easier for most members, and may be unavoidable when the difficulty of getting to the meeting is significant for some members, but it also jeopardizes quick response to issues.

None of the alternatives is attractive, because there is no attractive way to collaborate closely with people who work several thousand miles away. It is better to avoid the problems by having team members co-located, or at least with some common working hours.

Coping with Language Differences

Daily Scrum meetings become impossible if team members share no common language. Consider the case where members in a US “headquarters office” speak English, while those in a “branch office” in China may not all speak English. Even those in the remote office who do speak English often read and write it better than they speak, and may not feel comfortable enough to speak in meetings.

Recommendations for dealing with language differences include

  1. Have a local facilitator at the remote office who speaks both languages, and guides or interprets as necessary
  2. Have all team members submit their three pieces of information by writing (e.g., email, Wiki) in advance, for review and discussion at the meeting


Distributed Scrum can work, and distributed Scrum meetings can work, provided that enough care is taken to cope with time-zone and language differences. It is important to weigh the impact on communication and morale against expected benefits before making a decision to set up distributed teams.

Welcome to Deep Scrum

September 8, 2009

My name is Kevin Thompson, and this is my Web log about the Scrum framework for agile software projects.

I have a doctorate in physics, and certifications in project management and Scrum, so I take a very quantitative and scalable approach to Scrum. I am fascinated by the mathematics of Scrum, and how its basic concepts arise in a natural way from the fundamentals of project management.

I manage Scrum projects, teach Scrum to teams and project managers, and lecture on Scrum and software project management (email for details).

Kevin Thompson, Ph.D.

Project Management Professional
Certified Scrum Practitioner
Certified Scrum Master