Skip to main content

Product Backlog

Last post 11:21 pm April 7, 2016 by Jemer Garibay
4 replies
06:26 pm April 6, 2016

When Scrum Teams share the same backlog, should each team takes an equal # of items? Or rather based on velocity or decided by the Product Owner?


09:44 am April 7, 2016

Peter,

More than one team can serve a single product owner and product backlog. The teams can coordinate with the product owner and with each other to determine what makes sense for each team to accept each sprint, based on their comfort level, capacity, and ability. However, this suggestion is not mandatory.

The Product Owner may decide what to "offer" each team, but in no way does a Product Owner decide what a team will work on.

In the future, it is best to pose these types of questions in the other forum, and leave this forum for certification and assessment questions.


12:37 pm April 7, 2016

Each team pulling from the backlog can follow standard Scrum here. The Dev Team selects items that they think they can finish in a Sprint. The Dev Teams decide which and how much.


10:23 pm April 7, 2016

> When Scrum Teams share the same backlog,
> should each team takes an equal # of items?
> Or rather based on velocity or decided by the Product Owner?

What do you think self-organizing teams should do?

What does the Nexus Guide have to say about how Sprint Planning is conducted with multiple teams?


11:21 pm April 7, 2016

Each team can decide how many items it can take to achieve it's own sprint goals.

I don't think PO should decide how many should be taken by each team, but PO has the say on what priorities needed and can influence them on the number of items it wished to be added on the sprint.

Team velocities only show's the potential number of items that the team historically can achieve, but it doesn't warrant the number of items each team should take on every sprint.


By posting on our forums you are agreeing to our Terms of Use.

Please note that the first and last name from your Scrum.org member profile will be displayed next to any topic or comment you post on the forums. For privacy concerns, we cannot allow you to post email addresses. All user-submitted content on our Forums may be subject to deletion if it is found to be in violation of our Terms of Use. Scrum.org does not endorse user-submitted content or the content of links to any third-party websites.

Terms of Use

Scrum.org may, at its discretion, remove any post that it deems unsuitable for these forums. Unsuitable post content includes, but is not limited to, Scrum.org Professional-level assessment questions and answers, profanity, insults, racism or sexually explicit content. Using our forum as a platform for the marketing and solicitation of products or services is also prohibited. Forum members who post content deemed unsuitable by Scrum.org may have their access revoked at any time, without warning. Scrum.org may, but is not obliged to, monitor submissions.