Silos are the bane of value delivery

Many organizations adopt Scrum (or claim to) but then organize their teams in ways that completely undermine what makes Scrum powerful. They create technology or functional silos—dedicated teams for backend, frontend, QA, design, etc.—and then wonder why value trickles out so slowly.

The truth is simple: cross-functional teams are essential if you actually want to deliver value sooner. When a team has all (or most) of the skills needed to take an item from idea to done, they can move fast, collaborate effectively, and own the outcome. Silos create handoffs, dependencies, and coordination overhead that kill momentum.

One of the most common (and misguided) reasons organizations stay stuck in silos is the belief that a single Product Owner can’t effectively support more than one Scrum team. So they assign one PO per team, even if that means fragmenting the work across multiple specialized teams. This feels safer on paper, but in practice it creates far more work and frustration for everyone involved.

The Real Cost of Siloed Teams & Multiple Product Owners

Imagine you have a valuable feature or initiative that needs work from several areas. With siloed teams, your Product Owner doesn’t actually control the full delivery. They have to:

• Prioritize the work on their backlog.

• Then go beg, plead, or negotiate with other Product Owners to get that same work prioritized on their backlogs.

• Chase coordination across teams, deal with conflicting priorities, and wait for handoffs.

This is annoyingly difficult and slow. Instead of focusing on maximizing value and making smart trade-offs, the PO spends time in endless alignment meetings and political navigation. Value delivery grinds to a halt while dependencies pile up.

The irony? Organizations do this thinking it protects the Product Owner from overload. In reality, it adds massive overhead. A single empowered Product Owner who can set clear priorities across related work is far more effective.

A Better Way

A strong Product Owner can successfully work with multiple Scrum teams—especially when those teams are truly cross-functional and aligned around a shared product or value stream. Here’s why this works better:

• Clear prioritization authority: One PO sets the direction. No more negotiating with other POs to get your item moved up someone else’s backlog.

• Delegation done right: The PO doesn’t have to document every single Product Backlog Item themselves. They can leverage team members with business analysis experience, domain knowledge, or strong writing skills to help refine and document items. This keeps the PO focused on vision, stakeholder alignment, ordering for maximum value, and validation.

• Faster flow: Cross-functional teams reduce (or eliminate) external dependencies. Work flows through one team (or a tightly aligned set of teams) instead of bouncing between silos.

• Better accountability and learning: Teams see the full picture, build deeper product knowledge, and take pride in end-to-end delivery.

This approach scales value delivery without pretending every PO needs their own isolated fiefdom. It requires trust in the PO’s prioritization skills and investment in building genuinely cross-functional teams—but the payoff in speed and reduced frustration is enormous.

Moving Beyond Silos

If your organization is still organizing around technology layers or narrow functions, take a step back. Ask the hard questions:

• What are our actual products or value streams?

• Do our teams have the skills they need to deliver increments of those products end-to-end?

• Are we burdening Product Owners with coordination theater instead of empowering them to drive value?

True Agile transformation means aligning structure around value delivery, not protecting old habits. Cross-functional teams with empowered Product Owners (who can support multiple teams when needed) cut through the noise and get real results.

Organizations that embrace this see faster delivery, happier teams, and customers who actually notice the difference. Those who cling to silos stay stuck in slow, painful coordination hell—no matter how many meetings, coordination events, or administrative layers that they add.