Skip to main content

How to chill your company

Does anything do more damage to motivation and morale than a severe reprimand? Is anything more critical to a company's ability to innovate than motivation and morale? Can you be innovative in a climate of fear?

During my last trip to the States I heard various stories of people being called on the carpet by their management. Here's a typical story: John (name changed), a senior engineer with a passion for his organization's mission, had been building informal contacts across the organizational silos to improve cooperation, collaboration and innovation in his organization. The organization was losing the interest of its customers, and everybody felt an urgency to get the organization going again. Over time, many people become interested in John's idea and so they decided to have a little gathering.

The organization's top manager had been avoiding the topic and had cancelled every meeting John had tried to schedule with him to discuss this issue. When John sent out the invitations for the larger event, he neglected to invite said manager. What happened next is not exactly clear, but two days after the invite, this manager was quite upset. He called John into his office, chewed him out for over an hour and forbade John to ever raise the issue again. While John was not issued a formal reprimand, he left the meeting wondering what his future was at the organization.

What happened? John was "out of control" and the command-and-control hierarchy reasserted itself.

Do things like this happen often? I asked this question to an agile coach at large bank here in Zurich. His response: "Are you kidding!? All the time! Most recently at yesterday's sprint review! It's part of the culture."

Have you (or someone you know) been chewed out on job?  What impact does that have on you and your coworkers? Sound out on twitter! #chewedout

P.S. Want to make your organization a better place to be? Join us for the Zurich Gathering For C-Suite Leaders with Steve Denning and myself: Zurich, Sep 12, 2011


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…