

ScrumBan... Is it real? Or just Camouflage?
7 snips Oct 9, 2025
The discussion begins with skepticism around Scrumban, highlighting its potential as a camouflage for team shortcomings. Lee explores how adopting Scrumban can signal a lack of commitment and how it often leads to chaotic practices. He critiques common pitfalls like erratic sprint lengths and poorly prioritized backlogs that hinder team effectiveness. However, there’s a silver lining as Lee outlines conditions under which Scrumban could thrive, emphasizing the importance of high-trust teams and strong coaching.
AI Snips
Chapters
Transcript
Episode notes
Scrumban As Camouflage
- "Scrumban" is often a camouflage used when teams avoid Scrum's discipline rather than a deliberate hybrid choice.
- Lee Henson says many teams label undisciplined processes as Scrumban to dodge accountability.
Keep Sprints Timeboxed
- Avoid dynamic sprint lengths that change whenever someone wants to add scope mid-sprint.
- Preserve timeboxes and sprint goals so your team can finish and learn from each iteration.
Backlog Needs A Vision
- A backlog without vision becomes a noisy list of tasks with no prioritization or narrative.
- Lee Henson warns this reduces teams to feature-delivery units lacking strategy or discovery.