In Nexus with 5 Scrum teams, how can the Product Owner attend all Sprint Planning events?


As part of the webinar “Ask a Professional Scrum Trainer – Martin Hinshelwood – Answering Your Most Pressing Scrum Questions” I was asked a number of questions. Since not only was I on the spot and live, I thought that I should answer each question that was asked again here, as well as those questions I did not get to.

In case you missed it, here is the recording of yesterday’s Ask a Professional Scrum Trainer webinar with Martin Hinshelwood! Watch here:

[Question] In Nexus with 5 Scrum teams, how can the Product Owner attend all Sprint Planning events?

As you increase the number of Teams in a Nexus you can very quickly run into this common scaling issue. While Nexus talks about a single Product Owner who has overall accountability and ownership of the Product Backlog, you may need to scale the Product Owner role as your Nexus grows. My usual starting point here is to look at how the Product Backlog is decomposed. It may be that my Product Owner only provides detailed leadership down to the Feature level and not to the Product Backlog Level. This leaves the Scrum Team with ownership there, and releases pressure on the Product Owner. The Product Owner would then only require to attend the Nexus Sprint Planning portion, and would delegate the rest. As long as the Product Owner effectively communicates their vision & expectations as part of the Nexus Sprint Goals, the Scrum Teams should be able to work towards fulfilling them.

Product Backlog Items can be delivered in a singe Sprint with a preference for smaller.

Features are too big for a single team Sprint and may be delivered across multiple Sprints or Teams

Epics are too big for a Release and would be composed of many Features.

-Martin Hinshelwood

Each Scrum Team would then be free to choose how they manage this and make sure that they have enough ready Backlog Items for their part of Sprint Planning. Usually they will designate, or have, a virtual Product Owner that is dedicated to their team. This virtual PO role could be called a “Area Owner” if their Scrum Team is focused on only one area of the Product, or a “Team Owner” if there are many teams in the same area. This is roughly how the Azure DevOps engineering teams break down:

-Product Owner

|—-Work Item Product Owner

        |— Team A Product Owner

        |—Team B Product Owner

|—-Source Control Product Owner


In this case they have ~42 teams that roll up to ~6 Product Areas, and is just one example of how you might structure things. The danger is in disrupting the flow of information by increasing the distance between the Product Owner and the Development Team. The Azure DevOps engineering teams mitigate this with Autonomy. Each Area Owner is only looking at their functional area while fulfilling the vision set by the Product Owner, and the Team Owner is communicating constantly with their peers and the Area Owner.

If you do implement some kind of hierarchy I recommend focusing on keeping it as flat as posible and understanding that each of these folks, Product Owner, Area Owner, & Team Owner are fulfilling the role of the Product Owner as per the Scrum Guide as part of a Scrum Team. For the question above I would likely start with a dedicated Team Owner for each team that is the representative that attends the Nexus Sprint Planning and that works closely with the Product Owner. This will likely need close monitoring and a skilled Scrum Master to help coach the teams to maintain communication and not loose focus.

While there are no right answers there are some answers that are better than others. For your given situation select the most right answer, and iteration to the best version of it.

Upcoming Training Opportunities

These are the next five classes we have, and you can check out our full public schedule of classes.

Live virtual Professional Scrum with UX online on 5th December over four half-days
Virtual Advanced 5
5 - 8 Dec, 2022
09:30-13:00 GMT
Live Virtual Applying Professional Scrum Minecraft on  12th December 2022
Virtual Beginner 12
12 - 15 Dec, 2022
14:00-17:30 GMT

We can deliver any of our courses as private in-house training over Microsoft Teams & Mural. We also recommend training based on your accountabilities or role, you can go directly to recommended courses for Scrum MastersProduct OwnersDevelopers and Agile Leaders.

Create a conversation around this article

Share on Facebook
Share on Twitter
Share on Linkdin

Related Courses

No items found

Read more

Martin Hinshelwood (He/Him)
To my understanding there is a frustrating misunderstanding of reality when one thinks that the Product Owner can reject a single story at the Sprint Review. This is the fallacy of the rejected backlog item.
Martin Hinshelwood (He/Him)
There is no such thing as an Agile Transformation, Digital Transformation, DevOps Transformation, or any of the Whatever Transformation that you can think of or have been sold. You can’t buy agility, and you certainly can’t install it. There is no end state, no optimal outcome, No best practices. We …
Martin Hinshelwood (He/Him)
In light of the new normal and the last 20 years of technological progress, we need to re-define co-location as we no longer need to be in the same room as each other to get the 80% of communication that is non-verbal. If we are participating in an online event, …
Martin Hinshelwood (He/Him)
Gathering the metrics for Evidence-based Management in software organisations can be a strenuous task and I have a number of customers that are fretting on what to collect and from where. Here I try to create an understanding of the ‘what’ that we need to collect.


We believe that every company deserves high quality software delivered on a regular cadence that meets its customers needs. Our goal is to help you reduce your cycle time, improve your time to market, and minimise any organisational friction in achieving your goals.

naked Agility Limited is a professional company that offers training, coaching, mentoring, and facilitation to help people and teams evolve, integrate, and continuously improve.

We recognise the positive impact that a happy AND motivated workforce, that has purpose, has on client experience. We help change mindsets towards a people-first culture where everyone encourages others to learn and grow. The resulting divergent thinking leads to many different ideas and opportunities for the success of the organisation.