Episode
The Team That Gave Up — When Green Reports Mask a Sinking Ship | Maria Skvortsova
- Published
- Jun 2, 2026
- Duration seconds
- 914
- Processing state
not_requested
Actions
POST https://stenobird.com/v1/public/podcasts/scrum-master-toolbox-podcast-agile-storytelling-from-the-trenches-445588/episodes/the-team-that-gave-up-when-green-reports-mask-a-sinking-ship-maria-skvortsova/transcription-requests
Idempotently request low-priority transcript generation for this episode.GET https://stenobird.com/podcast/scrum-master-toolbox-podcast-agile-storytelling-from-the-trenches-445588/the-team-that-gave-up-when-green-reports-mask-a-sinking-ship-maria-skvortsova.md
Read the agent-friendly Markdown representation of this episode resource.
Summary
Maria Skvortsova: The Team That Gave Up — When Green Reports Mask a Sinking Ship Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes . "They said, 'Yeah, we know, but no one will listen to us.' And they just gave up — waiting for the ship to sink so they could swim away." — Maria Skvortsova Maria walked into a 20-person migration team where the PowerPoint reports glowed green but the reality on the ground was covered in red flags. Developers were building features against requirements that had already changed — nobody had told them. The scope was impossibly large, and when Maria asked the team why they hadn't raised a red flag, the answer shook her: "No one will listen to us." The team had given up. They were waiting for the project to fail so they could leave. Maria's first instinct was to observe — spend weeks understanding the dynamics, the communication patterns, the culture. But she learned the hard way that when a team is already drowning, there's no time for a slow ramp-up. She needed to act immediately. Her breakthrough came from a simple technique: replacing some daily standups with an async RAG (Red-Amber-Green) status system in Jira. Team members just chose a color for each story — no explanation needed. It gave them psychological safety to signal problems without speaking up in a 20-person meeting. From there, Maria broke the team into smaller cross-functional groups — one QA, one developer, one consultant — so they could actually discuss features instead of hiding behind silence. In this episode, we refer to Zombie Scrum Survival Guide by Christiaan Verwijs, Johannes Schartau, and Barry Overeem . Also check out the episode with Ba…