Skip to main content

PI Planning schema for unpredictable backlogs

Last post 06:45 pm November 19, 2024 by Daniel Wilhite
3 replies
08:15 am November 18, 2024

Team is working on Program1, Program2 and Program 3. Program1 & 2 having predefined content and Program 3 is not having any predefined content(backlog may come at any time). In this scenario how to define PI planning schema.


06:34 pm November 18, 2024

It sounds as though Programs 1 and 2 have no emergent work and hence no need for agility to be demonstrated. If there really is any complexity behind them, the precocious definition of work will put the success of those initiatives at risk.

Program 3 involves emergent work and hence planning ought to be undertaken each Sprint. The Product Owner should be able to communicate a Product Goal, and enough work should be refined and ready to allow Sprint Planning to begin.


07:34 am November 19, 2024

Agree with Ian, the product owner needs to communicate the product goal. This should be enable the team to create epics at a high level (should be prioritized by PO). Next the team can break down the epics to stories (add proper acceptance criteria and ensure each story delivers value). Then in the sprint planning let the team decide what should be pulled in. Utilize the sprint review and ensure the right stakeholders are available for the same to get the best possible feedback.

Another point you might have to check is the dependencies between prog 1,2 and 3. You mentioned PI planning which is essentially from SAfe so my guess is the 3 programs have some kind of dependencies or together contribute to your product.


06:45 pm November 19, 2024

Both @Ian and @Anand gave you great answers based upon the Scrum framework that is defined in the Scrum Guide (https://scrumguides.org/).  

However, it sounds like you are asking about how to accomplish something in SAFe. SAFe uses a version of Scrum that they created called ScrumXP (https://v5.scaledagileframework.com/scrumxp/). PI Planning (https://v5.scaledagileframework.com/pi-planning/) is a fairly regimented process in SAFe. And a Program Increment (PI) is also defined (https://v5.scaledagileframework.com/program-increment/).

Looking at those resources I would say that Program 3 is not ready to be included in PI Planning since it cannot be clearly understood and defined. It should be deferred to another PI Planning event so that it can be better prepared.  Have you considered Program 4? Is it ready?


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.