Any BU stakeholders should be able to place items in the product backlog at any time.
They could then be involved during backlog grooming, where a discussion can take place regarding prioritization. They can also answer questions from the team as they estimate and split the PBIs. This backlog grooming doesn't have to be a single meeting per sprint, but can occur any time. So you could choose to have one backlog grooming session per BU if you wanted. This would mean the PO would have to make decisions when to prioritize one BU over the other. If BUs might fight over priority, then I suggest having them all in backlog grooming together, so they can reach consensus, perhaps by making deals about whose PBIs get prioritized. The Scrum Guide suggests backlog grooming can take around 10% of sprint time, as a rough guideline.
Planning is a separate meeting that occurs later without the stakeholders, where the number of prioritized PBIs to commit to is selected, and can be broken into SBIs.
On Mon, Jul 11, 2011 at 6:54 PM, kevinkrac <kkrac78@...>
The challenge here is how to handle the product backlog for the
various business units and what approach to take for the different
Should we have one single planning meeting with all BUs stakeholders,
and there prioritize the backlog for each and choose the stories to
work on during the sprint? One planning meeting per BU?