On Mon, 15 Aug 2011 10:39:55 -0400, James Westby <[email protected]>
wrote:
> On Sat, 13 Aug 2011 10:43:25 +0200, Alexander Sack <[email protected]> wrote:
> > create project for status.linaro.org as part of infrastructure
> > component, create "backlog" milestone, put it there with essential
> > importance, and there its sitting quite high on top! :-P
>
> A couple of problems with this:
>
> * That's the backlog for one component. If we have essential items in
> the backlog for every component then which is most essential?
>
> * More importantly nowhere in our process does a backlog currently
> appear, so I don't see much value in doing this currently. The
> slides presented by kiko mention a backlog, but don't explain how it
> will be used, and I don't see a use for one in that presented plan.
Going over it again, I think I've found where the backlog lives:
* When a card is decomposed at a Connect, the resulting engineering
blueprints are placed in a backlog.
* At the start of each month blueprints are taken from the backlog
and assinged.
* At the end of each quarter anything that remains on the backlog is
assessed, and dropped or moved to another quarter.
Can this scheme work well if we don't have a priority ordered backlog
per-team, and only have one per-project?
Thanks,
James
_______________________________________________
Mailing list: https://launchpad.net/~linaro-project-management
Post to : [email protected]
Unsubscribe : https://launchpad.net/~linaro-project-management
More help : https://help.launchpad.net/ListHelp
