Is it simple? Depends upon what you mean by "it"

 

For years scrum has stated it's "simple to understand, difficult to master." The problem with simple to understand is that that what's important is how simple it is to use. This is a major difference in philosophy between Scrum proponents and those using Flow, Lean and ToC. We focus on "simple to use."

Consider bikes. A one speed bike is simply built, easy to understand, easy to start with but not necessarily easy to use. If you're biking up hill for a long time you might find a 27 speed bike geared somewhere between 1 and 9 better. You can keep it simple to understand by having someone who knows bikes set the speed before you use it.

You can also start with simple braking - just use the right brake (safest and easiet to use). When the rider is more experienced you can tell them about the left (front) brake.

Simple is related to "fit for purpose." A one speed bike may be fit for purpose in some places, but it certainly isn't fit for purpose everywhere. A well designed system can expose it's extra features as people are ready for them.

Disciplined Agile Scrum is designed to be simple to start with and use and to be expandable as needed. Might be a little harder for the consultant, but that's why you want a DA Scrum Master.

for more blogs on Scrum go to Blogs and Videos on Scrum.