<div dir="ltr">I'll go on the record as saying that I once helped create a system whereby child tasks could automatically update parent tasks -- for example: "all the children are done, so mark the parent as done."<div><br></div><div>It was a terrible, terrible mistake.</div><div><br></div><div>Yes, on paper, it looks like the right thing to do. In reality, reality is much, much different. For very strict, waterfall processes, it can sometimes work. But that assumes you've got a completely well-defined, repeatable and essentially unchanging process. (e.g. an assembly line or a process you manage with a Gantt chart). But, outside of that scope, it rarely works well.</div><div><br></div><div>e.g. consider a value prop broken down into experiences to be accomplished over the next 6 months. Assume all of the experiences are completed. Is the value prop now 'done/realized'? Maybe it is, but maybe it is not (or at least not fully). Maybe to fully realize the value prop requires three 6 month seasons of experiences. In other words, just because I have 4 children now doesn't mean I won't have additional children later. The closing out of the value prop is really a human decision, not an algorithmic one.</div><div><br></div><div>Will some people want automatically closing parents? Probably. Should we have that as an option? Maybe, but not for Pizza the Hutt. Many, many popular systems are surviving without this feature and happy users. The unhappy ones can go use IBM DOORS or something like that. :)</div><div><br></div><div>Note that it may be valuable to <i>highlight</i> any such inconsistencies -- e.g., some form of UI that draws my attention to an open parent with all children closed, or a report that lists all such WIs for me. That may help me to identify things on which I should make a decision.</div><div><br></div><div> -Todd</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Sep 30, 2016 at 2:12 AM, Max Rydahl Andersen <span dir="ltr"><<a href="mailto:manderse@redhat.com" target="_blank">manderse@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><u></u> <div> <div style="font-family:sans-serif"><span class=""><div style="white-space:normal"> <p dir="auto">On 30 Sep 2016, at 7:24, Ranjith Varakantam wrote:</p> <p dir="auto"></p></div> <div style="white-space:pre-wrap"><blockquote style="border-left:2px solid #777;color:#777;margin:0 0 5px;padding-left:5px"><div dir="auto">On Fri, Sep 30, 2016 at 1:22 AM, Leonard Dimaggio <<a href="mailto:ldimaggi@redhat.com" target="_blank">ldimaggi@redhat.com</a>> </div><div dir="auto">wrote: </div><div dir="auto"> </div><blockquote style="border-left:2px solid #777;color:#999;margin:0 0 5px;padding-left:5px;border-left-color:#999"><div dir="auto">Ranjith, </div><div dir="auto"> </div><div dir="auto">When you say: </div><div dir="auto">'...If yes, would it get incrementally updated along with each of child </div><div dir="auto">work item?...' </div><div dir="auto"> </div><div dir="auto">Are you referring to a state change in a child element resulting in an </div><div dir="auto">automatic state update in its parent element? </div><div dir="auto"> </div></blockquote><div dir="auto"> </div><blockquote style="border-left:2px solid #777;color:#999;margin:0 0 5px;padding-left:5px;border-left-color:#999"><blockquote style="border-left:2px solid #777;color:#bbb;margin:0 0 5px;padding-left:5px;border-left-color:#bbb"><div dir="auto">Yes, for example a user story has 4 tasks, when these tasks are </div></blockquote></blockquote><div dir="auto">complete, the user story should automatically be marked complete. The same </div><div dir="auto">would hold good for experience, if the user stories related to the user </div><div dir="auto">stories are complete then the experience state should also change. </div></blockquote></div> </span><div style="white-space:normal"> <p dir="auto">this assumes you have captured <em>everything</em> in all tasks and upfront knows nothing else are there.</p> <p dir="auto">I would not think automatic changing state to complete is the right thing to do.</p> <p dir="auto">Being able to list issues which have all their children and dependent issues resolved so<br> one can make an explicit decision - <em>thats</em> useful.</p> <p dir="auto"></p></div><span class=""> <div style="white-space:pre-wrap"><blockquote style="border-left:2px solid #777;color:#777;margin:0 0 5px;padding-left:5px"><blockquote style="border-left:2px solid #777;color:#999;margin:0 0 5px;padding-left:5px;border-left-color:#999"><blockquote style="border-left:2px solid #777;color:#bbb;margin:0 0 5px;padding-left:5px;border-left-color:#bbb"><div dir="auto">This would also inline with the query based results that Todd suggested, </div></blockquote></blockquote><div dir="auto">because when I am refining the backlog, I only want to see the experiences </div><div dir="auto">or user stories that are yet to be worked on. i.e. the ones which are not </div><div dir="auto">completed. </div></blockquote></div> </span><div style="white-space:normal"> <p dir="auto">Yup - but that query should be done by query and stories going into the state of being in progress,<br> not about amount of child tasks it has IMO.</p> <p dir="auto">/max<br> <a href="http://about.me/maxandersen" style="color:#3983c4" target="_blank">http://about.me/maxandersen</a></p> </div> </div> </div> <br>______________________________<wbr>_________________<br> almighty-public mailing list<br> <a href="mailto:almighty-public@redhat.com">almighty-public@redhat.com</a><br> <a href="https://www.redhat.com/mailman/listinfo/almighty-public" rel="noreferrer" target="_blank">https://www.redhat.com/<wbr>mailman/listinfo/almighty-<wbr>public</a><br> <br></blockquote></div><br></div>