In this episode of Good Intentions and Bad Outcomes, hosts Gino and Wayne explore how product demos and sprint reviews, while well-intentioned, can sometimes lead to counterproductive outcomes in agile teams.TIMESTAMPS:0:00 - Introduction0:43 - Wayne introduces the topic of product demos and sprint reviews1:32 - The good intentions behind product demos2:16 - When demos become counterproductive3:43 - Teams turning demos into elaborate productions5:17 - The "no code check-ins before demo" problem7:16 - The "fake demo" with screenshots instead of working software9:21 - Solution 1: Clarify the true purpose of demos11:03 - Solution 2: Show what you've done without extra preparation11:44 - Solution 3: Drop PowerPoint and use your existing tools13:00 - A success story: How a technical demo led to project simplification15:01 - Solution 4: Don't wait for perfect software to demo16:17 - Conclusion and invitation for listener storiesWayne and Gino discuss how sprint reviews and product demos, while intended to showcase progress and gather feedback, can sometimes become elaborate productions that waste development time or turn into competitive performances between teams. They share real examples of teams spending days preparing for demos, creating presentation decks instead of showing actual software, and prohibiting code check-ins before demos to avoid potential issues.The hosts offer practical alternatives including:- Reminding everyone that demos are primarily for feedback, not performances- Showing actual working software rather than presentations or screenshots- Eliminating extra preparation by simply demonstrating what's been completed- Building confidence to demo work-in-progress features for earlier feedback- Using existing tools (Jira, wikis) instead of creating separate presentationsIf you've experienced situations where well-intended workplace processes have backfired, share your story for a chance to be featured in an upcoming episode! Contact us at [email protected]

Ver todos los episodios