linaro-project-management team mailing list archive

[Alexander Sack <asac@xxxxxxxxxx>]

On Mon, Aug 15, 2011 at 7:03 PM, Joey Stanford <joey@xxxxxxxxxx> wrote:

> >   * 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.
>
> Correct!
>
> > Can this scheme work well if we don't have a priority ordered backlog
> > per-team, and only have one per-project?
>

I am not sure I understand your question.

What I read is whether we can live with not having all projects of a team
under one project group and hence we don't have an easy rolled-up view of
the whole team backlog by using the project group URL of that milestone?

If thats the question, then the answer is definitely yes. I don't see why we
can't live with that for the time being. Improving project groups to allow
you having everything under one project group is what is called out in kikos
slide as "May need to grow “better project grouping” abilities" (kiko slide
6).

Until we have that, we can artificially move all projects we use for a team
under the same project group or accept that we have to look at a couple of
milestone views during planning/tracking/reporting until launchpad can
support us here. Also note that status.linaro.org could help
band-aiding/fixing this by providing nice team views.

-- 

 - Alexander