linaro-project-management team mailing list archive

[Mounir Bsaibes <mounir.bsaibes@xxxxxxxxxx>]

On Wed, Jan 18, 2012 at 12:23 PM, David Zinman <david.zinman@xxxxxxxxxx>wrote:

> I'd like to generate some discussion here since the project
> managers are the point of focus for this system and are on
> the hook for some deliverables.
>
> The proposed timeline has the first deliverable on Jan 29 and that
> date is quickly approaching.
>
>  2011Q4 Work Items:
>         * All cards and blueprints updated
>         * Acceptance Criteria review, tested and go/no go decisions
>         * Short blurb on each not pass
>         * blueprints review - what was done, what was left out;
>            * how does that impact the objective
>            * influencing factors/unexpected events
>            * recommendations about not met criterias/oustanding
>              work
>         * Suggestions for future work
>
>   2012Q1 Work Items:
>        * One page plan for each roadmap card.
>
            What is intended here? Is it the same as "... good
understanding about the topic and a potential Agile plan" ?
             Please clarify.

>
>  For Linaro Connect Feb 6 - 10:
>        * For already existing cards and new proposed cards we should
>          go to connect with a good understanding about the topic and
>          a potential agile plan in mind.
>         * TSC presentation of summary of reports
>        * Dicussion of each relevant card by technical team
>
>
> On 18 January 2012 08:41, Alexander Sack <asac@xxxxxxxxxx> wrote:
> > Hi all,
> >
> > kiko and me discussed what to do with the cards now that we approach
> > end of quarter.
> >
> > Outcome was a set of timelines for the coming end/start of the quarter.
> >
> > If you have questions about any of these points, see at the bottom of
> > this mail, check with your PM, talk to dzin/me or just ask here :).
> >
> >
> >  Jan 29th: Q4 report, pre-plans ready for Connect
> >       * 2011Q4
> >           * All cards and blueprints updated
> >           * Acceptance Criteria tested and go/no go
> >           * Short blurb on each not pass
> >           * Suggestions for future work
> >       * 2012Q1
> >           * One-page plan for each roadmap card
> >
> >  Feb  5th: Connect
> >       * TSC presentation of summary of reports
> >       * Dicussion of each relevant card by technical team
> >
> > Feb 20th: Connect Plan Review
> >       * Agile Plan -- envisioned sequence/set of deliveries/steps to
> > deliver the plan (in form of blueprints) and 1-liner for each
> > blueprint
> >
> > Feb 27th: Work Item Review
> >       * All blueprints with work items recorded
> >
> >> Questions:
> >>
> >>    - Where do we record the deliverables above?
> >>        * Q4 report
> >>        * Q1 pre-plan
> >
> > Plan and report should go on papyrs card itself or to dedicated
> > wiki/papyrs pages that get linked from the card. PMs to flash out the
> > details.
> >
> >>
> >>    - How do we verify delivery of the above?
> >
> > PMs/TLs are responsible to deliver their card reports/plans. The
> > TSC-operational team (loic et al) is tasked to bring a quarterly plan
> > and post-mortem report together. At best they would work with the PMs
> > and techleads on that.
> >
> >>
> >> What is this agile plan?
> >
> > asac quick answer attempt:
> > "An agile plan is a set of steps/working blocks that based on the
> > current understanding need to be executed to meet the acceptance
> > criteria of a card. An agile plan usually is pretty accurate and
> > detailed about the first steps and more vague/flexible/scarce about
> > the steps coming afterwards. However, it should convey that there is a
> > plan that is worked against and that is continuously adjusted."
> >
> >>
> >> Who is supposed to do the work coming out of this and in particular the
> reports?
> >
> > PMs are supposed be the main owners/drivers of producing these
> > reports. Hence, they would also come up with a standardized
> > form/template for the reporting. Of course, TLs need to support them
> > and do the hard thinking to ensure that the agile plan makes sense and
> > is not too far from reality.
> >
> > --
> > Alexander Sack
> > Technical Director, Linaro Platform Teams
> > http://www.linaro.org | Open source software for ARM SoCs
> > http://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog
>
>
>
> --
> David Zinman
> Linaro Release Manager | Project Manager
> Linaro.org | Open source software for ARM SoCs
>



-- 
Mounir Bsaibes
Project Manager

Follow Linaro.org:
facebook.com/pages/Linaro/155974581091106
http://twitter.com/#!/linaroorg
http://www.linaro.org/linaro-blog <http://www.linaro.org/linaro-blog>