Thread by @RonJeffries

Scrum is designed for a single purpose, in my view: If you apply its roles, events, and artifacts, you will experience difficulties — impediments. Your mission is to remove them.
/1 of 13

Some of Scrum’s elements are difficult for some people to do. Especially in early days, this is probably some legacy element of your situation, trying to be identified as an impediment. Your mission is to fix that, not the difficult Scrum element.
/2 of 13

It is tempting, especially in early days, to drop the Scrum element that seems difficult. You are, of course, free to do that, just as you are free to stab yourself with that pencil over there, or to pet that kitty over there.
/3 of 13

Whether you should drop the element, stab yourself, or pet the kitty is a matter of judgment. Scrum assumes that you have judgment. Scrum people are also aware that Scrum elements often seem to Scrum newbies to be the problem, when they are just identifying a real issue.
/4 of 13

So Scrum people advise that when you are new to Scrum, it is probably unwise to drop a Scrum element, thinking that it doesn’t apply to you. You’re too new to really know that, but of course you are free to do it: Scrum assumes that you have judgment.
/5 of 13

Scrum’s creators, especially Ken, wish that if you are not doing all the Scrum elements, you would not call what you’re doing Scrum. This makes perfect sense. If you are eating meat all day, you should probably not talk so much about being a vegan.
/6 of 13

Now, someday, you may choose to eliminate some Scrum element, perhaps to replace it with something else. If you are new and inexperienced with Scrum, this might not be wise, but it is entrely legal. They hope you won’t call the resulting thing “Scrum”, is all.
/7 of 13

And someday you may know enough to replace a Scrum element and do so quite wisely. That might be the first day: more likely it will be many days in. Be that as it may, there definitely are better elements than Scrum’s, at least for experienced folks.
/8 of 13

There are also other places to start that are perfectly OK. If you don’t want to do Scrum, pick one of those. Or even make up your own: it’s all good, we’re all grownups here. Judgment, remember?
/9 of 13

Summing up, Scrum is one of a number of good ways to start trying to improve. It’s not the only one. It is not mandated by law in any jurisdiction. If you’re new to these ideas, and it seems interesting, give it a try.
/10 of 13

I’d advise sticking with it a bit, improving other things, rather than changing Scrum’s elements. I’d advise that for any packaged approach you try: the people who created it know a lot and following their guidance for a while will probably be helpful.
/11 of 13

But by all means, if the shoe doesn’t fit, don’t wear it. Feel free to drop out of Scrum, drop some of its elements, replace its roles with Gods and Demons, whatever makes sense to you. You have judgment and it’s your effort in the end.
/12 of 13

Do as you will. No one has said otherwise. Some people do ask that if you’re going to do something other than Scrum, you not call it Scrum. Don’t confuse that for a moral judgment. It’s a trademark matter, and little more.
/13 bad luck? END