Why I Still Teach Scrum

Scrum is an agile method (framework) that when instantiated can be rather ornate. Most developers, when I talk to them, tell me that when given a choice they would not be doing Scrum. While Scrum may have felt much lighter than the competition back in the nineties, today it weighs in as rather heavy.

Given this, I wanted to reflect on why I still teach Scrum (and have a blog post to point any of my students to).

It is really quite simple. Experienced people in well-working teams and/or functional working cultures don’t need Scrum. Scrum is great for anyone who doesn’t know how to go about software development yet (e.g. students facing their first team project) or for people with divergent experiences and backgrounds (e.g. reshuffled teams, corporate mergers). By taking everyone by the hand and having a method or process for every step along the way, Scrum can help build teams while picking up some initial speed.

I think the metaphor of training wheels is apt. You can get started with Scrum, but you will want to get rid of it as soon as you can.

5 Replies to “Why I Still Teach Scrum”

  1. While I agree that Scrum is good for getting started and certainly better than pretending to follow a formal process and being chaotic in reality, I wonder what you would rather recommend?

    1. From my experience of talking to companies, teams quickly let go of too much process and move to a combination of Kanban + CI/CD pipeline. I’m not sure there is a name for it, and there is plenty of variety. Larger organisations are also starting to add inner source to reintroduce a component quality perspective, which makes a lot of sense to me, but is not yet wide-spread.

  2. I’m interested in that blog post you are pointing your students to! Can you share the link with us?

Leave a Reply