[Fiware-wpa] Proposal to change hirarchy metric on tracker backlog calculations

[Sandfuchs, Thorsten]

Dear colleagues,

So far I agreed with Manuel on some improvements of the tracker calculations, which actually didn't make it across to his final numbers. These final numbers are now the ones that are finally reported to the EC, I think it would help that the WPL/WPA board is taking some decisions in order to significantly improve the situation and get to a much better "backlog" performance with as little as possible manual work for us.



Please take the proposal below as initial try to come up with new metrics and improve the existing performance and please support this proposal itself. If you think this needs to be further discussed in the Monday morning meeting, I'm happy to comment on this as well. Other than that I would think that it would be sufficient for Manuel that all chapters would agree to a certain case and he would go forward with this.



You probably followed the discussion of Manuel and the some colleagues out of the apps chapter on the metric which is related to "hierarchy" of backlog items.



As the apps chapter colleagues already communicated in a number of 1:1-telcos and consistently, we think the focus of having a consistent hierarchy is acceptable for ongoing and upcoming features and might be entitled for this kind of tracking. But as the rules on how the hierarchy was finally computed actually is quite "new" in relation to the overall FI-WARE project timeframe, I would propose to keep the focus on relevant (upcoming) things and not lose the focus in tedious renaming of items, which proof little value to the outside. This consensus to act in this way was initially reached on Telco level (at least this is what my opinion is and Manuel might disagree) - I did not insist to reflect this in the numbers, as this poses more effort on Manuel than on us to just "ignore" these numbers. Now and as the numbers are getting reported to the EC as "errors", we need to bring this up again and would seek for your opinion and support on how to go forward with this:



Proposal: ignore all "old" tracker-items (closed and dismissed) in the backlog-hierarchy computation in order to focus our work the relevant state-of-play and upcoming tasks.

This applies to T-C3:

Concept = stories with no feature father

>>>>> Stories need a Feature father to exist





Implications for chapters => leading to X% of resolution

-          Security: 2 out of 2         => 100%  resolution

-          Data: 37 out of 55           => 67% resolution

-          I2ND: 1 out of 2               => 50% resolution

-          Cloud: 16 out of 38         => 42% resolution

-          Apps: 111 out of 123      => 90% resolution



It is evident that apps has the most "effort" here, but you can clearly see that this metric with the new "rule" would greatly provide a "better" rating across the board of more than 50% (despite cloud with 42%) for each of the chapters.



Can you please vote if you would support this proposal or give an indication on how you want to discuss this further.



Please note: I have as well other proposals on how to improve the current metrics of backlog calculation which are not related to this and will be further distributed subsequently (additionally I'm reemphasizing that I can change a lot in your backlogs automatically now, hopefully closing this sooner and with less manual work for all of us).



Thank you and best regards,



                                                               /Thorsten



--



Thorsten Sandfuchs



SAP AG | Vincenz-Priessnitz-Strasse 1 | D-76131 Karlsruhe, Germany | www.sap.com<http://www.sap.com/>





Pflichtangaben/Mandatory Disclosure Statements: http://www.sap.com/company/legal/impressum.epx



Diese E-Mail kann Betriebs- oder Geschäftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrtümlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielfältigung oder Weitergabe der E-Mail ausdrücklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank.



This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation.



Please consider the environment before printing this mail!





-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-wpa/attachments/20131121/4775ed59/attachment.html>