linaro-project-management team mailing list archive

[Fathi Boudra <fathi.boudra@xxxxxxxxxx>]

Hi,

On 7 September 2011 01:25, Christian Robottom Reis <kiko@xxxxxxxxxx> wrote:
> On Tue, Sep 06, 2011 at 01:29:14PM +0200, Alexander Sack wrote:
>> so a while back me and fabo discussed using blueprints to burn down the
>> "standard" release monthly release and develop a default template that would
>> be instantiated for each and every month. If you look at the
>> project-management project you can see the current instance there.
>
> I assume you mean
>
>    https://launchpad.net/linaro-project-management/+milestone/2011.09

Yes

>> 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.

> I think you're suggesting something a bit different for the actual
> engineering teams, though. Is there an example blueprint we can see that
> explains how this will work?

My understanding is that we want to track the progress of managements
tasks in the same way we do for the engineering teams: using
blueprints and work items. It aims to have more visibility on the
Release process and PM work.

We have initial BPs used for Linaro 11.08 and are improved on the road to 11.09.
Below, you have 3 types of BPs:
 * relevant to Release Team like
https://blueprints.launchpad.net/linaro-project-management/+spec/linaro-other-o-11.09-release-tracking
 * relevant to Release Team/PMs like
https://blueprints.launchpad.net/linaro-project-management/+spec/linaro-other-o-11.09-gather-proposed-headlines
 * relevant to individual PM to track his pet project like
https://blueprints.launchpad.net/linaro-project-management/+spec/linaro-other-o-website-downloads-page-update
or https://blueprints.launchpad.net/linaro-project-management/+spec/linaro-other-o-toolchain-builders-utilisation

>> 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.

Cheers,

Fathi