Skip to main content

Market Survey: Agile in Germany

The latest issue of OBJEKTspectrum is dedicated to Agile SW development. In one article, they presented the results of a non-representative study on how widespread agile techniques are in Germany.

Not surprisingly, Scrum is the most widespread agile framework, 21% of the respondants are using it, 17% have had first experiences with Scrum 12% are planing to introduce Scrum. Second place goes to XP at 14%, 35% and 7%, respectively. Other agile methods are largely unknown and not widely in use.

Service companies ("probably" IT companies) at 27% and Financial Service companies at 25% provided the lion's share of the respondents, but Automotive and High Tech at 13%, Telecoms at 9% and Pharmaceuticals at 7% were all well represented.

Where these companies happy to use agile? 97% were satisfied: 30% "very statisfed" and 50% normally "satisfied" und 17% marginally satisfed. Only 3% said they were dissatisfied.

Which techniques were being used? Top on the list were: Short Release Cycles, a Product Owner with Product Backlog, incremental delivery and the daily scrum. Surprisingly, only 26% of the participants were doing retrospectives. (I admit, this is the easiest to forget, but is the secret of real improvement in productivity, quality, you name it!)

What are the effects of Agile?

  1. Improved Flexibility -- 89%
  2. Improved Job Satisfaction -- 88%
  3. Better Learning on the Job -- 87%
  4. Higher Productivity -- 78%
  5. Clearer Project Status -- 74%
  6. Higher Quality -- 74%
  7. Higher Velocity -- 72%

52% of the respondents thought Agile was suitable for large projects,
26% did not (and presumably the rest had no opinion). Only 14% of the
respondants though Agile produced "Chaos" in development.

What kinds of projects are developed using agile?

  1. Web Development -- 72%
  2. Individual Projects -- 71%
  3. Product Development - 70% (including embedded systems)

Agile is popular even for larger projects. More than 7 People: 52%, including 11 to 20 People: 16% and 20 to more than 50 people: 14%

Their conclusion:

"Agile Software Development is entering the mainstream. This is confirmed not just by the brand recognition, but also by the fact that many participants have already taken their first steps with Agile and that large organizations and many different branches are adopting it.... Agile is being successfully deployed for industrial projects for many different industries.

"The value of agile development can be identified, but it is not yet so great as we had expected. There is more unrealized potential for optimization. Further, agile is being used mostly in small and medium sized projects, even though agile would be applicatable in large contexts."

They concluded with a recommendation, which I share wholeheartedly: do the retrospectives! This continuous improvement is what makes Agile work.

The article is available online in German. The print edition comes out on April 25, at which time the PDF should disappear.


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…

Explaining Story Points to Management

During the February Scrum Breakfast in Zurich, the question arised, "How do I explain Story Points to Management?" A good question, and in all honesty, developers can be an even more critical audience than managers.

Traditional estimates attempt to answer the question, "how long will it take to develop X?" I could ask you a similar question, "How long does it take to get the nearest train station?

The answer, measured in time, depends on two things, the distance and the speed. Depending on whether I plan to go by car, by foot, by bicycle or (my personal favorite for short distances) trottinette, the answer can vary dramatically. So it is with software development. The productivity of a developer can vary dramatically, both as a function of innate ability and whether the task at hand plays to his strong points, so the time to produce a piece of software can vary dramatically. But the complexity of the problem doesn't depend on the person solving it, just …

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…