Skip to main content

Core Agile Values

I have always felt that agile is really about values: Openness, Honesty, Courage, and Trust. Personally Whenever I remained true to these values things went OK. In those (rare) cases when I have given into temptation, danger was lurking.

Thanks to Geek and Poke
This cartoon illustrates a classic case. Three levels of management get three different answers about the state of the project. As the report moves up the management chain, its status changes from Red to Yellow to Green. Sound familiar?

Why does this happen? A project leader colleague of mine was literally afraid of losing his job if he told his managers the truth about his project. So he didn't. Until one day, the truth could not be hidden any longer. Unfortunately, this was three days before a release party (which had to be canceled). Bad thing.

Did the impact of the truth get smaller as time went on? No. Did it become easier to deal with the problem as time went on? No. So why do people hide the truth? I think lack of trust (and the fear it inspires) is the root cause.

In another case, a ScrumMaster I know didn't want to show the release burn down to the product owner or discuss how much the team had worked on the project during the first sprint. The team hadn't met its goals for the sprint (and had spent much more time than planned on support duties from a previous project).

Why didn't she want to show the P-O this information? "He'll flip out when he sees the project is late after just one sprint." I insisted and she made the information available. She was right, though. The P-O did flip out. And when he settled down, he and the relevant managers had a talk about the amount of support work the team was allowed to do, which eliminated the problem.

If someone is afraid of the consequences of being honest, then that person is more likely to tell people what they want to hear. An policy of trust implies that people can tell possibly unpleasant truths without fear of retribution.

A policy of openness means that all stakeholders in a project have a right to complete, correct and up to date information about the state of the project. It means that there is no good news and bad news, just facts, and we want to react to facts as soon as they become known. If you know the facts, you can deal with them.

Some of you may be thinking, "we can't tell the customer about that." If you think openness is a bad thing, consider the alternative. What are the consequences of a lack of openness? What will happen when the information eventually comes out? (Don't worry, it will come out!) Can you have a policy of selective openness? And if yes, how will that impact your customer's trust and how will that impact your business?


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 …

Money for Nothing, Changes for Free

“Money for Nothing, Changes for Free” encourages both customers and suppliers to focus on value.

A key advantage of Scrum projects is that at least once per sprint you have something that could be shipped and no work in progress. You can change direction every sprint, and you can reevaluate whether the project is a good investment or if your money could be better spent elsewhere. Abrupt cancellation is risky for the supplier.

While the concept of an early-exit penalty is not new, Jeff Sutherland gave it a unique allure with his allusion to the Dire Straits hit.
Desired Benefit Incentivize both customers and suppliers to focus on functionality that provides genuine value.
Structure This works with Agile software projects because there is little or no work in progress. After each Sprint, functionality is either complete or not started. Work is basically on a Time and Materials basis with a cost target, often with the intention that the project should not use up the entire project budge…