Project Management

Please login or join to subscribe to this thread

Change in Portfolios and Programs in Scrum

linkedin twitter facebook  
avatar
Tam Nguyen Annandale, Va, United States
Can someone explain this statement " Portfolio Prioritized Product Backlog Meeting (also referred to as Portfolio Backlog Meeting), should be conducted at 4-12 month intervals. The frequency and impact of changes to a portfolio largely determine the time duration between two Portfolio Backlog Meeting. If there are several expected changes in portfolio, it is preferable to conduct Portfolio Backlog Meeting at more regular intervals (4-6 month), but if there are fewer expected changes and if requirement are stable, the duration between two Portfolio Backlog Meeting could be increased (9-12 month)

Why Portfolio Backlog Meeting need short duration for several expected changes but It needs longer duration for fewer expected changes.
Sort By:
avatar
Wade Harshman Scrum Master| GDIT Indianapolis, In, United States
Where does this statement come from?
...
1 reply by Tam Nguyen
May 31, 2017 4:48 AM
Tam Nguyen
...
In Scrum. Chapter 6 pages 112. thank you
avatar
Saket Bansal Gurgaon, Haryana, India
What i feel is you made " it is preferable to conduct Portfolio Backlog Meeting at more regular intervals" = Short Duration of Meeting itself .

In my view the text you shared saying that we need to conduct portfolio backlog prioritization meeting frequently when we expect many changes in priority , if the market is stable we may not need to do prioritization so frequent hence the meeting can be done at less frequency.
...
1 reply by Tam Nguyen
May 31, 2017 4:47 AM
Tam Nguyen
...
If there are several expected changes in portfolio, it is preferable to conduct Portfolio Backlog Meeting at more regular intervals (4-6 month), but if there are fewer expected changes and if requirement are stable, the duration between two Portfolio Backlog Meeting could be increased (9-12 month)
But the statement said different. there are fewer requirement taking 9-12 month. That I concerned
avatar
Tam Nguyen Annandale, Va, United States
May 30, 2017 12:36 PM
Replying to Saket Bansal
...
What i feel is you made " it is preferable to conduct Portfolio Backlog Meeting at more regular intervals" = Short Duration of Meeting itself .

In my view the text you shared saying that we need to conduct portfolio backlog prioritization meeting frequently when we expect many changes in priority , if the market is stable we may not need to do prioritization so frequent hence the meeting can be done at less frequency.
If there are several expected changes in portfolio, it is preferable to conduct Portfolio Backlog Meeting at more regular intervals (4-6 month), but if there are fewer expected changes and if requirement are stable, the duration between two Portfolio Backlog Meeting could be increased (9-12 month)
But the statement said different. there are fewer requirement taking 9-12 month. That I concerned
avatar
Tam Nguyen Annandale, Va, United States
May 30, 2017 11:20 AM
Replying to Wade Harshman
...
Where does this statement come from?
In Scrum. Chapter 6 pages 112. thank you

Please login or join to reply

Content ID:
ADVERTISEMENTS

"There is nothing more difficult than talking about music."

- Camille Saint-Saens

ADVERTISEMENT

Sponsors







Vendor Events

See all Vendor Events

Newsletters

Jun 3: The Career Problem Facing New PMs
May 20: Your PM Career as a Project Life Cycle
May 13: The Big Lie After Layoffs

See all newsletters