Scrum Master Toolbox Podcast: Product Owner Patterns – From Absent to Exceptional with Salum Abdul-Rahman

Date: August 29, 2025
Host: Vasco Duarte
Guest: Salum Abdul-Rahman
Episode Focus: A deep dive into product owner (PO) patterns—examining the detrimental effects of absent POs and the transformative qualities of exceptional ones, grounded in real-world Agile team experiences, especially in the public sector.

Episode Overview

This episode explores the spectrum of product owner behaviors and their impact on Agile teams. Salum Abdul-Rahman, an experienced Agile coach, shares stories highlighting a frequent anti-pattern of the "absentee PO" and contrasts it with the qualities of exemplary product owners he’s encountered. Together with host Vasco Duarte, they dig into organizational obstacles, cultural baggage, and actionable strategies for supporting product owners—especially in high-stakes public sector environments.

Key Discussion Points & Insights

1. Product Owner Anti-Pattern: The Absentee PO

• Definition:
  The most common anti-pattern in the public sector is the absentee product owner. These are specialists who are already fully engaged in another role and only allocate 10-20% of their time to PO duties.
• Consequences:
  • POs lack the bandwidth to be effective.
  • No time or support to develop necessary skills.
  • Projects suffer from lack of decision-making and prioritization.
• Salum’s Approach:
  • Salum would "book time in their calendar" and walk them through basics like backlog refinement and user stories:

    "It was very, very, very kindergarten style learning of 'we'll do this backlog refinement thing together. And this is how you use JIRA and this is what a user story is.'"
    (Salum Abdul-Rahman, 03:35)

  • These POs often saw their job as simply transmitting requirements, not actively making decisions.

    "It was not just passing requirements from stakeholders, but actually making decisions. And making decisions is hard."
    (Salum Abdul-Rahman, 05:12)

• Cultural Challenge:
  • Decision-making is discouraged in traditional hierarchies.
  • Many organizations create layers of committees, slowing down necessary PO action.

    "You need a committee to talk about the multiple possible outcomes and then another committee to make the final decision and then another committee to validate that the previous committee made the right decision."
    (Vasco Duarte, 05:50)

2. Role of Scrum Master and Agile Coach

• It often falls to Scrum Masters and Agile Coaches to provide the necessary guidance and hand-holding:

  "It's very important to recognize the importance of roles like Scrum Master and Agile Coach, because you do need to do this hand holding if you want to bring that product owner into the software development process."
  (Vasco Duarte, 06:59)

3. What Makes an Exceptional Product Owner

• Salum’s Best PO Story:
  • Salum worked with a PO who had a PhD in data science and was extremely systematic, particularly in working with stakeholders on a data visualization tool for the public sector.
  • Key qualities:
    • Decisive from the outset (no hand-holding required).
    • Highly analytical, always focused on meaningful metrics—even in environments (like the public sector) where monetary feedback doesn’t exist.
    • Bridged the abstract (“changing the world”) with the concrete (stakeholder communication, value metrics).
    • Engaged cross-sector stakeholders, facilitating communication between private and public entities.
    • Could translate high-level value into actionable guidance for teams.
  • Notable Reflection:

    “You have to talk about how we're actually changing the world. Like, what is the value we bring to society, what is the value we bring to our users to make it meaningful for the team?”
    (Salum Abdul-Rahman, 11:04)

• Challenge in Value Communication:
  • Many POs default to reporting metrics, but it’s critical to connect those numbers to real value and context for the team.
  • Host Perspective:

    “If we don't have this clear vision of what the value is, we're going to make many of those decisions wrong, not because of lack of competence, but rather because lack of understanding of what is the value and who are the stakeholders that we are serving.”
    (Vasco Duarte, 13:37)

4. Abstraction, Decision-Making, and Impact

• Multi-Layered Complexity:
  • Decisions made at each abstraction layer (dev, design, ops, business) can have enormous, systemic impacts.

    "The decisions made on different abstraction layers can have like large systemic effects on the other layers and eventually to business and value and project and even people's health and well-being."
    (Salum Abdul-Rahman, 14:08)

• Developer Needs:
  • Developers, designers, DevOps engineers depend on PO clarity to make sound, value-aligned decisions.

Notable Quotes & Memorable Moments

• On Systemic Change (03:00):
  “This is something that has changed on a systemic level, that people understand the role of a product owner a bit better... but I remember working with a product owner that had time for meetings with stakeholders, had time for meetings with the team and nothing else related to the project.”
  (Salum Abdul-Rahman)

• On Decision-Making in Hierarchical Culture (05:12):
  “A lot of organizational culture discourages us from making decisions and helping people to understand that your role is to actually make decisions is really difficult because I think it's disincentivized in traditional hierarchical management.”
  (Salum Abdul-Rahman)

• On the Public Sector and Value (11:04):
  “You have to talk about how we're actually changing the world... what is the value we bring to our users to make it meaningful for the team?”
  (Salum Abdul-Rahman)

• Value Engineering Reference (13:11):
  “[Tom Gilp] talks about the incredible necessity of understanding, defining and even quantifying value, but not only to one stakeholders, to all of the stakeholders... the ability to bring all of these different perspectives into a coherent message that does not feel too abstract for the team is incredibly important because as developers, we're making decisions that affect the value delivered every single day, many times an hour.”
  (Vasco Duarte)

Timestamps for Key Segments

| Segment | Timestamp | |------------------------------------------------------------- |------------| | Intro & Anti-Pattern Setup | 01:11 | | Absentee PO Explored (Practical Experiences) | 01:48–05:50| | Organizational & Cultural Obstacles to PO Effectiveness | 05:50–06:59| | Role of Scrum Masters and Agile Coaches | 06:59–08:07| | Transition to “Best Product Owner” Experiences | 08:07–09:14| | Story: The Exceptional Data Scientist PO | 09:14–12:41| | Value Communication and Stakeholder Engineering | 12:41–14:08| | Multi-layered Abstraction, Developer Decision-Making | 14:08–14:43| | Closing Remarks and How to Connect with Salum | 15:19–15:45|

Episode Takeaways

• A true product owner must be full-time, empowered, and supported—not splitting attention or acting only as a requirements relay.
• Decision-making is core; organizational cultures must encourage, not stifle, PO agency.
• Great POs bring a blend of strategic vision and practical communication—they quantify and contextualize value, especially critical in non-monetary environments.
• Team empowerment hinges on clarity: Developers and all Agile team members rely on a PO who can translate vision into concrete, actionable guidance across abstraction layers.
• Supporting new, underprepared POs is a key Scrum Master/Agile Coach responsibility.

Learn More & Connect

• Find Salum Abdul-Rahman on LinkedIn:
  “If you want to send a connection request, please mention that you found me on this podcast. I don't accept anonymous connection requests, but you can always follow and I post links to whatever thoughts I'm sharing to mostly the public.”
  (Salum Abdul-Rahman, 15:19)

This episode is essential listening for Agile practitioners aiming to understand and cultivate effective Product Owner behaviors, especially amid the complex dynamics of the public sector and large organizations.