Scrum - Three Strikes and You're Out!

My rule for adopting Scrum at your organization is three strikes and you're out.

That is, if you say you're doing Scrum, but not following one of the core assumptions, you can get by, and you'll probably get very good results that help gain support to address and fix the comprimises.

If you're breaking two core rules of Scrum, that's definitely not good, but perhaps you can still get some value for the compromises that you are making. And with some value and time, maybe you'll get support to address these shortcomings.




But if you are breaking three, stop. Ask your leadership, your management if the company is really ready for Scrum. Why? Because you will get marginal results for a LOT if change and disruption. And if you are the one advocating Scrum, your neck is on the line, too.

Here are the most common strikes (could also be any other of the rules of Scrum):

 - Team not co-located
 - Team matrixed on multiple projects
 - Team too big

It could also include
 - ScrumMaster not dedicated
 - PO not available, too busy

I've mentioned this in my classes, and old students have been referencing it, so I thought I'd share it here. 

Our best to you on finding and taking your next step - for you, your team and your company.