Should you use Scrum in 2024? πΊοΈ
A first-principles approach to dev process frameworks, plus a ton of real-world stories from the community.
Last month I started doing weekly interviews for the podcast. I have done four already, and one of the topics that comes up the most frequently is development process.
In the recent chat with Aadil Maan, we discussed how the best teams often take pieces from canonical frameworks like Scrum or Kanban, and mix&match them to fit their needs.
Is this how you should think about them? Or is it good, sometimes, to just trust the framework and slap it onto your team?
The answer is less trivial than it seems.
Two years ago I wrote a full piece about Scrum. I have used Scrum for many years β at first, almost religiously, then less and less so, until we could hardly call it Scrum anymore.
Later, since I started Refactoring, I have had the chance to talk with countless managers and CTOs about their dev process and how it evolved over time.
So, today we will try to connect the dots, and write an updated take on Scrum and, more in general, how to use frameworks for good.
Here is the agenda:
π The Role of Processes β what we should expect from them.
βοΈ Criticism to Scrum β why people complain about Scrum.
π¨Β The meta-dev cycle β a first-principles approach to what the dev cycle should do.
π½ Team Maturity β how your team stage impacts what the best process looks like.
π± Product Maturity β how your process should evolve alongside your product.
π¬ Community Examples β five stories and processes from real-world companies
π Bottom Line β parting advice to summarize what we covered.
Letβs dive in!