Skip to main content

Announcing Radical Management Training

Radical Management Training
Delighting The Customer Through Continuous Innovation

with Steve Denning and Peter Stevens

As a business leader, have you ever wondered what Steve Jobs did to turn an almost bankrupt computer company into a firm that transformed the world of retail, music, mobile phones and tablets?  Have you ever thought about what you can do to not to fall victim to the disruptive innovation that has killed so many companies?

What would your company be like if your customers loved your products and services? How would work be different if your staff were totally motivated and happy to come to work?  If turf battles, silo organizations and layers of management did not stifle the creativity you need to survive and thrive in the 21st century?

It's not a dream. Your company can be innovative, responsive and profitable (and a seriously fun place to work!). There are companies like that today. Maybe even parts of your organization are like that today. Your organization can be that ideal company in your mind: Innovative, Responsive, Profitable and Fun (seriously!).

In this 3-day interactive course, you learn and experience the values, principles and practices of Radical Management that are behind some of the most successful companies today. So you can apply them in your company the day you return to the office.

When:
  • February 22-24, 2012 
  • April 18-20, 2012 
  • May 21-23, 2012
Location:

The 20 F Street Conference Center
20 F Street NW,
Washington DC 20001
Close to Union Station, shops and hotels.


For more information and registration: http://radical-management.eventbrite.com/

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 …