All About Agile | Agile Development Made Easy


Lame Scrum Implementations

by Joe Little, 18 May 2011 | Scrum

This content is syndicated from Agile & Business by Joe Little. To view the original post in full, click here.

I was talking to a colleague about one problem, and then said, "but this is not our biggest problem -- our biggest problem is lame scrum implementations." So, I thought I would discuss that. First, truly, our biggest problem is not Scrum or anything to do with Scrum. Our biggest problem is to figure out what "the good life" is, and then to live it. (A nod to Socrates.) But, if we take the premise in business (which I do) that Scrum helps us live the good life, then anything that hurts Scrum, hurts us. And I think Scrum, unfairly, is getting a bad reputation because of lame Scrum implementations. And, more to the point, people are suffering with 'less good' lives because of bad Scrum implementations. Now, in every case I have seen, a bad Scrum implementation is better than what they were doing before. Still.... OK. What are the root causes of bad Scrum implementations? Here are my top 5. 1. Bad team. By this I mean a team that is fundamentally not competent for the work that they have to do, or is fundamentally dysfunctional. This is pretty darn rare, but I have seen it happen. 2. Bad company. This is a company or company culture that apparently does not allow any impediments to be removed. Or almost none. Or only at great human cost. I find this issue to almost always be there, to some degree. Except that I feel (and yes, Virginia, it is hard to call this more than a feeling based on lots of experience) that people feel more powerless to change the company than they really are. Now I have companies so bad that I have said "well, if you can't change your organization, you have to change your organization." Still, as the key root cause, overall I rate it fairly low (second). 3. Low knowledge. Mainly this is low knowledge of Scrum, or of how to make a business case to managers to fix the impediments around here. I find this very common, bordering on universal. But the main root cause of this cause (ie, the reason is does not get fixed sooner) is a lack of aspiration. IMO. People always misunderstand Scrum to some degree. People always do it wrongly (at least for the first two years), as any beginner does with any sport or any musical instrument. We have knowledge decay. Etc, etc. This is not so hard to fix once we recognize it and mitigate it. 4. Serious technical debt. I won't try here to define technical debt. But let's just say that legacy systems are hard to change. So, the team that works with a 'bad' legacy system can seem to have a lame Scrum implementation and get almost no velocity of new story development. And the underlying problem is serious technical debt. Again, this can be fixed in due time. If there is the aspiration to do so. 5. Not sufficient aspiration. So, this ends up being the classic problem of leadership. How to... a. Get them to see a common problem that they really want to fix, and b. Get them to feel that it is not impossible to fix it. Or...how to ask for something, but not too much. So, earlier I have almost said that lame Scrum implementations arise, fundamentally, because of lack of aspiration. Either people don't see the possibilities or they don't want them enough. I think Scrum holds a lot of potential. In every dimension of improvement that we want. So, why is this not seen better? I think there is no one person to blame. We can all get better. The 'Scrum guys' (such as I am) can explain it better. The leaders can lead better. The teams can have more courage. And the teams will have more courage in time, as they start to believe we actually really mean 'self-organizing' in a sensible way...that it is not just another of a thousand meaningless slogans. Does this breakdown of root causes show you a path to action?

Home



Leave a Reply

What is 2 + 7 ?
Please leave these two fields as-is:
Please do this simple sum so I know you are human:)