Skip to main content

What does it mean to be an agile company?

Agile: Having the faculty of quick motion in the limbs; apt or ready to move; nimble; active; as, an agile boy; an agile tongue
Agile has become fashionable. Everything from Scrum to Network Attached Storage is going to help your company become more agile. At least if you believe what the advertising hype tells you.  So agility has become something companies want. OK. But how many of them have thought through what that really means?

While discussing the product backlog with a student at my Scrum class (an employee of a well known national institution), we discovered an interesting confict:
  • Student: How do you know when a release will be ready?
  • Me: Take the product backlog, which is sorted by priority. Combine feature sizes with estimated velocity per sprint, to group features into sprints. That, the sprint length and a calendar give you the estimated completion date for each feature.
  • Student: But the Product Owner can change his mind? Those features are not committed.
  • Me: Right, only the Sprint Contract is a binding committment. Until the start of the sprint, the product owner can change the priorities of the product backlog. Only the sprint backlog is binding.
  • Student: But management expects schedules to be a commitment! Can we really deliver to a commitment?
  • Me: well, you could limit the product owner and say, you're not allowed to change anything...
  • Student: but that wouldn't be very agile.
  • Me: No, it wouldn't. Being agile is about being able to change your mind (and the discipline to do it sensibly). By committing in detail to your course of action for the next 6 months, you become languid, lethargic, ponderous, slow and unresponsive.
There you have it: a management who claims it wants to be agile, but deep down, it prefers to be a pondering elephant. You can lead a horse to water...


Anonymous said…
I don't get your last sentence...your conclusion. What are you talking about "a management". Who are you talking about and what is your point again? It's not clear to me after reading your last sentence what your conclusion or moral of the story is and outside the student who you are referring to.
Peter said…
You can lead a horse to water, but you can't make him drink.

This refers to the frustration felt by certain coaches who are asked to come in a help a company to become agile, show the company how to do it, only to discover that the company does not want to be agile. Only one thing to do: Smile and move on to the next company.

Popular posts from this blog

Sample Definition of Done

Why does Scrum have a Definition of Done? Simple, everyone involved in the project needs to know and understand what Done means. Furthermore, Done should be really done, as in, 'there is nothing stopping us from earning value with this function, except maybe the go-ahead from the Product Owner. Consider the alternative:
Project Manager: Is this function done?
Developer: Yes
Project Manager: So we can ship it?
Developer: Well, No. It needs to be tested, and I need to write some documentation, but the code works, really. I tested it... (pause) ...on my machine. What's wrong with this exchange? To the developer and to the project manager, "done" means something rather different. To the developer in this case, done means: "I don't have to work on this piece of code any more (unless the tester tells me something is wrong)." The project leader is looking for a statement that the code is ready to ship.

At its most basic level, a definition of Done creates a sh…

Explaining Story Points to Management

During the February Scrum Breakfast in Zurich, the question arised, "How do I explain Story Points to Management?" A good question, and in all honesty, developers can be an even more critical audience than managers.

Traditional estimates attempt to answer the question, "how long will it take to develop X?" I could ask you a similar question, "How long does it take to get the nearest train station?

The answer, measured in time, depends on two things, the distance and the speed. Depending on whether I plan to go by car, by foot, by bicycle or (my personal favorite for short distances) trottinette, the answer can vary dramatically. So it is with software development. The productivity of a developer can vary dramatically, both as a function of innate ability and whether the task at hand plays to his strong points, so the time to produce a piece of software can vary dramatically. But the complexity of the problem doesn't depend on the person solving it, just …

Scaling Scrum: SAFe, DAD, or LeSS?

Participants in last week's Scrum MasterClass wanted to evaluate approaches to scaling Scrum and Agile for their large enterprise. So I set out to review the available frameworks. Which one is best for your situation?

Recently a number of approaches have started gaining attention, including the Scaled Agile Framework ("SAFe") by Dean Leffingwell, Disciplined Agile Development (DAD), by Scott Ambler, and Large Scale Scrum (LeSS), by Craig Larman and Bas Vodde. (Follow the links for white papers or overviews of each approach).

How to compare these approaches? My starting point is Scrum in the team. Scrum has proven very effective at helping teams perform, even though it does not directly address the issues surrounding larger organizations and teams. An approach to scaling Scrum should not be inconsistent with Scrum itself.

Scrum implements a small number of principles and constraints: Inspect and Adapt. An interdisciplinary Team solves the problem. Deliver something of va…