linaro-project-management team mailing list archive

[Roger Teague <Roger.Teague@xxxxxxx>]

Hi ya,

Works for me too .

- Roger

-----Original Message-----
From: Andrea GALLO [mailto:andrea.gallo@xxxxxxxxxxxxxx]
Sent: 15 May 2012 18:28
To: 'ilias.biris@xxxxxxxxxx'; 'opscom@xxxxxxxxxx'; 'techleads@xxxxxxxxxx'; 'linaro-project-management@xxxxxxxxxxxxxxxxxxx'
Subject: Re: Reporting proposal

Ilias,

Sounds very good to me!

Thank you,

Andrea

----- Original Message -----
From: Ilias Biris [mailto:ilias.biris@xxxxxxxxxx]
Sent: Tuesday, May 15, 2012 04:41 PM
To: TSC Operational Subcommittee <opscom@xxxxxxxxxx>; Linaro Tech Leads <techleads@xxxxxxxxxx>; Proj Mgmt Mailing List <linaro-project-management@xxxxxxxxxxxxxxxxxxx>
Subject: Reporting proposal


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 ilias.biris@xxxxxxxxxx
Project Manager, Linaro
M: +358504839608, IRC: ibiris Skype: ilias_biris
Linaro.org│ Open source software for ARM SoCs

-- IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium.  Thank you.