Is Scrum hard to learn?
The Scrum framework is small: three accountabilities, five events, three artifacts. What is hard is applying it. Here is why, and how to shorten the curve.
Scrum is easy to describe and hard to do. The 2020 Scrum Guide is 13 pages. You can read it on a train ride. You can memorise the three accountabilities, the five events, and the three artifacts in an afternoon.
None of that will make you good at Scrum.
The framework is small on purpose
Scrum is deliberately underspecified. It tells you to inspect and adapt, but not what to inspect. It tells you to protect the Sprint Goal, but not how to say no to the VP who wants a favour. The framework leaves the hard work to you.
What is actually hard
- Saying no to a stakeholder without breaking the relationship.
- Coaching a Developer to answer their own question when you already know the answer.
- Ordering a backlog under conflicting definitions of value.
- Holding a Retrospective that changes the team's behaviour instead of producing a list of grievances.
- Deciding an increment is not Done when 90 percent of it is.
None of these are in the Scrum Guide because none of them can be. They are judgement calls that get better with reps.
The shortest path
Read the Scrum Guide. Then get reps, either on a real team or in a simulator that puts you in the moments the framework does not describe. Reading a second book on Scrum before you have felt a bad Sprint is a mistake.
Scrumling exists for this second step. Ten browser-based Scrum games that make you feel the pressure of a real Sprint. Free.