Thursday, September 30, 2010

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?

Sunday, September 12, 2010

New Blog: Scrum4Kids

I have started a new blog:

It's about applying Scrum and Agile to family situations. I think there is a lot to learn about scrum in daily life and a lot to learn about daily life from Scrum. Comments & Co-authors are welcome!

Thursday, September 2, 2010

Scrum Breakfast/October: Enhancing agile development with software assessment

An agile process replaces upfront design with the focus on the ability to react and to decide based on the current situation. But, to take the right decision we need to be able to assess the situation accurately and fast. However, software systems are large and complex and they handle large amounts of data. Thus, they present many more details than we can reliably control. Approaching the problem in an ad-hoc manner does not benefit us.

Assessment is a critical activity to ensure proper decisions involving large amounts of details. And it is expensive, too, with various studies reporting assessment to account for as much as 50% of the total development effort. As such, it should be addressed explicitly in the development process.

In this talk, Tudor Girba will provide an overview on the problem of assessment and illustrate how the current popular approaches fail to solve it because they are either ad-hoc or too generic. He then describes agile assessment, a new approach that puts emphasis on offering contextual and continuous feedback.


Tudor Girba attained his PhD in 2005 from the University of Berne, Switzerland, and he now works as a consultant at Sw-eng. Software Engineering GmbH. His main expertise lies in the area of software engineering with focus on software assessment, and he is currently helping companies assess and manage large software systems and data sets. He is one of the main architects and developers of the Moose platform (, and he participated in the development of several other assessment tools, models and techniques. He is the president of the Moose Association and the Treasurer of the Swiss Group for Object-Oriented Systems and Environments (CHOOSE).

Registration, Coffee & Gipfeli
Talk & Discussion 
Networking, Coffee & Informal Discussion
Free Coaching! Bring a problem or help with the solution! 3x 20 Minute Sessions in the coaching room.

Time, Location:
  • Date: Wednesday, 6 October 2010
  • Location: SwissICT, Vulkanstrasse 120, 8048 Zurich (above the Jeep-Dealership).
  • Registration through the SwissICT
  • The LAS core team will meet from 11.00 to 12.30. Interested people are more than welcome!
P.S. If you are not yet a member, please support the SwissICT and become a member! They provide the venue, coffee and gipfeli without charge so this can stay a free event.