Back to Forum

Grooming Horizon and large scrums

Last post 01:55 pm November 8, 2019 by Ian Mitchell

3 replies

Kaushik Subbaratnam

11:49 am November 7, 2019

Hi,

I would like to get some expert opinion on how are large scrum managed and Grooming horizon done?

Regards

Kaushik Subbaratnam

Ben Brumm

10:09 pm November 7, 2019

What do you mean by "large scrum managed"? Are you referring to using Scrum in large teams or multiple teams?

What do you mean by "grooming horizon"?

Kaushik Subbaratnam

01:16 pm November 8, 2019

Hi Ben,

While working with multiple teams (which are also large ~ 9) how can a PO effectively manage and groom the requirements (stories/epic etc.) in an effective way?

Example - How to avoid many touch points to make an effective time boxed product backlog to enable sprints to be effective with multiple teams

Regards

Kaushik Subbaratnam

Ian Mitchell

01:55 pm November 8, 2019

Shouldn't it also be the responsibility of Development Teams, or their representatives, to identify and minimize dependencies during Product Backlog refinement?

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.