Skip to main content

Lean/Agile Leadership Series

"People change what they do, not so much because we give them analysis that shifts their thinking, but because we show them a truth that influences their feelings."

John. P. Kotter, Heart of Change
High Performance requires
Engineering, Teamwork and Focus
Photo (c) Fotolia

A classic failure scenario when implementing Scrum is lack of understanding and support from management. Why? Since they do not understand what the Agile/Scrum teams are trying to accomplish, the have not bought into it.

Mary & Tom Poppendieck closed the gap between management and Agile with their Lean Software Development books. Inspired by their work, I have created a series of workshops, the Lean/Agile Leadership Series to expose all levels of management to the basic truths behind Lean, Agile and Scrum.

The goal of these three Workshops is to create Awareness, Interest and Desire among all levels of Management and Thought Leaders for the Lean Principles and Agile Values.

Each on-site workshop consists of an introduction to the corresponding Lean and Agile principles and values, a discussion of the pressing issues of your organization, an interactive simulation to experience the principles at work, and a debriefing on opportunities and side-effects of applying these principles in your organization. You and your management leave each workshop with ideas for improvment that you can apply to your business immediately.

Curious about the workshop? Download the Lean/Agile Leadership Series description or contact me.

Ready to go beyond the internal marketing phase? The check out Mary and Tom Poppendieck's Lean Leadership course to learn essential Lean tools, skills and principles. September 8 and 9, 2010 in Diessenhofen, Switzerland (45 Minutes from Zurich Airport).

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 …