
Scrum is simple. There, I have said it!
The Scrum Guide used to describe Scrum as being “simple to learn” and “difficult to master”. I agree it is (or should be) simple to learn. It can be learned quickly and easily in a variety of ways. Most people learn from experience, from reading the Scrum Guide and a few good books or attending a Scrum training course.
I would argue it is actually also relatively simple to master Scrum. What is difficult to master are the circumstances, environments and challenging projects and products where Scrum is put to use. Scrum will highlight issues, problems and challenges in these places. It is solving these issues that is the difficult thing that will take a lifetime to master.
Many people I come across view Scrum as something complicated. This should simply not be the case. Scrum is designed to help you solve complex issues, but should not in itself be complicated or complex. It shouldn’t take 10,000 hours to learn how to use Scrum effectively. If it does you are likely missing the point of it which is to help you manage and reduce complexity, not add to it.
Scrum helps you implement an empirical approach (transparency, inspection, adaptation) to find and test solutions to the problems you face. Yes, the problems you face may be complex, but Scrum itself is not. It should help you deal with complexity, not add to it. Scrum is simple!




