[Fiware-wpa] backlog management of "your" chapter for recurring tasks on "Tracker"-items

[Sandfuchs, Thorsten]

Dear colleagues,

as SAP I can offer you support on your particular backlog-tasks and efforts which might be automatable.



Eg. for the apps chapter we migrated a lot of issues (860 issues going down to ~420 issues) with very limited manual effort.



I tried to summarize in the table below what might be effected by this automatism, I won't check your reviews proactively, if you think it might be relevant for your tracker/backlog improvements please check the list below. Please let me know what you think could be automated and I can consider implementing this - although I can't promise resolutions in all cases!



Your task would be to focus on the "larger" portions that need to be fixed (as it requires still some manual work on my side to customize the scripts) and saves more time. If you would have in C1 e.g. only 2 items, then I would kindly refrain from investing time into it J



Best,

                                                               /Thorsten





Things that MIGHT be automated:

C1 - sprint and release fields

--> consistency  of features != open with release and sprint

--> consistency of epics with release and sprint

>>>>> Scheduled Stories need to have release and sprint

>>>>> Scheduled Features need to have release, sprint is not needed

>>>>> Scheduled Epics don't need to have either release or sprint



ð  I can delete arbitrary fields, if Manuel thinks they are not needed any more and implies this as error


C2 - backlog reference (summary) consistency with its fields

--> items' reference with inconsistent entry type

>>>>> Items whose entry type field is not consistent with the entry slot of the reference



ð  I can change e.g. STORY to Story or similar transitions on field level

C5 - Items' descriptions

--> backlog items (Story, WorkItem, Bug) with no description on the tracker

--> backlog items (Epic, Feature) whose description is provided on the wiki

>>>>> Descriptions of Epic and Feature are provided in the wiki, so duplicated here.

>>>>> These descriptions can be removed



ð  I can delete arbitrary fields automatically





Things that are hard or NOT possible to automate



C3 - backlog hierarchy


C4 - Tracker link to the Wiki

--> links not needed: Story, WorkItem and Bug on tracker

--> links non existing or inconsistent with their reference in tracker

--> expected backlog items references (Epic, Feature) but not available in wiki directory (materializing)

--> consistent urls but a connection try failed



... and all other things that are NOT listed before J





--



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/20131120/8c9e2d0e/attachment.html>