<div dir="ltr"><div class="gmail_default" style="font-family:georgia,serif">Trying image attachment again.<br><br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">I
didn't start out to be a naysayer though. I am really replying to to
share some team practices with the group based on experience with the
#Scap3
project.<br></blockquote></blockquote><div id="gmail-:10h" class="gmail-ii gmail-gt gmail-adP gmail-adO"><div id="gmail-:10b" class="gmail-a3s gmail-aXjCH gmail-m1598ed4e440ab0ea"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><span class="gmail-im"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div><div><br><a href="https://phabricator.wikimedia.org/project/board/1449/" target="_blank">https://phabricator.wikimedia.<wbr>org/project/board/1449/</a>
is the parent project. It could be a sub-project under our team project
but it's currently a top-level project. The top level workboard is
mostly for backlog and high-level categorization of the tasks. We have
created milestones that approximately correspond to quarterly goals.
When something moves from backlog it can go into a future milestone, the
current milestone or into the "debt" column for a future tech debt
sprint. Further prioritization and progress tracking happens within each
milestones' workboard:<br><br><a href="https://phabricator.wikimedia.org/project/subprojects/1449/" target="_blank">https://phabricator.wikimedia.<wbr>org/project/subprojects/1449/</a><br><br></div><div>We
still end up with epic tasks and the phabricator task graph helps with
those but I think milestones are nice for this sort of thing. Milestones
could represent any amount of work, not just quarterly goals, however,
the key advantage in keeping them small is that you can easily see
everything on one screen. So I would recommend scoping your milestones
so that they are limited to whatever you feel is a manageable set of
tasks that doesn't become overwhelming to look at.<br></div></div></div></div></div></blockquote></span><div><br><div style="font-family:georgia,serif;display:inline" class="gmail_default">There
may be two separate issues worth considering here: How we use epics or
other tools to groups bundles of tasks "tactically", at the range of
about 3 to 15 tasks, for daily management, and how we group tasks for
longer-term and bigger planning. Once we get beyond one screen-ful of
tasks, we need aggregate reporting to effectively track them.<br><br></div><div style="font-family:georgia,serif;display:inline" class="gmail_default">So, Milestones are good for looking at a countable number of tasks (~7 or less) as a group. For managing larger quantities of tasks, aggregate reports are essential. For example:<br><br><img src="cid:ii_iy1t7sup0_159ad885bb936dd0" width="478" height="269"><br></div><div style="font-family:georgia,serif;display:inline" class="gmail_default"><br></div></div></div></div></div></div></div></div></div>