Linaro 11.10 - Planning phase

Registered by Fathi Boudra

This BP ensures that teams have done their monthly planning.
It aims to define the planning process that we can execute from an operational point of view.

Links:
The headlines consolidation is done on http://wiki.linaro.org/Cycles/1110/Release/Blueprints

Blueprint information

Status:
Complete
Approver:
Fathi Boudra
Priority:
Essential
Drafter:
Fathi Boudra
Direction:
Approved
Assignee:
Linaro Project Management
Definition:
Approved
Series goal:
Accepted for trunk
Implementation:
Implemented
Milestone target:
milestone icon 2011.10
Started by
Fathi Boudra
Completed by
Fathi Boudra

Related branches

Sprints

Whiteboard

Work items (11.10):
[ibiris] Gather proposed headlines from Graphics PM, consolidate on release blueprints wiki page: DONE
[mounir-bsaibes] Gather proposed headlines from Kernel PM, consolidate on release blueprints wiki page: DONE
[anmar, usman-ah] Gather proposed headlines from Landing Teams PM, consolidate on release blueprints wiki page: DONE
[ibiris] Gather proposed headlines from Multimedia PM, consolidate on release blueprints wiki page: DONE
[tony-mansson] Gather proposed headlines from Android PM, consolidate on release blueprints wiki page: DONE
[dzinman] Gather proposed headlines from Developer Platform PM, consolidate on release blueprints wiki page: DONE
[dzinman] Gather proposed headlines from Infrastructure PM, consolidate on release blueprints wiki page: DONE
[fboudra] Gather proposed headlines from Validation PM, consolidate on release blueprints wiki page: DONE
[mounir-bsaibes] Gather proposed headlines from Power Management PM, consolidate on release blueprints wiki page: DONE
[mounir-bsaibes] Gather proposed headlines from Toolchain PM, consolidate on release blueprints wiki page: DONE

Notes:
* more details and information on the blueprint. it should be more planning/PM oriented.
* split to 1 blueprint per team? ownership of PMs to deliver a complete blueprint. start with 1 overall blueprint then split when needed.
* collect feedback from stakeholders throughout the month
  - we need to make it more explicit how you can influence the "next" queue
  - asac thinks that roadmap view could have instructions who to contact and send requests to if you want to change something in the next queue or backlog priority or want to add something to backlog (or even remove)
  - should PMs organize a call with key stakeholder a week before planning to allow high bandwidth discussion?
* document feedback received throughout the month and on stakeholder call in the planning blueprint
* PM run a call with TL to review backlog/next queue, decide which one go next, ensure that those have the right fields (acceptance/headline) and adjust priority based on feedback etc...
  - how to consider push forwards in the plan?
* make a monthly plan summary/document
  - tell the story of what will be delivered
  - tell the story of what (if we know) we currently have planned for the upcoming month
  - document stakeholder requests that could be accomodated
  - document stakeholder requests that could not be accomodated
  - propose key topics for the month
* plan due on monday (latest tuesday) after release
* all stakeholder comments due by release day -> asking for plan adjustment/priority-boost etc.
* stakeholder call (if needed) to happen during release week
* all linaro release review report due on monday after all-linaro release
  - basically the reports from teams releasing earlier are collected and wrapped here
* no all linaro plan will be published, because some teams are already half way through their cycle -> teams need to publish their plans individually.

Rules for blueprints operations:
* initial set of blueprints is announced after planning, following the release day (see planning process above)
* Team and PM should be explicitely subscribed by the blueprint creator/writer.
* high and essential blueprints are always committed -> rescope or push back needs to go through RM/PM/post-mortem
* medium and low blueprints can be dropped back to backlog or pushed forward or rescoped as needed (as long as they somewhat keep the same spirit); PM should be informed so this can be recorded for stats -> PM should be just subscribed to all blueprints
* adding new blueprints is fine as long as rules above are honoured
* expanding scope of blueprints (if the old scope is a subset) is also fine, but TLs/PMs are encouraged to rather create a new blueprint.

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.