<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Agreed - as one who files bugs, I’m not expecting them to take priority over anything already in the Sprint. Rare cases may call for something to be triaged quickly, but I have never felt that bugs are always a ‘do this now’ type of item.<div class=""><br class=""></div><div class="">-Adam</div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Oct 20, 2016, at 5:47 AM, Ranjith Varakantam <<a href="mailto:rvarakan@redhat.com" class="">rvarakan@redhat.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div class="">Same goes for research activities (Spikes). <span class="gmail-_Tgc">We need to define a Story when our aim or goal is to answering a question or gathering information and schedule it in a Sprint just like any other story along with estimation. <br class=""><br class="">1. We should clearly define it the acceptance criteria, in this case what are we trying to find out and to what degree of confidence <br class="">2. Also time box it. That is to say that we will spend a maximum of 2 days on it and make a decision based on that information.<br class=""><br class=""></span></div><span class="gmail-_Tgc">Ranjith<br class=""></span> </div><div class="gmail_extra"><br class=""><div class="gmail_quote">On Thu, Oct 20, 2016 at 12:58 PM, Thomas Mäder <span dir="ltr" class=""><<a href="mailto:tmader@redhat.com" target="_blank" class="">tmader@redhat.com</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">What he said. Same with "technical debt tasks". Let's do it!<span class="HOEnZb"><font color="#888888" class=""><br class=""> <br class=""> /Thomas</font></span><span class="im HOEnZb"><br class=""> <br class=""> On 10/19/2016 04:36 PM, Michael Kleinhenz wrote:<br class=""> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> Hi,<br class=""> <br class=""> because this topic was popping up in today's plannings. My 2ct on bugs<br class=""> vs. stories in the planning process:<br class=""> <br class=""> Usually bugs are treated like stories in the planning process. They<br class=""> should be part of the backlog and should be part of the order of<br class=""> execution. They should also be estimated and placed into sprints like<br class=""> stories. In an ideal case this leads to a backlog that consists of<br class=""> stories ("new features") and bugs ("debts") that are treated equal in<br class=""> terms of planning an iteration.<br class=""> <br class=""> Comments?<br class=""> <br class=""> -- Michael<br class=""> <br class=""> </blockquote> <br class=""></span><div class="HOEnZb"><div class="h5"> ______________________________<wbr class="">_________________<br class=""> almighty-public mailing list<br class=""> <a href="mailto:almighty-public@redhat.com" target="_blank" class="">almighty-public@redhat.com</a><br class=""> <a href="https://www.redhat.com/mailman/listinfo/almighty-public" rel="noreferrer" target="_blank" class="">https://www.redhat.com/mailman<wbr class="">/listinfo/almighty-public</a><br class=""> </div></div></blockquote></div><br class=""><br clear="all" class=""><br class="">-- <br class=""><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr" class=""><div class="">Ranjith Reddy V.<br class=""></div>Agile Coach<br class=""></div></div> </div> _______________________________________________<br class="">almighty-public mailing list<br class=""><a href="mailto:almighty-public@redhat.com" class="">almighty-public@redhat.com</a><br class="">https://www.redhat.com/mailman/listinfo/almighty-public<br class=""></div></blockquote></div><br class=""></div></body></html>