Hi, 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.
This worked well, and we would like to use that model to standardize and track more of the release - process going deeper to the PM team level now. 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. For both phases all teams will get a small blueprint each and every month assigned to their PM; escalation and discussion etc. would happen through the blueprint instead of through IRC private chat. This would give me and management more transparency where we stand and where the roadblocks that we need to help with and I don't need to ask fabo that often anymore. 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. Let us know if you don't like this process innovation. Also let us know if you would like email reminders for upcoming PM deliverables on this list or rather one mail at the beginning of the month stating what is due when. -- - Alexander
_______________________________________________ Mailing list: https://launchpad.net/~linaro-project-management Post to : [email protected] Unsubscribe : https://launchpad.net/~linaro-project-management More help : https://help.launchpad.net/ListHelp
