# How a Miro Board Experiment Changed the Way His Team Understood the Big Picture | Njegos Ilic

Page: https://stenobird.com/podcast/scrum-master-toolbox-podcast-agile-storytelling-from-the-trenches-445588/how-a-miro-board-experiment-changed-the-way-his-team-understood-the-big-picture-njegos-ilic
Text version: https://stenobird.com/podcast/scrum-master-toolbox-podcast-agile-storytelling-from-the-trenches-445588/how-a-miro-board-experiment-changed-the-way-his-team-understood-the-big-picture-njegos-ilic.md
Podcast: [Scrum Master Toolbox Podcast: Agile storytelling from the trenches](https://stenobird.com/podcast/scrum-master-toolbox-podcast-agile-storytelling-from-the-trenches-445588)
Published: 2026-05-27T10:05:00+00:00
Episode link: https://scrummastertoolbox.libsyn.com/how-a-miro-board-experiment-changed-the-way-his-team-understood-the-big-picture-njegos-ilic
Audio file: https://traffic.libsyn.com/secure/scrummastertoolbox/20260527_Njegos_Ilic_W_Up2.mp3?dest-id=246429
Processing state: not_requested
JSON: https://stenobird.com/v1/public/podcasts/scrum-master-toolbox-podcast-agile-storytelling-from-the-trenches-445588/episodes/how-a-miro-board-experiment-changed-the-way-his-team-understood-the-big-picture-njegos-ilic
Duration seconds: 683

## Resource

Njegos Ilic: How a Miro Board Experiment Changed the Way His Team Understood the Big Picture 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 . "Every feature is a product bet. I would call this a process bet — just try to see what works best for you." - Njegos Ilic Njegos shares a change story from his time working with a tech lead who had previously been a Scrum Master — a partnership that made all the difference. Together, they introduced a simple but powerful change: visualizing the team's work on a Miro board instead of relying on a standard ticket board with cards and status columns. They mapped out concepts, connected ticket numbers to a visual representation of how different pieces of work fit together, and used this board during dailies and refinements to track progress in context. The change wasn't imposed top-down — Njegos and his tech lead simply said, "Give us one sprint to try this. If it doesn't work, we drop it." The result was immediate: dailies became more engaging, the team could see how their individual work connected to the bigger picture, and Njegos found it much easier to track progress as a visual thinker. His advice for Scrum Masters and product owners who want to introduce something similar is refreshingly simple — frame it as a "process bet," just like you'd frame a product bet. Try it, measure what happens, and if it doesn't work, drop it and try something else. The willingness to experiment with your own process is a prerequisite for experimenting with the product itself. Self-reflection Question: What "process bet" has your team been avoiding — and what would it take to just try it for one sprint? [The Scrum Ma…

## Actions

- request_transcript: `POST https://stenobird.com/v1/public/podcasts/scrum-master-toolbox-podcast-agile-storytelling-from-the-trenches-445588/episodes/how-a-miro-board-experiment-changed-the-way-his-team-understood-the-big-picture-njegos-ilic/transcription-requests` — Idempotently request low-priority transcript generation for this episode.
- read_markdown: `GET https://stenobird.com/podcast/scrum-master-toolbox-podcast-agile-storytelling-from-the-trenches-445588/how-a-miro-board-experiment-changed-the-way-his-team-understood-the-big-picture-njegos-ilic.md` — Read the agent-friendly Markdown representation of this episode resource.

A page view does not enqueue transcription. Agents should invoke `request_transcript` explicitly when they need this episode processed.

## Transcript

Full transcripts are not published on public pages unless there is a clear rights basis.