Skip to main content

Do you believe in the Scrum Alliance?

I got an interesting inquiry today:
I am a Scrum Practitioner and agile believer too. The reason of my contact is regarding a blog post I came across in your blog - scrum breakfast. I'd like to first thank you for providing visibility of important changes happening in Scrum Alliance and I would like to ask you what will be your position towards your membership in Scrum Alliance. Will you continue to be a member? Will you move to Scrum.org ? What would you recommend for someone who is a CSP trying to pursue a Trainer status at this moment in light of these big changes that happened in Scrum Alliance? Thanks.
My response:

The jury is still out on why these changes occurred and what they mean for the Scrum Alliance. I still believe in the Scrum Alliance so I am working to make it a better place. I am unlikely to move to scrum.org.

I do believe that CSTs represent the highest standards in the industry, and would encourage you to pursue CST certification. AFAIK, the CST is the only Scrum trainer certification for which candidates must a) apply as opposed to being recruited (if not spammed!) and b) demonstrate guide-level competency in Scrum theory, practice and teaching skills. I believe that if you are a CST, any Scrum oriented organization would be happy to have you.


Update: I have included a link to the InfoQ article about the changes. Scrum Alliance Directors Resign. Four directors resigned, the Secretary stepped down, and one director returned.



Comments

bigpinots said…
What changes at Scrum Alliance are you referring to Peter?
bigpinots said…
Peter, what changes in Scrum Alliance is your post referring to?
Peter said…
Several Board resignations (and one return in the space of a few months. AFAIK the only reporting on the changes has been article on InfoQ: Scrum Alliance Directors Resign

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 …