[teampractices] How do teams track work not related to goals?

Mon Aug 17 17:01:12 UTC 2015

VE puts all of this into the Interrupt bucket.  So all work that is
proposed for VE is either
1) rejected
2) put into the general backlog, which in practical terms is the same thing
3) put into an ordered Tranche corresponding to a milestone coming up in
the next 3-6 months
4) Put into the interrupt bucket, which is maybe 30-50% of all work for VE

*--Joel Aufrecht*
Team Practices Group
Wikimedia Foundation

On Mon, Aug 17, 2015 at 9:43 AM, Kevin Smith <ksmith at wikimedia.org> wrote:

> Within the foundation, each team identifies one or a handful of quarterly
> goals, which become the focus of the team. However, there is always going
> to be important work that doesn't fit into a goal. Either there were
> already too many goals in place, or there is one main goal but 10 ongoing
> projects, or maybe this other work is too small to justify being a goal,
> but too important to let slip.
>
> So the question I was asked was: How do other teams track these non-goal
> important work items? Obviously the tasks themselves can be tracked in
> phab, but do they get rolled up anywhere? How do teams ensure that they
> continue to be worked on, despite not being one of the main goals?
>
>
> Kevin Smith
> Agile Coach, Wikimedia Foundation
>
>
> _______________________________________________
> teampractices mailing list
> teampractices at lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/teampractices
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.wikimedia.org/pipermail/teampractices/attachments/20150817/d9147a45/attachment.html>