Star Wars Agile Retrospectives a Principle 12 Story
Can a metaphor help your Agile Retrospective? Here's my take with Star Wars. Do we want this Agile Retrospective outcome to destroy a tie-fighter or defeat the empire?
I work with software teams on product strategy, technical decisions, and facilitation—usually some combination of all three, because the interesting problems don't stay in neat categories.
Product direction, technical architecture, and roadmap prioritization — helping teams figure out exactly what to build and why.
Code reviews, mentoring, and interim technical leadership — working alongside teams that need depth, not just direction.
Retrospectives, planning sessions, and stakeholder alignment — navigating difficult conversations to reach clear decisions.
Can a metaphor help your Agile Retrospective? Here's my take with Star Wars. Do we want this Agile Retrospective outcome to destroy a tie-fighter or defeat the empire?
Do you feel like your Agile Retrospective is only tackling low hanging fruit and missing out on real improvements? Have you ever wondered if in your retro you're dealing with clear, complicated or complex issues? In this post I write how Cynefin can help with that.
This post assumes you know what a retrospective is and focuses on Kerth's prime directive to ensure the facilitator can answer common challenges and confidently explain it to the group.