About this episode
Why Is ‘Make Work Visible’ one of the three Scrum artifacts? Why does it matter and how can you apply it to non-technical and non-scrum initiatives?
- Making Work Visible doesn’t seem like an artifact, but in fact is a way of thinking about delivery and status that eliminates the overhead of collecting and producing status reports
- The easiest way to make work visible is to publish done things, but there are many other practices that make true ’status’ more available and transparent
- These techniques also apply to non-technical product
Get every episode summarized
Each time Badass Agile publishes, we email you a written briefing from the transcript — the topics, who appeared, and any specific claims, with the ad reads skipped.
Email me new episodesFree for 3 shows. No card needed.
Hosts & guests
No transcript yet
This episode has not been transcribed. Request it and it moves to the front of the queue.
More episodes
More from Badass Agile
The Forge, Forge, Forge Lightning and Forge Genesis
Badass Agile
May 5, 202615:32pending
AI Agile Hype Creates a Leadership Trap
Badass Agile
Apr 28, 202610:30failed
The 1 Thing Agile Coaches MUST Do More Of
Badass Agile
Apr 15, 202611:33failed
Agile In 2026 – The 4 Pillars of Leadership
Badass Agile
Mar 26, 202616:21failed