PO overwhelmed by the number of scrum teams
So here's the scenario. The PO is currently working on a finance system that caters to different countries (8 for now.) Each country has their own specifications/ configurations but at the end of the day, those 8 countries are working on a single increment. I still say that he doesn't need additional POs as that might bring more problems in the future. What do you think we should do to help him? We have BAs for each team but these BAs are also asking him for the features and other clarifications. Currently there are 4 scrum teams and 2 scrum masters for these teams. Imagine all those 4 scrum teams doing the sprint events in a single day...
p.s: We are using SAFe. I would love for us to use Nexus instead but i don't think i could make that call right now.
Agile practice is based on empiricism and validated learning. How does the Product Owner currently inspect product performance and adapt the Product Backlog? What constraint is there on his ability to do this effectively?
Currently, he joins the sprint review of all the 4 teams. There's minimal change in the backlog as we have a "PI commit" (SAFe). The product is still not in production because the business keeps on expanding their MVP. All in all we are still waterfallish in terms of implementation.
Most of the challenges he encounters is when he spends time with the BAs in discussing the user stories. He's also the one responsible ordering the items in the backlog. These are just some of the tasks that he is handling
How else can the Dev Team (assuming the BAs are members of the Dev Team, right?) get access to the details of the PBI?
I still say that he doesn't need additional POs as that might bring more problems in the future.
What kinds of problems would at least one additional PO bring?
Inversely, what benefits would at least one additional PO bring?
In my opinion, 1 PO and BAs that are heavily relying on that 1 PO, and feeding 4 scrum teams is too stretched (for that PO).
Imagine the time of discussing with the BAs, with each scrum team and joining scrum ceremonies.
I would recommend additional PO (Yes, it will take time to train but in the long run, it will help the PO and the teams).
Question: What happens when that 1 PO is on leave (e.g. more than a month)? What happens to your committed items if BAs are relying heavily on the PO?
@Oliver:
How else can the Dev Team (assuming the BAs are members of the Dev Team, right?) get access to the details of the PBI?
They usually go directly with the PO and./or go directly to the SMEs. But still, he needs to oversee all of the user stories
@John
What kinds of problems would at least one additional PO bring?
As stated above :)
Inversely, what benefits would at least one additional PO bring?
I would say it would bring more confusion. There's only one product/increment/build for all those countries and I don't see how more than one PO would help. But of course I am listening to your suggestions :)
@Sherwin
Imagine the time of discussing with the BAs, with each scrum team and joining scrum ceremonies.
Exactly! He often gets sick actually... Thankfully he is dedicated to our "cause".
Question: What happens when that 1 PO is on leave (e.g. more than a month)? What happens to your committed items if BAs are relying heavily on the PO?
I believe the BAs would go directly to the project sponsor(s). And probably one of those sponsors will act as a PO temporarily.
I would recommend additional PO (Yes, it will take time to train but in the long run, it will help the PO and the teams).
I am thinking that maybe assign one of our BAs to be an "assistant" PO.