Back to Forum

Need new backlog for those PBIs being not ready due to external vendors?

Last post 07:30 pm August 17, 2017 by LK L
2 replies
LK L
05:22 am August 17, 2017

In typical projects, the vendors often have delays in delivering their components, should SM suggest PO to move those impacted PBIs into another new backlog for future sprints?

With reference to Ian's blog as below, my view tends to have PBIs re-ordering accordingly, but I'm NOT sure about the guidelines on whether a new backlog is required. Suppose PBL should be created for only a product. Any advice?

https://sites.google.com/site/wicmitchell/home/ordering-a-product-backlog-to-minimize-development-team-dependencies

 

Ian Mitchell
06:49 pm August 17, 2017

Each clear Product must have a clear Product Owner and exactly one Product Backlog.

Are you suggesting that certain work on a Product, which must be deferred to future Sprints for whatever reason, might be in some sense deserving of a separate Product Backlog? If so, why? 

LK L
07:30 pm August 17, 2017

Got it, that means my understanding "PBL should be created for only a product" (and thus no need of new backlog) is correct. With regards to the PBL re-ordering under the captioned scenario, the impacted PBIs may or may not require re-ordering subject to whether the dependences could be minimized or avoided, is this understanding correct?

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.