<div dir="ltr">I threw it to Stack Overflow: <a href="http://pm.stackexchange.com/questions/15532/what-problems-can-be-diagnosed-from-a-scrum-cumulative-flow-burnup">http://pm.stackexchange.com/questions/15532/what-problems-can-be-diagnosed-from-a-scrum-cumulative-flow-burnup</a><br><br></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature"><div dir="ltr"><font color="#888888"><div><b>Joel Aufrecht<br></b></div><div>Team Practices Group<b><br></b></div><div>Wikimedia Foundation<br></div></font></div></div></div>
<br><div class="gmail_quote">On Thu, Jul 16, 2015 at 9:21 AM, David Strine <span dir="ltr"><<a href="mailto:dstrine@wikimedia.org" target="_blank">dstrine@wikimedia.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">This is pretty cool.<div><br></div><div>I think this will indirectly encourage detailed breakdowns within the sprint. If a team usually brings in large story point features they may look "in progress" for the majority of the sprint and then close, resulting in the hockey stick. </div><div><br></div><div>Textbook scrum would require a team to use hours inside the sprint and Story Points for long term planning. Phab isn't set up up for this. However, if we could use hours we would get much more granular detail. </div><div><br></div><div><br></div><div>How usable is this? How hard is it to switch when a new sprint begins? <br></div><div><br></div><div>Very cool stuff :)</div></div><div class="gmail_extra"><br><div class="gmail_quote"><div><div class="h5">On Wed, Jul 15, 2015 at 4:43 PM, Joel Aufrecht <span dir="ltr"><<a href="mailto:jaufrecht@wikimedia.org" target="_blank">jaufrecht@wikimedia.org</a>></span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5"><div dir="ltr"><div>Hi,<br><br>In anticipation of getting some burnup charts, I'm working on <a href="https://phabricator.wikimedia.org/T100708" target="_blank">Mock up burnup/CFD charts showing examples of different patterns and anti-patterns</a>. Here are the top two examples that came to mind; I am looking for feedback on these and for other examples of problems in a Scrum team that burnup charts can reveal.<br><br><img src="cid:ii_ic5etrnv0_14e941675399bea9" height="322" width="520"><br></div>This chart shows a bottleneck in QA. Developers are coding stories faster than the QA team can keep up, and so a bunch of In Testing stories pile up and overall Doneness lags. This could be because the QA team is short-handed, or because they don't have the tools to test efficiently. It could also show that testers are are sending things back with questions, but failing to change the state back to In Development.<br><div><img src="cid:ii_ic5etrol1_14e941675399bea9" height="322" width="520"><br></div><div>The hockey stick burnup shows a bunch of stories being completed in the last day of the sprint. Note also that In Development shoots up early. This probably suggests that the stories developers are working on are too big or too interdependent. QA seems to be keeping up, but I would be very skeptical that the stories passing testing in the last day really got the same quality of testing.<br></div><div><br></div><div>Do you have more examples like this, especially of patterns you have actually seen out in the wild?<span><font color="#888888"><br></font></span></div><span><font color="#888888"><div><br clear="all"><div><div><div><div dir="ltr"><font color="#888888"><div><b>Joel Aufrecht<br></b></div><div>Team Practices Group<b><br></b></div><div>Wikimedia Foundation<br></div></font></div></div></div>
</div></div></font></span></div>
<br></div></div>_______________________________________________<br>
teampractices mailing list<br>
<a href="mailto:teampractices@lists.wikimedia.org" target="_blank">teampractices@lists.wikimedia.org</a><br>
<a href="https://lists.wikimedia.org/mailman/listinfo/teampractices" rel="noreferrer" target="_blank">https://lists.wikimedia.org/mailman/listinfo/teampractices</a><br>
<br></blockquote></div><br></div>
<br>_______________________________________________<br>
teampractices mailing list<br>
<a href="mailto:teampractices@lists.wikimedia.org">teampractices@lists.wikimedia.org</a><br>
<a href="https://lists.wikimedia.org/mailman/listinfo/teampractices" rel="noreferrer" target="_blank">https://lists.wikimedia.org/mailman/listinfo/teampractices</a><br>
<br></blockquote></div><br></div>