PO or PM? Who decides what truly matters in a Sprint?

Zakaria Botros
Thanks for sharing that perspective
It brings a balanced view of collaboration between PO and PM.

I’d be curious to hear more:
- In your experience, when that alignment breaks down, what helps restore it?
- Have you seen leadership actively support those trade-offs or does one role usually carry the burden?

Any example you’ve seen that worked (or didn’t)?
These real-world stories are key to understanding how teams actually navigate the tension between value now vs value later.

Excellent question, Luis. I’ve seen this tension play out often, the PO focuses on maximizing immediate product value, while the PM looks at sustainability and alignment with the broader strategy. Ideally, it shouldn’t be about who decides, but how they decide together. A joint prioritization framework, such as balancing business value with strategic risk or technical debt, keeps both views aligned. Strategic agility, after all, is about short-term value that doesn’t compromise long-term direction.

As said previously, the PO and PM should align around a shared vision — with the Product Owner focusing on short-term value, business objectives and market responsiveness, and the Project Manager ensuring development coherence and sustainability of the overall effort. Ideally, they collaborate effectively to balance these perspectives.

However, when this alignment does not happen in practice, it should become a priority for the organization or the PM-PO team to hold a retrospective — to identify what is working, what is not, and how collaboration can be improved.
This reflection is not just about process: it directly impacts the team’s productivity and the business value of the solution being built.

David Portas
Thank you for this thoughtful reflection
You raise a crucial point about the evolving boundaries between product and project management.

I fully agree that, in a mature agile ecosystem, Product Ownership naturally embraces both short-term responsiveness and long-term stewardship of value.
However, in many organizations (especially those operating across multiple portfolios or regulated environments) project-based governance remains essential to secure funding, align stakeholders, and orchestrate complex interdependencies.

In such contexts, the Project Manager is not an extra layer but a strategic bridge: connecting the flow of delivery with the cadence of governance and the rhythm of long-term strategy.
When product agility meets ethical, adaptive project discipline, organizations achieve something rare - strategic coherence that regenerates rather than constrains.

Lissette Indhira Pimentel Sosa
Thank you.
That’s a beautifully balanced insight.
I completely agree: the real question is not who decides, but how the decision system itself is designed.

Joint prioritization frameworks are powerful when they integrate not only value and risk, but also ethical intent and systemic awareness, ensuring that what we accelerate today does not silently erode tomorrow’s capacity to deliver value.

In my experience, when PO and PM co-create decisions within a transparent, principle-based framework, strategic agility becomes more than speed, it becomes sustainable coherence in motion.

Ovidiu Crisan
That’s an excellent point, and a very grounded one.
You’re absolutely right that, in practice, project managers often face unplanned shifts driven by regulatory change, client urgency, or market volatility.

However, what truly distinguishes strategic agility from reactive adaptation is the quality of the decision process behind those shifts.
When urgency is handled through a transparent framework (where intent, impact, and alignment are consciously examined) even a “firefighting” action can reinforce, not erode, strategic coherence.

In that sense, agility is not the absence of surprise; it’s the capacity to integrate disruption without losing direction.
And that’s where both PO and PM become essential, not just executing change, but shaping how the organization learns from it.