<div dir="ltr"><div><div><div>We're still trying to flesh out a full set of use cases for the whole thing (work planning?), which is probably impossible since it's a huge topic, but without explicit use cases we keep falling back to logical data design and then getting stuck in the maze. Let's start:<br></div><ol><li>Individual team members want to know what they should work on next</li><li>Product managers want to identify potential work in the near future</li><ol><li>from team goals</li><li>from foundation goals</li><li>from call to action or any other expressions of priority<br></li><li>from community requests</li><li>from other inputs<br></li></ol><li>Product managers want to estimate, break down, and prioritize potential work<br></li><li>Product managers want to know what work they have already planned</li><li>pretty much everybody wants to know when particular things (tasks, goals) will be done</li><li>Bug reporters want to know the status of bugs they have reported<br></li><li>More generally, stakeholders want to know the status (estimate, priority, expected completion date) of work they care about</li><li>Product managers want to compare their teams' actual output to the planned output or goals</li></ol><p>Does this include what you want to accomplish with goals? Can you add to this list?<br></p></div>Side note: we probably want to keep Epics and Goals distinct. We're working on a baseline vocabulary for the whole Foundation. The direction I think we want to go (no consensus on this yet) is that Task/Story is a completable piece of work; Epic is a theoretically completable piece of work that's more than (very roughly, will vary by team) a few person-weeks; Goal/Milestone Criterion/Key Result is a target that you compare to a project's current state to decide what Epics or Stories to create or implement next.<br><br></div><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 Wed, Jul 1, 2015 at 10:06 AM, Max Binder <span dir="ltr"><<a href="mailto:mbinder@wikimedia.org" target="_blank">mbinder@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"><div><div><div><div>Hey Dan,<br><br></div>This has been an ongoing and as yet unresolved point of discussion with some teams. There are concerns about goals-as-epics, from a long-term process perspective, as well as overwhelming Phab with proprietary tags (a problem that Bugzilla apparently suffered). Andre, Joel A, Kevin S, Kristen, and I all chatted at some point about this on #wikimedia-teampractices. While I can't say we found ultimate resolution, we did decide that the simplest thing to do would be to use the Epic project Tag, and apply it to goals-as-epics "tasks."<br><br></div>Another thing to consider is Phab's "Goal" category. Joel and the VE team are apparently going to experiment with that.<br><br></div>I wish I could better explain where we landed, but I am still wrapping my head around it. Maybe one of the others could illuminate the issues more clearly than I?<span class="HOEnZb"><font color="#888888"><br><br></font></span></div><span class="HOEnZb"><font color="#888888">Max<br></font></span></div><div class="gmail_extra"><br><div class="gmail_quote"><span class="">On Wed, Jul 1, 2015 at 9:49 AM, Dan Garry <span dir="ltr"><<a href="mailto:dgarry@wikimedia.org" target="_blank">dgarry@wikimedia.org</a>></span> wrote:<br></span><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>I'm creating epics to track the <a href="https://www.mediawiki.org/wiki/Wikimedia_Engineering/2015-16_Q1_Goals#Discovery" target="_blank">Discovery Department Q1 2015-16 goals</a>, and thought it might be useful to track organisation-wide progress towards achieving their quarterly goals by having such epics have tagging them as Q1 2015-16 goals.<br></div><div><br></div><div>The epic tag already exists, but I would consider quarterly goals to be a strict subset of epics: all quarterly goals are epics, but not all epics are quarterly goals.</div><div><br></div><div>Thoughts?</div><span><font color="#888888"><div><br>Dan</div><div><div><br></div>-- <br><div><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr">Dan Garry<div><span style="font-size:small">Product Manager, </span><span style="font-size:small">Discovery</span></div><div>Wikimedia Foundation</div></div></div></div></div></div></div></div>
</div></font></span></div>
<br></div></div><span class="">_______________________________________________<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></span></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>