Skip to main content

Big Scrum Projects: Allianz Project Light Beacons

Besides successful start-ups, at least three "name brand" European companies have committed to Scrum for their software development: Nokia (source of the Nokia test), SAP, and Allianz Deutschland (Germany).

At the most recent gathering of the German Scrum User Group, Simon Roberts presented how Allianz committed to and introduced Scrum. Simon described Project "Leuchtfeuer" - transitioning the Enterprise to Scrum via a series of lighting beacons.

His metaphor reminds me of the airway lighting beacons used in the 1920s and 30s. At night, pilots flew from light beacon to light beacon, enabling navigation over long distances for the first time. Even today, approach light beacons play a critical role in the precision approaches which allow aircraft to land in bad weather.

Simon's "airway" has nine waypoints:
  1. Sponsor - don't leave home without one.
  2. Initiate - get outside help
  3. Ignite - light the first beacon with a pilot project
  4. Diversify - light more beacons with additional projects
  5. Promote - do good and talk about it
  6. Professionalize - training, training and a center of excellence
  7. Establish - light still more beacons
  8. Consolidate - align with corporate strategy
  9. Integrate - Corporate Governance, SOX, CMMI etc.
Sponsor - Having support from a senior executive is critical. Successful change is a combination of top down and bottom up. Bottom up alone isn't enough, which means that Stealth Scrum won't work. Top down (the classic consultant driven approach) has its limitations as well; the successful transition requires both top level and grass roots support.

Initiate - Corporations will usually need outside help. Reading a book without practical experience isn't enough. The need is not so much for classical consulting, but rather for coaching of the teams and management as they build experience and overcome problems using Scrum.

Ignition - The first project. Here top-down meets bottom up. The first project should "a real project, not too easy, not too critical". Lots of coaching will be needed, especially during the first few sprints. Successes are the basis of support, both grass-roots and top level.

Diversify - After initial success, add more projects. Do different types of projects. If the first project was a web application, try a mainframe project. Ensure that enough coaching is available for the new teams.

Promote - Internally and externally. Top Management needs to see results and give buy in. Allianz competed for and won this year's IT Strategy Prize from CIO Magazine, and Agile was part of the application. Simon recommended the patterns of Fearless Change: Champion Skeptic, Corporate Angel, Corridor Politics... and many open informational events.

Professionalize - Scrum Masters and Product Owners need the corresponding training (CSM, CSPO). Eventually the company should establish a Scrum Center which serves as a resource for helping Teams and Product Owners do Scrum better.

Establish - work with Customers, Project Management Office, Corporate Education, etc. to make Scrum an offical option or even the preferred open for software development management.

Consolidate - at this point, Scrum has demonstrated successes at the base and support from top management. If the strategy has been emergent, now is the time to consider an Enterprise Transistion Team which assures defines the strategy and assures alignment of IT operations with business strategy.

Integrate - The enterprise is still has Laws, Regulations and Standards, e.g. Corporate Governance, Compliance, Standards and Frameworks that it needs to comply with. Scrum can be integrated into all of them (e.g. SOX, CMMI, ITIL). Don't worry about it, but don't start too soon either.

A fascinating talk about a practical introduction of Scrum into a very large organization. You can download his slides at

I would have liked to hear a bit about the business results of this program. Has the company become more innovative? What impact has it had on the productivity, employee retention, effectiveness, corporate results? Allianz Deutschland is making a substantial change in their corporate processes. Is it worth it?

Simon and his partner Christoph Mathis have agreed to talk about Scrum in the Enterprise at the Scrum Breakfast in Zurich. This promises to be an interesting discussion! December 3, 2008 -- mark your calendars! And if you want an invitation, let me know!


Popular posts from this blog

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…

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…

What is the role of a Business Analyst in Scrum?

When I teach a CSM class, my goal is that my participants go home delighted (and of course that they learn about Scrum, that they are motivated to do Scrum, and can pass the online CSM exam). So after every class, I ask for feedback, in particular what could I do to get a better score. And for the next class, I strive to implement or address two or three of the points raised by my participants.

One issue that was raised was unanswered questions. It is annoying to ask questions and not get answers! Time is limited, so it is not always possible to answer all questions, so I thought, why not answer them on my blog? So here goes, first question:
What is the role of a Business Analyst in Scrum? This question is a challenge because Scrum doesn't answer this question! Scrum is a simple, team-based framework for solving complex problems. The roles and ceremonies in Scrum are designed to ensure that inspect and adapt can occur regularly with complete and correct information. Scrum does not…