Jesse Fewell has written a blog post called Scrum Is Dead. Long Live Scrum. His viewpoint is that the old Scrum is dead, and that it is morphing into something new. In the comments, Jesse asked the following question in response to my call for the Scrum Alliance to focus on the Software Community:
Hereâ€™s my question though, if the SA isnâ€™t going to be the one to apply agile thinking to lawyers, financial analysts, music producers, and managers, then who will? Are tech workers the only knowledge workers worthy of agile thinking?
Scrum Alliance Background
(If you donâ€™t want all of the background, skip to Cory Gets to the Point)
Itâ€™s a good question. Letâ€™s start with why the Scrum Alliance exists. On their web site it says:
The Scrum Alliance is a nonprofit organization committed to delivering articles, resources, courses, and events that will help Scrum users be successful.
But if you scroll down and look at the Form 990 filed for tax year 2008, it says:
Scrum Allianceâ€™s mission is to promote increased awareness and understanding of Scrum, provide resources to individuals and organizations using Scrum, and support the iterative improvement of the software development professions
(Emphasis mine). Further, in section 4a it says:
Scrum Alliance is organized and operated exclusively for purposes of furthering the advancement of the â€œScrumâ€ software development process
(Again, emphasis mine). And while the board members arenâ€™t compensated, the managing director made, in 2008, $240,000 USD. In fact, all told, the Scrum Alliance paid out three quarters of a million dollars in â€œindependent contractingâ€ fees.
Not bad for managing a 3-person staff of independent contractors. Full disclosure â€“ I worked as an independent contractor for 6 months for the Scrum Alliance. I imagine my compensation should be available in the 2009 filing form. But, letâ€™s just say, it was pennies compared to the above numbers.
Ok, so now that we see that the Scrum Alliance states their purpose is furthering software development, letâ€™s look at the break down of staff:
- Managing Director
- Creative Director (new as of this year â€“ Tobiasâ€™ position)
- Membership Coordinator / Website Coordinator
- 5-person board
And the heart of Jesseâ€™s question becomes, what is the most effective use of a team like that?
SoftwareScrum < Scrum::BaseScrum
Well, letâ€™s look at the existing programs:
- Certified Scrum Master
- Certified Scrum Coach
- Certified Scrum Product Owner
- Certified Scrum Trainer
- Scrum Gatherings (4-5 per year held around the globe)
- Community outreach (funding of User Groups, Welfare CSM, etc)
Which seems to be the right lineup for what Scrum is (3 roles â€“ ScrumMaster, Product Owner, and â€œOtherâ€). So, in fact, if one was going to set out to â€œTransform the World of Workâ€, then keeping the offerings and programs industry agnostic seems like a good thing. Except for one thing.
Magic. Magic is the little dots in the Scrum diagram which shows what actually happens in those 2-4 weeks sprints, and those 24-hour increments. In software terms, Scrum is an abstract class, which doesnâ€™t implement Do24Hours() and DoIteration(). You have to do that. Anyone implementing Scrum has to do that. Itâ€™s that magic which distinguishes the successful teams from the non-successful ones. Itâ€™s where Lean and Kanban and XP and all sorts of other things get put in. Or, in other industries, where the real work happens.
For example, if Iâ€™m a Lawyer, that 24-hour period, or that iteration, Iâ€™m going to be going to court, preparing cases, visiting my clients, bribing judges, etc, etc. Or if Iâ€™m a movie producer, Iâ€™m going to be coordinating shoots, editing previously filmed clips, pampering the actors and actresses, etc.
Which means that if we want Scrum to be successful, what happens during that 24-hour period, or that iteration, has to be successful. If it isnâ€™t, then what happens outside of it â€“ the product management, the demos, the daily stand-ups â€“ doesnâ€™t mean diddly.
(Also known as Cory Gets to the Point)
I estimate that 75% of those organizations using Scrum will not succeed in getting the benefits that they hope for from it.
Proof is in the pudding. If Scrum isnâ€™t executed successfully, it doesnâ€™t work. Which means that if we want Scrum to succeed, then we need to be helping those teams figure out what happens in the â€œmagicâ€ areas of the Scrum process.
So far, so good. Jesseâ€™s question still stands â€“ why not help everyone find the magic quadrant?
Because we canâ€™t. The one thing any coach will tell you is that every engagement is different. Some political game. Some quirk about the product. Some jursidictional rule. Some working hour filming requirement in Pago Pago. But, if the Scrum Alliance wants to help, there are at least two options:
- Build a Community of People to Implement Scrum In Specific Industries â€“ Letâ€™s recognize that each industry has specific needs, and therefore will need Scrum taught different ways. In fact, it was already recognized with the creation of the PMP CSM class held earlier in 2009 (I canâ€™t find a link right now). But to expand, you need leaders, and to get leaders, you have to seed the community. The existing CSP/CST program isnâ€™t setup for that at all. So drop it. Stop centralizing the certifications from CSMs all the way up to the CSTs and push that out to the industry-specific subgroups.
- Get Scrum Working Well in One Industry â€“ Scrum started to help software teams, and its stated purpose is to help software teams. Yet 75% of the teams arenâ€™t getting the benefit. Hello? Is anyone listening? Why donâ€™t we find how to fix that problem before spreading out to lots of other industries?
Hereâ€™s how I look at it. You have a board and directorship of software industry leaders. You have thousands of people in the software industry using Scrum. You have people begging for better ways to do software. And you have your founder saying that 75% of teams arenâ€™t getting the benefit. You want to look at all that and say, â€œLetâ€™s branch out?â€
Look over to your right. Thatâ€™s a laser going through a prism. Alright, thatâ€™s what happens when a laser goes through a prism. It gets split into lots of shiny objects. That are so very pretty to look at. And hear about. Now watch this video:
The Scrum Alliance can be a shiny object, pretty to look at, fun to talk about, neat for a demo or two. Or it can be a focused cost and quality-overrun killing machine by helping the software industry find out what is in those magic circles which is causing 3/4s of the users to not get the benefit. Or, to put it in real numbers, find out why of the members who paid collectively a tad over $2.6 million in 2008, three-quarters (or around $2 million dollars worth of fees) arenâ€™t getting the benefit they should be getting.
So, Jesse, thatâ€™s why. The Scrum Alliance canâ€™t hold the keys and want to open the doors at the same time. Either fix what is broken, or split off an industry specific group which has control over the certifications for that industry and can fix it for them.
Personally, Iâ€™d prefer to see the certifications dropped and the Scrum Alliance focus on fixing the industry-wide pandemic we call software development. But thatâ€™s just me.
Edit: William Pietri points out that lasers are monochomatic, and so when shot through prisms, they split into multiple beams as shown here. It’s still shiny objects with less power than the original – just better represented. Thanks William!