+1. However, post mortem feedback by definition happens only after the release; it cannot happen on the week of the release. To accurately report which blueprints get delivered for the cycle before the cycle ends, development and verification of the blueprint must be complete by the day of release candidate (the Monday before release). Our current agile process allows for development to continue up to the day of the release.
Post mortem meetings and evaluations happen on the day after release and the post mortem report is issued very early at the beginning of the next cycle. Note that this pertains only to blueprint reporting, not the status or ETA of card delivery which should be reported on the last week of the cycle and rolled into the post mortem after the cycle has finished. On 16 May 2012 09:24, Ilias Biris <[email protected]> wrote: > Hi > > thanks to all who responded. I got only +1s by the way. TLs/PMs can we > already start this model this week? It would be a level 1 reporting > (weekly-style) based on the description - can these updates be added by > end of Friday this week - latest? > > Best regards, > Ilias > > On 15/05/12 17:41, Ilias Biris 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 -- David Zinman Linaro Release Manager | Project Manager Linaro.org | Open source software for ARM SoCs _______________________________________________ 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
