+1 on the proposal. Very good to have lightweight weekly exception trigger in place and organize sharp roadmap updates once a month, aligned with our "normal" engineering wrap up.
On Tue, May 15, 2012 at 4:41 PM, Ilias Biris <[email protected]> wrote: > > Hello folks > > Regarding the JIRA reporting from engineering I would like to propose > the following change. As a reminder currently I have asked for a > progress update in JIRA cards on a biweekly basis (every second Wednesday) > > Setting up two levels of reports with individual requirements: > > 1. weekly JIRA progress updates extracted from the weekly team meeting > - must notify of new BLOCKED work, problems or risks > - it is ok to not have an update if there is no significant change, > we would take no news as good news (everything going well). However if > you reported blocked items earlier, or risks, you should follow up > otherwise I will try to get in touch with the TLs to get fresh info on > those troubled items. > > 2. monthly - on the week of the release: getting detailed JIRA progress > updates based on the release information, post mortem feedback which > should include additionally the TL/PM assessment of milestone ETA for > delivery of the card (and a warning about any changes to ETA). I would > expect that even if progress is going superwell there would be some > update on the progress in this monthly info > - in this report we should also get a list of blueprints packages > delivered for the card during the related month update. However please > note that just listing the blueprints does not say much to the beholder > - the narrative mentioned above is important. > > This breaks slightly the requirement of having succinct reports, but it > would give an opportunity to cover slightly more questions on a monthly > basis. > > What do you think? Is that something we could establish already? Is the > timing useful? Hopefully the 2nd level of the updates would not be a > huge amount of extra work, but I am open to counter proposals. > > > BR, > -- > Ilias Biris [email protected] > Project Manager, Linaro > M: +358504839608, IRC: ibiris Skype: ilias_biris > Linaro.org│ Open source software for ARM SoCs -- 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 _______________________________________________ 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
