<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta http-equiv="Content-Type" content="text/xhtml; charset=utf-8"> </head> <body> <div style="font-family:sans-serif"><div style="white-space:normal"> <p dir="auto">On 5 Aug 2016, at 17:39, Thomas Mäder 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">I just wonder how the approach scales to large projects. What do you do with bug reports that you can't get to right now...just abandon them? Way to value your customers that were nice enough to actually report a bug... </div></blockquote></div> <div style="white-space:normal"> <p dir="auto">Yeah, I've always struggled with how to handle bug reports in an "Agile process" - I think the answer lays in the article though: If noone is around to care about an issue, then it is better of being closed.</p> <p dir="auto">This does not mean you just abandon them, it means that if you care about your customers bugs then someone is triaging them and making sure they are on the backlog and in the plan for the coming sprints.</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">Part of the approach seems to be that the have a engineering tracker and then the "real" issue tracker somewhere on the side (left as an exercise...) </div></blockquote></div> <div style="white-space:normal"> <p dir="auto">Yeah, this is my takeaway too and it plays to my ideas of making it trivially easy for anyone (and I mean <em>anyone</em>, not just product managers) to be able to define one or more queries that can be used as "backlog" for a board (or other mechanism used to visualise work).</p> <p dir="auto">While at the same time making it an option to explicitly add issues to actually be on a board.</p> <p dir="auto">In model terms that is that unlike Jira where a query fetch all the items for a board (backlog and current progress) then we would have that for defining the backlog, but each issue will explicitly be linked to a board and possibly its column (column/state should be possible to calculate most of the time rather than manually set it). </p> <p dir="auto">This is a hybrid of trello's 100% manual adding and moving of boards and jiras all queried. I think this will give the best mix.</p> <p dir="auto">And it allow one to have boards that focus on different things - keeping them fairly clean, without resorting to deleting everything outside the developers mind set.</p> <p dir="auto">/max</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">/Thomas </div><div dir="auto"> </div><div dir="auto">Am 05.08.2016 um 16:10 schrieb Max Rydahl Andersen: </div><blockquote style="border-left:2px solid #777; color:#999; margin:0 0 5px; padding-left:5px; border-left-color:#999"><div dir="auto">Hey, </div><div dir="auto"> </div><div dir="auto">spotted this article today: <a href="http://blog.gitprime.com/a-priority-driven-model-for-issue-tracking/" style="color:#999">http://blog.gitprime.com/a-priority-driven-model-for-issue-tracking/</a> </div><div dir="auto"> </div><div dir="auto">Pretty interesting read and it captures one of the concerns I always have when I see the number of ideas, bugs, tasks etc. flowing into an planning tool or issue tracker - it will just overwhelm you if things are not nurtured. </div><div dir="auto"> </div><div dir="auto">In this they very aggressively say that anything not precise enough or too old gets removed from the engineering issue tracker. </div><div dir="auto"> </div><div dir="auto">This article nicely illustrate the importance of not cluttering your system - I do see that we need in almighty be careful about how we present the workitems and that we do not require a lot of process hell to keep it uptodate. </div><div dir="auto"> </div><div dir="auto">In PDD terms - might be that board views by default filter out higher level work items and just provide a link to them. Basic stuff like that. </div><div dir="auto"> </div><div dir="auto">/max </div><div dir="auto"><a href="http://about.me/maxandersen" style="color:#999">http://about.me/maxandersen</a> </div><div dir="auto"> </div><div dir="auto">_______________________________________________ </div><div dir="auto">almighty-public mailing list </div><div dir="auto">almighty-public@redhat.com </div><div dir="auto"><a href="https://www.redhat.com/mailman/listinfo/almighty-public" style="color:#999">https://www.redhat.com/mailman/listinfo/almighty-public</a> </div></blockquote><div dir="auto"> </div><div dir="auto">_______________________________________________ </div><div dir="auto">almighty-public mailing list </div><div dir="auto">almighty-public@redhat.com </div><div dir="auto"><a href="https://www.redhat.com/mailman/listinfo/almighty-public" style="color:#777">https://www.redhat.com/mailman/listinfo/almighty-public</a> </div></blockquote></div> <div style="white-space:normal"> <p dir="auto">/max<br> <a href="http://about.me/maxandersen" style="color:#3983C4">http://about.me/maxandersen</a></p> </div> </div> </body> </html>