You know that moment in sprint planning when everyone reveals their story point estimates simultaneously, and the numbers range from 2 to 13? That's not a planning failure—that's collaborative dice rolling at its finest. Just like a D&D party assessing whether they can take on a dragon, your development team is essentially asking "What are the odds we can pull this off?" The answer, as any seasoned dungeon crawler knows, depends on your party composition, available equipment, and whether anyone remembered to bring healing potions.
Scrumgeons & Dragons: Why Your Development Team Is Just a Really Organized D&D Party
Ever notice how a well-run Scrum team feels suspiciously like a D&D campaign? The Scrum Master guides the narrative, developers bring specialized skills to overcome challenges, and everyone rolls dice (story points) to see how badly they've underestimated the complexity of "simple" tasks. After years of facilitating sprints and rolling d20s, I've realized these frameworks aren't just similar—they're practically the same game with different terminology.
Surprise Driven Development
Welcome to Surprise Driven Development (SDD) — the revolutionary methodology where uncertainty isn't a bug, it's a feature. Why plan when you can panic? Why document when you can discover? Join me as we explore the chaotic art of building software where every deployment is Christmas morning and every bug is a delightful present from your past self.