Skip to main content

Scrum Breakfast June: Agile Management

Radical Management, or a New Work Paradigm?

Today, some companies are wildly successful at creating value and excitement for their customers. You can see it in the stock prices of companies like Apple, Google, or Salesforce.com. Other companies are doing more to destroy value than to create it. These companies die slowly or become the subjects of government bailouts.

What is the difference between these two classes of company? A pattern is emerging. Successful companies are embracing practices and principles of Agile and Scrum and failing companies are sticking to traditional command and control. The successful companies are energized, pleasant places to work.

How can your company embrace agile values at the management level? How can you create an environment conducive to creativity and continuous improvement? How can you transform your company in to a more competitive organization (and have more fun while working)?

As readers of this blog know, next week I'll be at the Washington Gathering on revolutionizing the world of work. I expect to bring back many good ideas on building bridges between agility and management. 

This exchange seeks to build the bridge between agility and management and offer models for an agile organization. My goal is for each of us to leave the room with ideas for how to make our companies better, more creative environments.

Where: SwissICT
When: 1.June 2011, 8 to 11am
Registration via SwissICT

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 …