In this episode, Matthew Coxall introduces Harmony: Building Coherent Product-Led Organisations, his new book exploring why capable people, teams and leaders still experience so much organisational friction.

Matthew discusses the patterns that often sit beneath delivery challenges: unclear ownership, decision latency, project-based funding, governance friction, rising technical debt, weak alignment and teams working from different assumptions.

Rather than presenting another framework or transformation playbook, Harmony offers a practical lens for understanding how Product, Engineering, Design and Business can work together as a coherent system.

The episode explores why many organisations struggle despite adopting Agile practices, product operating models and digital delivery approaches, and why sustainable improvement depends on the conditions around teams, not just the methods they use.

Harmony: Building Coherent Product-Led Organisations is available now on Amazon in paperback, hardback and Kindle.  

Support the show

Enjoyed the episode?
Don’t forget to subscribe to Agile Product Hub for more deep dives into Agile roles, real-world practices, and product thinking that delivers.

Explore the Harmony series for organisational guidance  or the full Agile How To book series for hands-on guidance tailored to Product Owners, Scrum Masters, Developers, and Agile Leaders.

Visit AgileProductHub.com to access resources, templates, and training designed to help you thrive.

The views and thoughts expressed in this podcast are those of the author. 
Podcast created on the notebookllm platform

🎧 #OrganisationalFrictionSeries | #AgileHowToSeries | #AgileProductHub

More governance does not always create more confidence.

In this episode of the Organisational Friction Series, we explore how governance can sometimes shift risk rather than reduce it, especially when decisions are pushed upwards, expertise arrives too late, or approval becomes a substitute for clear decision rights.

We look at the difference between guardrails and stage gates, why some formal approvals are entirely appropriate, and where repeated approval can create delay, diffuse accountability and weaken learning.

We also explore what healthier governance looks like: clear boundaries, earlier specialist involvement, proportionate evidence, intentional escalation and governance that helps people make better decisions closer to the work.

A question to take back to your organisation:

Where does governance genuinely reduce risk, and where does it mostly move responsibility somewhere else?

And then:

What would need to change for that governance to help the people closest to the work make a better decision earlier?

The episode draws on Matthew Coxall’s upcoming body of work around Harmony, including Harmony, The Harmony Operating Model and Harmonised.

Listen at https://agileproducthub.com/podcasts

Available on your favourite podcast platform.

Support the show

Enjoyed the episode?
Don’t forget to subscribe to Agile Product Hub for more deep dives into Agile roles, real-world practices, and product thinking that delivers.

Explore the Harmony series for organisational guidance  or the full Agile How To book series for hands-on guidance tailored to Product Owners, Scrum Masters, Developers, and Agile Leaders.

Visit AgileProductHub.com to access resources, templates, and training designed to help you thrive.

The views and thoughts expressed in this podcast are those of the author. 
Podcast created on the notebookllm platform

🎧 #OrganisationalFrictionSeries | #AgileHowToSeries | #AgileProductHub

When everything is important, everything is urgent, and every stakeholder has a legitimate reason why their work cannot wait, something predictable happens:

Teams get busier, but meaningful progress gets harder.

In this episode of the Organisational Friction Series, we explore why prioritisation is not simply about ranking work. Real prioritisation requires trade-offs, sequencing and deciding what will not receive attention yet.

We look at how strategy, funding, governance, measurement, dependencies and leadership behaviour can combine to keep too much work active at the same time, creating context switching, hidden queues and constant stop-start movement.

We also explore what healthier prioritisation looks like: fewer active priorities, explicit sequencing, visible trade-offs, clearer ownership of priority decisions and leadership that protects focus rather than continually adding more work.

The episode draws on Matthew Coxall’s upcoming body of work around Harmony, including the Harmony philosophy, The Harmony Operating Model and Harmonised.

A question to take back to your organisation:

If everything currently labelled a priority cannot happen at the same time, who is actually deciding what happens first?

And then:

Is that decision being made intentionally, or is the organisation leaving teams to discover it through overload?

Listen at Agile Product Hub.com and on your favourite podcast platform.

Support the show

Enjoyed the episode?
Don’t forget to subscribe to Agile Product Hub for more deep dives into Agile roles, real-world practices, and product thinking that delivers.

Explore the Harmony series for organisational guidance  or the full Agile How To book series for hands-on guidance tailored to Product Owners, Scrum Masters, Developers, and Agile Leaders.

Visit AgileProductHub.com to access resources, templates, and training designed to help you thrive.

The views and thoughts expressed in this podcast are those of the author. 
Podcast created on the notebookllm platform

🎧 #OrganisationalFrictionSeries | #AgileHowToSeries | #AgileProductHub

Many organisations say they want empowered teams.

Yet those same teams are often expected to seek approval before changing scope, challenging a deadline, protecting technical health, saying no to a request or responding to what they have learned.

In this episode of the Organisational Friction Series, we explore why permission-seeking is often a rational response to the system around the team, rather than a lack of confidence, capability or ownership.

We look at how unclear decision boundaries, governance, funding, measures and leadership behaviour can quietly teach teams where authority really sits. We also explore what meaningful empowerment requires: clear intent, usable authority, trusted boundaries, shared context and leadership support when decisions become uncomfortable.

The episode draws on Matthew Coxall’s upcoming body of work around Harmony, including the Harmony philosophy, The Harmony Operating Model and Harmonised.

A question to take back to your organisation:

What decision does your team repeatedly ask permission to make, even though it already has the context and accountability to make it?

Support the show

Enjoyed the episode?
Don’t forget to subscribe to Agile Product Hub for more deep dives into Agile roles, real-world practices, and product thinking that delivers.

Explore the Harmony series for organisational guidance  or the full Agile How To book series for hands-on guidance tailored to Product Owners, Scrum Masters, Developers, and Agile Leaders.

Visit AgileProductHub.com to access resources, templates, and training designed to help you thrive.

The views and thoughts expressed in this podcast are those of the author. 
Podcast created on the notebookllm platform

🎧 #OrganisationalFrictionSeries | #AgileHowToSeries | #AgileProductHub

In this episode of the Deep Dive on the Agile Product Hub, we explore decision latency, the hidden delay between a decision needing to be made and an organisation feeling safe, clear and confident enough to act.

The episode opens with a simple image: a high-performance sports car, engine roaring, fuel burning, but going nowhere. Many organisations feel the same. They have talented people, clear roadmaps, active governance, full calendars and visible delivery activity, yet work still waits.

Drawing on Matthew Coxall’s Product Agile Harmony, THOM, The Harmony Operating Model, and the Agile How To role books, this episode looks at why decision latency is not just slow decision-making. It is a system signal.

We explore how unclear boundaries, escalation patterns, governance weight, accountability without authority and low trust in local judgement can quietly stop product flow. We also look at how decision latency affects Product Owners, Scrum Masters, Development Teams, Specialists and Engineering Leaders in different ways.

The episode closes with a practical decision confidence check, a set of questions teams and leaders can use when work stalls:

What decision is actually needed?
 Who has the best context?
 Who owns the affected outcome?
 What boundary is unclear?
 What risk is being avoided?
 What would make the decision safe enough?
 Does this genuinely need escalation?

The key question is:

Where is work waiting in your organisation, not because people lack skill, but because the system has not made decisions safe enough to make?

Agile Product Hub podcasts:
 https://agileproducthub.com/podcasts

Available on your favourite podcast platform.

Support the show

Enjoyed the episode?
Don’t forget to subscribe to Agile Product Hub for more deep dives into Agile roles, real-world practices, and product thinking that delivers.

Explore the Harmony series for organisational guidance  or the full Agile How To book series for hands-on guidance tailored to Product Owners, Scrum Masters, Developers, and Agile Leaders.

Visit AgileProductHub.com to access resources, templates, and training designed to help you thrive.

The views and thoughts expressed in this podcast are those of the author. 
Podcast created on the notebookllm platform

🎧 #OrganisationalFrictionSeries | #AgileHowToSeries | #AgileProductHub

Agile leadership is not traditional management with Agile language added.

In this episode, we explore the difference between Agile leadership and traditional leadership, and why leading with harmony, not control, is critical in modern digital product organisations.

We discuss how traditional leadership often seeks confidence through control, reporting, escalation, approvals, and output tracking, while Agile leadership creates confidence through clarity, trust, learning, decision boundaries, autonomy with accountability, and better operating conditions.

The episode also introduces some of the thinking behind Matthew Coxall’s upcoming work on Product Agile Harmony and THOM, The Harmony Operating Model, as a practical way to understand how leadership, product flow, technology, funding, measurement, and everyday decisions interact.

Listen to more Agile Product Hub podcasts:
 https://agileproducthub.com/podcasts

Available on your favourite podcast platform.

Support the show

Enjoyed the episode?
Don’t forget to subscribe to Agile Product Hub for more deep dives into Agile roles, real-world practices, and product thinking that delivers.

Explore the Harmony series for organisational guidance  or the full Agile How To book series for hands-on guidance tailored to Product Owners, Scrum Masters, Developers, and Agile Leaders.

Visit AgileProductHub.com to access resources, templates, and training designed to help you thrive.

The views and thoughts expressed in this podcast are those of the author. 
Podcast created on the notebookllm platform

🎧 #OrganisationalFrictionSeries | #AgileHowToSeries | #AgileProductHub

In this episode of The Deep Dive, we explore one of the biggest tensions in modern agile and product organisations: are agile roles disappearing, or are they simply evolving?

Across many organisations, there is a growing narrative that roles such as Scrum Master, Product Owner, Engineering Leader, and specialist roles are no longer needed in the same way. Under pressure to simplify structures, cut cost, and move faster, some businesses are questioning whether these roles have become overhead.

This conversation takes a different view.

Rather than seeing these roles as outdated, this episode explores how they are maturing in response to a more complex organisational reality. As digital product work has grown beyond small co-located teams into distributed, cross-functional, AI-influenced environments, the demands on these roles have shifted. The challenge is no longer just about following frameworks or managing delivery activity. It is about enabling better decisions, supporting flow, aligning around value, and helping organisations work more coherently across product, engineering, business, and specialist disciplines.

In the episode, we discuss:

•  why so many organisations are rethinking agile roles right now 
•  the old, narrow view of roles such as Scrum Master, Product Owner, Engineering Leader, and specialists 
•  the real shift in what modern organisations need 
•  how Scrum Masters are evolving beyond facilitation into system enablement and organisational influence 
•  how product roles are moving beyond backlog management into strategy, discovery, and value shaping 
•  how engineering leaders are shifting from delivery oversight to enabling technical excellence and long-term value 
•  why specialist roles still matter, and how they are evolving from gatekeepers into embedded enablers 
•  what all of these roles now have in common 
•  where organisations still get it wrong, especially when structural and cultural problems are mistaken for role problems 
•  what the future of agile roles may look like as AI, hybrid work, and organisational complexity continue to grow 

This is not a framework debate or a defence of old job titles. It is a broader reflection on what healthy product and agile organisations actually need from the people working within them.

If you work in product, agile, engineering, delivery, transformation, or leadership, this episode offers a calm, practical, system-focused perspective on why agile roles are not dying, they are maturing.

Based on insights drawn from books by Matthew Coxall.

Support the show

Enjoyed the episode?
Don’t forget to subscribe to Agile Product Hub for more deep dives into Agile roles, real-world practices, and product thinking that delivers.

Explore the Harmony series for organisational guidance  or the full Agile How To book series for hands-on guidance tailored to Product Owners, Scrum Masters, Developers, and Agile Leaders.

Visit AgileProductHub.com to access resources, templates, and training designed to help you thrive.

The views and thoughts expressed in this podcast are those of the author. 
Podcast created on the notebookllm platform

🎧 #OrganisationalFrictionSeries | #AgileHowToSeries | #AgileProductHub

In many organisations, Product and Engineering are structured as separate functions. Product Managers and Product Owners focus on customer value and direction, while engineering teams focus on technical capability and delivery.

Yet the most effective digital organisations recognise that these disciplines must work hand in hand.

In this episode of The Deep Dive, we explore how the expectations placed on Product Managers and Product Owners have evolved as digital products become central to modern organisations. Drawing on insights from Matthew Coxall’s books on product leadership, agile delivery, and organisational design, the conversation looks at how product leaders interpret strategy, collaborate with engineering teams, work with specialist expertise, and operate within complex organisational systems.

Rather than focusing on tools or frameworks, this episode takes a reflective look at the system around product work. What does strong product leadership look like today? How do Product and Engineering collaborate effectively? And why does organisational design often shape product capability more than individual skill?

If you enjoy thoughtful conversations about digital product and agile, follow the series so you don’t miss future Deep Dive episodes.

 #AgileProductHub
 #DigitalProductManagement
 #ProductOwnership
 #AgileLeadership
 #ProductAndEngineering
 #AgileHowToSeries 

Support the show

Enjoyed the episode?
Don’t forget to subscribe to Agile Product Hub for more deep dives into Agile roles, real-world practices, and product thinking that delivers.

Explore the Harmony series for organisational guidance  or the full Agile How To book series for hands-on guidance tailored to Product Owners, Scrum Masters, Developers, and Agile Leaders.

Visit AgileProductHub.com to access resources, templates, and training designed to help you thrive.

The views and thoughts expressed in this podcast are those of the author. 
Podcast created on the notebookllm platform

🎧 #OrganisationalFrictionSeries | #AgileHowToSeries | #AgileProductHub

Many organisations introduce Agile teams, adopt Scrum or Kanban, and invest heavily in transformation programmes. Yet despite the new roles, ceremonies, and terminology, progress often feels slower than expected.

In this episode of The Deep Dive, we explore why Agile transformations still struggle to deliver the value they promise.

Drawing on insights from the books of Matthew Coxall, the conversation looks beyond team practices to examine the deeper organisational structures that shape how work really happens.

We discuss how many organisations adopt the vocabulary of Agile while still operating with project-era assumptions around funding, governance, and decision-making. These structural patterns create friction that no amount of stand-ups, retrospectives, or backlog refinement can resolve.

Topics explored in this episode include:

• The hidden impact of project logic in modern digital organisations
• Why funding models often reinforce delivery against scope rather than learning
• The reality of conditional autonomy inside Agile teams
• How governance layers create decision latency
• Why many Agile transformations stall despite genuine effort from teams

The episode concludes by introducing the concept of Product Agile Harmony, where Product, Engineering, Design, and Business operate as a connected system rather than separate functions.

Agile transformation is not simply a delivery change. It is a structural shift in how organisations learn, make decisions, and invest in digital products.

Podcast Format
 A reflective conversation exploring organisational design, leadership dynamics, and product thinking in modern digital organisations.

Source Material
 Insights drawn from books by Matthew Coxall including:

Product Agile Harmony (WIP)
 Agile How To Succeed as a Product Owner
 How to Navigate the Agile Journey as a Scrum Master
 How to Lead in Agile as an Engineering Leader

Support the show

Enjoyed the episode?
Don’t forget to subscribe to Agile Product Hub for more deep dives into Agile roles, real-world practices, and product thinking that delivers.

Explore the Harmony series for organisational guidance  or the full Agile How To book series for hands-on guidance tailored to Product Owners, Scrum Masters, Developers, and Agile Leaders.

Visit AgileProductHub.com to access resources, templates, and training designed to help you thrive.

The views and thoughts expressed in this podcast are those of the author. 
Podcast created on the notebookllm platform

🎧 #OrganisationalFrictionSeries | #AgileHowToSeries | #AgileProductHub

In this episode of The Deep Dive, we step beyond team mechanics and into a harder organisational question:

When a decision carries real weight, who actually owns it?

Agile promises empowerment, but empowerment without structural clarity is fragile.

As organisations scale, governance layers increase. Risk management expands. Alignment meetings multiply. Yet decision rights are rarely redrawn.

The result?

• Decision latency.
• Authority drift.
• Escalation disguised as alignment.
• Shadow ownership.

Based on insights from books by Matthew Coxall, this conversation explores how separating accountability from authority creates predictable friction.

When accountability sits in one place and authority in another, delay isn’t surprising. It is designed into the system.

This episode examines:

• Why autonomy often collapses under pressure
• How alignment theatre replaces ownership
• The structural cost of approval loops
• What mature organisations do differently

This is not a critique of leadership or governance. It is a diagnosis of structural design.

If you’ve ever felt that your teams are “empowered” until something important happens, this episode will resonate.

Where do decisions stall in your organisation?
 And who absorbs the delay?

Part of The Deep Dive – a series on digital product and agile.

Support the show

Enjoyed the episode?
Don’t forget to subscribe to Agile Product Hub for more deep dives into Agile roles, real-world practices, and product thinking that delivers.

Explore the Harmony series for organisational guidance  or the full Agile How To book series for hands-on guidance tailored to Product Owners, Scrum Masters, Developers, and Agile Leaders.

Visit AgileProductHub.com to access resources, templates, and training designed to help you thrive.

The views and thoughts expressed in this podcast are those of the author. 
Podcast created on the notebookllm platform

🎧 #OrganisationalFrictionSeries | #AgileHowToSeries | #AgileProductHub

It’s common to hear that teams are performing well, delivery is steady, and ceremonies are running smoothly.
 And yet, progress feels slower than it should. Decisions drag. Learning stalls. Tension shows up elsewhere in the system.

In this episode, I explore the idea of the healthy team illusion — the moment when teams appear fine on the surface, but organisational constraints quietly limit their effectiveness.

Through the lens of the evolving Scrum Master role, we look at:

• Why mature teams often surface problems they can’t solve themselves
• How accountability and authority drift apart across roles
• Why coordination increases as systems struggle, even when teams are capable
• What Scrum Masters, Product Owners, and specialists tend to notice first, long before metrics change

This isn’t a critique of teams, or of individuals doing the work.
 It’s an exploration of what happens when systems don’t evolve at the same pace as the people within them.

If you’ve ever felt that something isn’t quite right, even when everything looks “healthy”, this episode is for you.

If you’d like to explore further
 You’ll find related podcasts, articles, and books at agileproducthub.com

Support the show

Enjoyed the episode?
Don’t forget to subscribe to Agile Product Hub for more deep dives into Agile roles, real-world practices, and product thinking that delivers.

Explore the Harmony series for organisational guidance  or the full Agile How To book series for hands-on guidance tailored to Product Owners, Scrum Masters, Developers, and Agile Leaders.

Visit AgileProductHub.com to access resources, templates, and training designed to help you thrive.

The views and thoughts expressed in this podcast are those of the author. 
Podcast created on the notebookllm platform

🎧 #OrganisationalFrictionSeries | #AgileHowToSeries | #AgileProductHub

As Agile teams mature, the role of the Scrum Master is too often seen as expendable. But what if that perception misses the deeper evolution of the craft?

In this episode, Matt reflects on the Scrum Master’s journey from ritual facilitator to system steward. Drawing from How to Navigate the Agile Journey as a Scrum Master (Chapters 2, 4, 6, and 8), he explores how real impact often lies not in what’s visible, but in what’s sensed, shaped, and sustained across the system.

Expect a mix of insight and reflection on:

• How mature teams still benefit from strategic system support
• The difference between surface-level agility and true sustainable pace
• Coaching the organisation, not just the team
• The quiet leadership that holds space for trust, clarity, and coherence

This episode is for Scrum Masters ready to evolve, and leaders who think they’ve outgrown the role. The lighthouse still matters — especially when the waters look deceptively calm.

Support the show

Enjoyed the episode?
Don’t forget to subscribe to Agile Product Hub for more deep dives into Agile roles, real-world practices, and product thinking that delivers.

Explore the Harmony series for organisational guidance  or the full Agile How To book series for hands-on guidance tailored to Product Owners, Scrum Masters, Developers, and Agile Leaders.

Visit AgileProductHub.com to access resources, templates, and training designed to help you thrive.

The views and thoughts expressed in this podcast are those of the author. 
Podcast created on the notebookllm platform

🎧 #OrganisationalFrictionSeries | #AgileHowToSeries | #AgileProductHub

In this episode of Agile Product Hub: Deep Dives, we explore one of the most misunderstood (and often skipped) parts of product development: discovery.

Too many teams rush to delivery with half-baked ideas and unclear outcomes. We’re flipping that script.

I break down:

• What real Agile discovery looks like in practice
• The dangers of solution-first thinking
• How discovery drives value, alignment, and customer outcomes
• Practical tips to embed discovery into your sprint rhythm

Whether you’re a Product Owner, Product Manager, Scrum Master, or engineering leader—this episode will sharpen your thinking and challenge your defaults.

If you’ve ever asked:
 “Are we building the right thing, or just building it right?”
…this episode is for you.

 #AgileHowToSeries #AgileProductHub #DeveloperGrowth #ScrumMastery

Support the show

Enjoyed the episode?
Don’t forget to subscribe to Agile Product Hub for more deep dives into Agile roles, real-world practices, and product thinking that delivers.

Explore the Harmony series for organisational guidance  or the full Agile How To book series for hands-on guidance tailored to Product Owners, Scrum Masters, Developers, and Agile Leaders.

Visit AgileProductHub.com to access resources, templates, and training designed to help you thrive.

The views and thoughts expressed in this podcast are those of the author. 
Podcast created on the notebookllm platform

🎧 #OrganisationalFrictionSeries | #AgileHowToSeries | #AgileProductHub

In Part 2 of this special Agile Product Hub mini-series, we continue the deep dive into what it means to thrive—not just survive—as a developer, tester, or technical contributor in Agile environments.

Building on the foundation from Part 1, this episode takes it further, focusing on:

•  Overcoming blockers and making your voice heard
•  How to contribute to continuous improvement without being “the complainer”
•  Navigating refinement, retrospectives, and technical excellence
•  Becoming a trusted, high-impact member of your Scrum or Kanban team

Whether you’re working in a sprint, flowing with Kanban, or somewhere in between—this episode offers practical tools and reflective prompts to help you grow.

🎧 Based on the book: Agile How To Thrive as a Development Team Member in Scrum and Kanban

 🎙️ Missed Part 1? Start there first! - Thriving as a Dev in Agile: The Real Talk (Part 1 – Foundations & Flow)

#AgileHowToSeries #AgileProductHub #DeveloperGrowth #ScrumMastery

Support the show

Enjoyed the episode?
Don’t forget to subscribe to Agile Product Hub for more deep dives into Agile roles, real-world practices, and product thinking that delivers.

Explore the Harmony series for organisational guidance  or the full Agile How To book series for hands-on guidance tailored to Product Owners, Scrum Masters, Developers, and Agile Leaders.

Visit AgileProductHub.com to access resources, templates, and training designed to help you thrive.

The views and thoughts expressed in this podcast are those of the author. 
Podcast created on the notebookllm platform

🎧 #OrganisationalFrictionSeries | #AgileHowToSeries | #AgileProductHub

In this energising two-part special, we kick off a ground-level look at what it really means to thrive as a developer, tester, or technical team member in Scrum and Kanban environments. Based on Matthew Coxall’s practical guide How To Thrive as a Development Team Member, Part 1 dives into the foundational mindsets, team dynamics, and delivery flow strategies that turn average teams into high-impact ones.

We explore:

• What “thriving” actually means for devs and testers in Agile
•  Key mindset shifts that unlock collaboration and autonomy
•  Making sense of flow, WIP, and self-organisation in real teams
•  How to stop surviving sprints—and start shaping them

If you're a developer, tester, or even a Scrum Master trying to support your team better—this one’s built for you.

🎧 Based on the book: Agile How To Thrive as a Development Team Member in Scrum and Kanban

 🎙️ Part 2 coming soon: Navigating blockers, continuous improvement, and technical excellence.

 #AgileHowToSeries #AgileProductHub #ScrumTeamSuccess

Support the show

Enjoyed the episode?
Don’t forget to subscribe to Agile Product Hub for more deep dives into Agile roles, real-world practices, and product thinking that delivers.

Explore the Harmony series for organisational guidance  or the full Agile How To book series for hands-on guidance tailored to Product Owners, Scrum Masters, Developers, and Agile Leaders.

Visit AgileProductHub.com to access resources, templates, and training designed to help you thrive.

The views and thoughts expressed in this podcast are those of the author. 
Podcast created on the notebookllm platform

🎧 #OrganisationalFrictionSeries | #AgileHowToSeries | #AgileProductHub

Episode 2: Guiding the Agile Journey – The Scrum Master’s Real Role
In this episode of Agile Product Hub, the NotebookLM Deep Dive hosts turn their focus to Agile How To: Navigate the Agile Journey as a Scrum Master. This isn't just a look at servant leadership—it's a deep conversation about what it really means to guide, challenge, and support teams in today’s complex product environments.

From Chapter 5 onwards, we explore:

•  The evolving responsibilities of modern Scrum Masters
•  How to coach teams beyond ceremony and compliance
•  Navigating resistance, enabling self-organisation, and creating space for growth
•  The shift from doing Agile to being Agile—and helping others get there too

If you’ve ever wondered how Scrum Masters can drive real change without controlling the team, this episode brings insight, challenge, and inspiration.

📘 The book the hosts are discussing: https://amzn.eu/d/46CmnCh
🎧 #AgileHowToSeries #AgileProductHub

Support the show

Enjoyed the episode?
Don’t forget to subscribe to Agile Product Hub for more deep dives into Agile roles, real-world practices, and product thinking that delivers.

Explore the Harmony series for organisational guidance  or the full Agile How To book series for hands-on guidance tailored to Product Owners, Scrum Masters, Developers, and Agile Leaders.

Visit AgileProductHub.com to access resources, templates, and training designed to help you thrive.

The views and thoughts expressed in this podcast are those of the author. 
Podcast created on the notebookllm platform

🎧 #OrganisationalFrictionSeries | #AgileHowToSeries | #AgileProductHub

Episode 1: The Agile Product Hub Origin – Diving Into the 'Agile How To' Series
Join the NotebookLM Deep Dive hosts as they explore the core themes and key takeaways from Agile How To: Succeed as a Product Owner. In this premiere episode, we go beyond the basics—starting from Chapter 5 onwards—to unpack what it really means to manage backlogs, deliver value, and lead with purpose. From practical backlog techniques and prioritisation strategies to real-world stories about stakeholder alignment and discovery practices, this conversation sets the tone for a podcast series dedicated to making Agile work in the real world.

If you're ready to move from theory to thoughtful action, this is your starting line.
 #AgileHowToSeries #AgileProductHub

The book the hosts are discussing - https://amzn.eu/d/0narTQW 

Support the show

Enjoyed the episode?
Don’t forget to subscribe to Agile Product Hub for more deep dives into Agile roles, real-world practices, and product thinking that delivers.

Explore the Harmony series for organisational guidance  or the full Agile How To book series for hands-on guidance tailored to Product Owners, Scrum Masters, Developers, and Agile Leaders.

Visit AgileProductHub.com to access resources, templates, and training designed to help you thrive.

The views and thoughts expressed in this podcast are those of the author. 
Podcast created on the notebookllm platform

🎧 #OrganisationalFrictionSeries | #AgileHowToSeries | #AgileProductHub