Podlipodcast player Webplayer

Scrum Master Toolbox Podcast: Agile storytelling from the trenches

Scrum Master Toolbox Podcast: Agile storytelling from the trenches

Why the Product Trio Breaks the Hand-Off Mentality That Kills Team Engagement | Njegos Ilic

Scrum Master Toolbox Podcast: Agile storytelling from the trenches · May 26, 2026 · 15:01

0:0015:01

Listen in the Podli app 🎧

Follow your favourite podcasts, listen offline and in the car with CarPlay and Android Auto, and always pick up where you left off. Free to try.

Njegos Ilic: Why the Product Trio Breaks the Hand-Off Mentality That Kills Team Engagement

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 .

 

"I can't change people, but I can definitely involve them." - Njegos Ilic

 

Njegos describes a pattern he's encountered multiple times as a product owner: teams where engagement is almost nonexistent. He walks into a refinement session, presents ideas, asks for feedback — and gets crickets. Nobody pushes back, nobody asks questions, nobody challenges the assumptions. The result is a product owner working in isolation, defining everything alone, only to discover gaps during development that could have been caught early with a single conversation. Njegos is honest about the limits of what any one person can do — you can't change people's personalities, and expecting a Scrum Master to do so is unrealistic. But what you can do is involve people. His approach when joining a new team: don't come in announcing how things will work. Instead, learn how the team already works, meet them where they are, and then find ways to fit new concepts into their existing rhythm. For the non-negotiable things — the red lines — he's precise, open, and always provides an alternative rather than just pushing his way.

 

In this segment, we talk about Discovery and Delivery and the Product Trio concept.

 

Self-reflection Question: When you join a team meeting and get silence instead of feedback, do you assume agreement — or do you treat it as a signal that something deeper needs to change?

<h2

Episodes: Scrum Master Toolbox Podcast: Agile storytelling from the trenches

PodliGet the free Podli app
↓ App