Like many, I’ve been spending time with the Scrum Guide Expansion Pack. I’m still digesting it. ⛰️ At first I was viewing it through the lens of someone immersed in the work and the practice. But I’ve since shifted perspective - looking at it more as a #product, and more importantly, through the lens of #adoption. There’s real #utility here - and credit to the contributors - the time, thinking, and effort that’s gone into this is clear. That energy deserves recognition. But reading it gradually (on my iPhone, obviously), it feels less like something snackable and more like a seven-course meal. High utility, but high energy to adopt. It’s not small. It’s not easy to get into. It reads more like a collected body of work - some of it emerging, especially around #AI - than a true extension of the #Scrum Guide. That’s not a criticism. It adds value through context and searchability. But naming it an “Expansion” sets a different expectation: something lightweight, practical, and immediate. Scrum itself offers that in the Scrum Guide. This is heavy. Because it includes emerging areas, some parts will date quickly. That raises the maintenance overhead and impacts its longer-term utility. Bloat creeps in. Extensibility takes a hit. I keep circling back to the name. “Expansion” doesn’t quite land for me. “Collected Thinking” or something along those lines might be closer to the mark. I’ll keep reading, keep digesting. But right now, it feels more like a well-organised Wikipedia subsection than something I’d plug in and use straight away. TL;DR - It feels like Windows Vista - for Scrum. #AgileDelivery #ProductThinking #ScrumGuide #AgilePractices #AgileTransformation #ProfessionalPractice #TeamDesign #AgileLeadership
TL;DR - It feels like Windows Vista - for #Scrum.
Like many, I’ve been spending time with the Scrum Guide Expansion Pack. I’m still digesting it, but here are some early and evolving thoughts.
#AgileDelivery #ScrumGuide #AgilePractices #ProfessionalPractice #TeamDesign
