Skip to main content

Toasting Management in #stoos? Anstossen or anstoosen?

In ten days or so, barring bad weather or last minute emergencies, some 22 thought leaders, idea farmers, managers, agilists, community leaders or otherwise interesting people will get together in Stoos to catalyze a change management. It turns out, Stoos is a pun in German, which I'd like to explain.

Stoos is the name of a community overlooking Schwyz and located at about 1'300m above sea level, with ski slopes up to about 1950m. In German, it is often referred to as 'der Stoos' (the Stoos) as if it were the name of mountain, but I don't think that is case.

I don't know why Franz Röösli chose this hotel. We wanted a ski location (in honor of the gathering which produced the Agile Manifesto being held at the Snowbird Lodge in Utah). It needed to have a conference room, be willing to block rooms for 20 people, and be reasonably easy to get to for international travelers. It was the only alternative he proposed, but it looked good, so here we are.

Stoos is very similar to another German word: 'stossen' which means 'to push'. A variation of stossen is anstossen (this would be a preposition in English, but in German its part of the verb). Anstossen has many interested meanings for our gathering:
  • to poke
  • to kick off (something)
  • to toast (or to drink to) something
So what will do in Stoos? We may poke management, but we want to change management, not bury it. Certainly we will start with a toast to tomorrow's management. Here's mine:

To common sense! May it displace the Pointy Haired Boss as the leading representative of management! #stoos #toastmgmt

How would you toast management in the 21st century?

Comments

Jonas said…
My toast to the new management will be : "Let customer delight be our only guide to a better corporate world! Manage radically, forget shareholder's interests. #stoos #toastmgmt"

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 …