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

Comments

Popular posts from this blog

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…

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…

10 Warning Signs, that your team is not self-organizing

How do you know that self-organization is working? The Bern Chapter of Scrum Breakfast Club looked into this questions, and identified the following warning signs (which I have taken the liberty of translating).

The team reports to the Scrum Master at the Daily ScrumPeople wait for instructions from the Scrum MasterTeam members don't hold each other responsible [for their commitments]The same impediment comes up twice"That's the way it is" => resignation"I" instead of "We"Flip charts are lonelyCulture of conflict-avoidanceDecisions processes are unclear, nor are they discussedPersonal goals are more important than team goals
To this list I would add my a couple of my favorites:
you don't see a triangle on the task board (not working according prioritization of stories)after the daily Scrum, people return directly to their desks (no collaboration)there are a least as many stories in progress as team members (no pairing)
P.S. You can join the …