linaro-project-management team mailing list archive

[Mounir Bsaibes <mounir.bsaibes@xxxxxxxxxx>]

On Wed, Jan 18, 2012 at 7:41 AM, 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.
>
On Papyrs should work fine. We can update the card template to have a new
section called, for example, Card closeout and have  multiple sub-sections
inside the closeout section:
1) report - what was delivered and what was not , reason why, etc...
2) tsc directive -  ( is enough delivered to close the card or do something
additional, create new card or simply add a new blueprint to really
complete the left over)
with the closeout section we can associate a check list, similar to when
the card was created:
1) report done
2) operation review
3) tsc directive
4) directive followed

 Mounir

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



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