Need new backlog for those PBIs being not ready due to external vendors?
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
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?
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?