linaro-project-management team mailing list archive

[Christian Robottom Reis <kiko@xxxxxxxxxx>]

On Wed, Sep 07, 2011 at 10:54:27AM +0300, Fathi Boudra wrote:
> >> For that fabo will create a template and initial blueprint
> >> instances for the two key PM events during the month: planning and
> >> post-mortem; we feel that this has been managed a bit lax in the
> >> past and fabo currently has to do quite a few manual pokings etc.
> >> and we think having those blueprints will help better track
> >> progress.
> >
> > I"m not sure exactly what you mean here -- I see 3 blueprints for l-p-m
> > which I think are relevant:
> >
> >    https://blueprints.launchpad.net/linaro-project-management/+spec/linaro-other-o-11.09-release-tracking
> >    https://blueprints.launchpad.net/linaro-project-management/+spec/linaro-other-o-11.09-release-response-team-tracking
> 
> These 2 are relevant to the Release Team. They track the release progress.
> 
> >    https://blueprints.launchpad.net/linaro-project-management/+spec/linaro-other-o-11.09-gather-proposed-headlines
> 
> That's the current BP targeted to PMs. It covers the planning tracking
> part. I still need to do the post-mortem related BP.
> Note that linaro-other-o-11.09-release-tracking should/will depend on
> these BPs implementation.

Right, but referring back to the "two key PM events" you mention in your
original paragraph above -- does that mean you will have a "Planning" and
a "Post-Mortem" pair of blueprint, or were you just misleading me? ;-)

I'm not clear if any of the links above is one of those two.

> >> Driving delivery of those blueprints will be worked into the
> >> overall release blueprint for now. Later we probably will make one
> >> more standalone blueprint to drive those two very important phases.
> >
> > I don't know what you mean in this piece :-/
> 
> As we started to use the BPs to track the project management tasks,
> the format of BP isn't written in stone. I started with a planning and
> post-mortem (coming) blueprints. This format could change in the
> future for improvement, visibility, whatever reasons.

I guess I still don't understand how this process is meant to work. Can
you restate the whole process in terms that my little overburdened brain
can record :-)?
-- 
Christian Robottom Reis, Engineering VP
Brazil (GMT-3) | [+55] 16 9112 6430 | [+1] 612 216 4935
Linaro.org: Open Source Software for ARM SoCs