Skip to main content

Are agile trainers agile?

There are literally hundreds if not thousands of people out there who will train you to do Agile (and some will even try to convince you to be Agile). Some of them are certified, some are not. How many of them apply Agile to their own profession? I believe the answer is "not many," and I have realized that I was not one of them. This a-ha moment help me refine the purpose of my CST mentorship program.

When people say "Agile", most people are referring to the four values of the Agile Manifesto. While these are important, I believe the fundamental definition of Agility is contained not the four values, but the first statement: We are uncovering better ways of developing software by doing it and helping others do it. (emphasis added).

I don't develop software, I train people to do Scrum. Actually, I like to believe I enable them to turn their current project into their best project ever, so maybe this "training Scrum" is too limiting. Hmm... let's not go overboard just yet! So what would my manifesto look like? Here is the first draft:
We are uncovering better ways of teaching Scrum, by doing it and helping others to do it! -- Peter Stevens
This has become the overarching goal of my CST Mentorship idea. Not just to get you through the TAC, but to create a community of like minded Agile trainers, who help each other to become better trainers, and help others to do the same.  It is no longer just a CST mentorship program, but a CST Mentoring Network.

P.S. I went looking for trainers who are active and transparent about mentoring. I have only found two (including myself):


Does anyone else belong on this list? Please let me know!


Comments

Adrian Christen said…
Dear Peter

Thank you for clarifying "agile" vs. "Agile"! As Jurgen Appelo has written in his splendid book "Management 3.0" [1], there is a difference between "agile" and "Agile" and even further while doing "Agile" (software development) you aren't "Agile" - I think :)!

For me, "Agile" is a lot more (!!!) then "doing" scrum, doing "continuous delivery" or what ever "sh*tt*-cool-newbie-thing" you can read or talk about in the context of "Agile". It's something which goes way deeper into your personal behaviour or personality - I think!
And exactly this makes it so hard to live or to explain. (Too) often you can here people say: "Ou hey, I read this awesome book 'The Scrum Guid' - let's do it!" or "Ou hey, I read this 'Management 3.0' thing: let's be Agile!". And for sure I hear too much "Ou hey, I know how, then finally I succeeded the SM certificate." (sorry for that, Peter).

Because of that I'm really interested in your effort creating a network concerning the "Agile"-thing. Maybe we/you look also over the border of the "scrum"-part and have an eye on the "Agile"-lifestyle (or how ever you want to call this "f*ck*ing-sh*tt*-cool-newbie-thing" - LOL!) like "Agile values" and "Agile principles"? If so: I'm in!

[1] http://www.management30.com/product/management30/
Peter said…
Dear Adrian,

The longer I have done Scrum training, the more I have discovered the essence of both Agile and Scrum.

The CSM certificate (or any other piece of paper from the noble and not-so-noble competition) is but one step in a journey. In each step you realize what you did wrong before. I know that's been my case. Inspect and Adapt. We are uncovering better ways...

The Scrum Breakfast Club is about learning. (Yes, it's also about getting the next piece of paper, but, well, employers value paper. What can you do?) I hope you will join us for a workshop soon. I am still working on the Agile training concept. I'd love to hear from you offline if you'd like to talk further!

Cheers, Peter

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 …