Skip to main content

Results: Quick Poll on Scrum Training Needs

Last week's Quick Poll on Scrum Training Needs produced a lot of interest. The poll was divided into 4 sections. The 31 repondants voted on:
  1. What kinds of courses are needed?
  2. What advanced topics are needed?
  3. What language do they what the training in?
  4. What location/kind of course do they want?
Given the number of participants, I would not call this anything like a representative sample (and strickly speaking, an internet poll cannot be representative). Still...

The Certified Scrum Master Training seems to be well accepted among Scrum practioners. 48% of the respondants expressed a need for certified training. Scrum training however is expensive, and almost as many — 42% — felt the need for lower cost training (or at least would accept non certified training). Advanced topics (with out specifying which ones) and Getting Started courses were desired by only 26% of the respondants.

Under the advanced topics, (and more people checked these boxes than said they needed "advanced topics") Agile Planning and Estimating was the clear favorite: 48%, followed by Agile Contracting at distant 2nd — 42% —, followed by XP and Lean Workshops for Management (19% and 16%).

Interestingly, it seems the need for onsite training is larger than for open courses (or perhaps the demand for open courses is sufficiently satisfied): 35% wanted company courses, 19% each wanted open courses and webinars. Podcasts must be considered exotic with only 9% wanting podcasts.

The questions on language were interesting. The percentage wanting training in German was virtually identical to the % of visits coming from German speaking countries. The percentage wanting some other language was the same as the number coming from other non english speaking countries. Surprise.

On the other hand, 54% said English would be OK I suspect this result is a bit self-selecting, because this blog is written in English....

@jp - would you like to run this poll in german on your site?

One the whole, the demand looks healthy, particularly for on site training and training in local languages. (And Scrum Trainers know what they have to do to improve their training offerings...)

Next week, I want to revisit the poll on managment tools from January 2007.


jp said…
Hi Peter,

oh yes, i COULD do it, but i have an better idea: Would'nt it be great if you could post the german version of this post on my blog? As guest blogger? I can give you an helping hand for spelling and writing...

Cheers, jp
Peter said…
It's deal. Send me an invite :-)



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…