[almighty] Portfolio backlogs vs Product backlogs?

[Michael Kleinhenz]

>> 1. Iterations are hierachical
>>     -> an Interation on a program level may contain several iterations
>> on an implementation level, also across projects.
>>         So we could have "business iterations" that contain several
>> iterations of other projects in the org.
>
> I'm unsure whether business iterations need to roll up other iterations.
> But, lower level product backlogs do have to be rolled up to a higher level
> portfolio backlog.
> We can continue discussing this.

Mmmh, but does a backlog makes sense without something like
iterations? Without iterations, the character changes: from an actual
"working on" to a "control of". Such a program backlog model would be
of use for a scenario where it is solely used for controlling state
and progress of the actual "working" projects below. But it this a
realistic usecase? I doubt that, because:

1. there might also be work items on the program level: "approve
features", "strategic definitions" etc.

2. iterations on a program level might have a different business
meaning, like "fiscal year".

I think having iterations there definitely makes sense.

-- Michael


--
Principal Software Engineer

Red Hat Deutschland GmbH
Werner-von-Siemens-Ring 14
85630 Grasbrunn
Germany

RED HAT | TRIED. TESTED. TRUSTED.
Red Hat GmbH, www.de.redhat.com,
Registered seat: Grasbrunn, Commercial register: Amtsgericht München,
HRB 153243,
Managing Directors: Paul Argiry, Charles Cachera, Michael Cunningham,
Michael O'Neill