[almighty] Portfolio backlogs vs Product backlogs?

[Pete Muir]

For pizza, if someone wants to manage a portfolio, we would recommend they
use a project for the portfolio, and use areas to divide up the work.

On 10 Nov 2016 7:19 a.m., "Michael Kleinhenz" <kleinhenz at redhat.com> wrote:

> > My original understanding was that product backlogs are where work is
> > scoped, estimated and executed, and portfolio backlogs should just
> reflect
> > this in a rolled up manner. A portfolio WI is 'done', when the rolled up
> > stories in product backlogs are 'done'.
>
> I also thought exactly that until I talked to some POs at my old
> company in my last week there. I was talking to them about project
> management software in preparation for this job. They consistently
> told me that if the lower level stories in the product backlogs are
> done, this does not mean the portfolio "story" is done. There are
> different Definitions of Done in place on the different layers and
> there also may be additional tasks on the higher level, like "review
> and approve".
>
> -- Michael
>
> --
> Michael Kleinhenz
> 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
>
> _______________________________________________
> almighty-public mailing list
> almighty-public at redhat.com
> https://www.redhat.com/mailman/listinfo/almighty-public
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/almighty-public/attachments/20161111/aef709d8/attachment.htm>