Skip to main content

My Philosophy, Sharpened at the Scrum Gathering

The day before the Scrum Gathering officially starts: I had a great talk with CSC Bob Hartman about Books, training techniques and the importance of values to a person or organization.
  • Quoting from 'the Last Lecture': Tell the Truth. 
  • To which Bob would add: All the Time. 
  • And I would prepend: Live your values! 
Tell the Truth is about Honesty and Openness and is the basis for effective communication. All the time demands an atmosphere of Trust and Courage.

This for me is what Scrum is about. In my life, I have never gotten into trouble as long as I was staying close to my values. Lose sight of them, and bad news! IMHO, these are the problems that led to the fissure in the Scrum Alliance last fall, and also caused Toyota the problems that they are having now.

When I ask myself, what do I do as a coach? I teach people to apply these three principles:
Live your values. Tell the truth. All the time.
And that they don't need to be afraid of doing so.

Comments

Bob Hartman said…
Peter, thanks for capturing our conversation. Only one correction - I didn't add "all the time" The original context was Randy Pausch anwering the question "what 3 words of advice would you tell people?" (or something like that) and his response was "tell the truth." He added that if he had 3 more words he would say "all the time."

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…