Team Practices Group/Measuring Types of Work

Category A
"Keeping the lights On"

Something essential will fail immediately (days? hours?) if this work is not done.

Category B
"Maintenance"

anything which keep search ticking, but doesn't related directly to our goals

Something essential will fail or degrade fairly soon (weeks? months?), or will cost much more to fix later, if this work is not done now.

Category C
"Investment/New Projects"

Functionality that is not currently available.

Can a team be their own customer? If a team delivers functionality to themselves, to make their own work easier/cheaper/better, is that category C, or B?

So this includes *all* new features, even if they are relatively minor tweaks to existing functional areas?

Uncategorized
Prototyping/Research

Tech Debt

responsive correction

meta-work

Category A
Supporting others

https://www.mediawiki.org/wiki/Developers/Maintainers and https://www.mediawiki.org/wiki/Upstream_projects and who (if anyone) is tasked with fixing bugs in extensions/code that no existing team/individual is currently (officially) working on.

Category B
Internal to team goals

Interrupt vs planned
For a Scrum team, would this just be "This work was added after we had locked in our tasks for this sprint", or would it also include "We have known about this for months but is is not part of our main thrust"?

Category A
most strategic in terms of achieving our mission

Category B
Not Strategic. Shouldn't be doing it.

=== Lila's Buckets for infrastructure teams ===

VisualEditor
All tasks in one big Phab project. "Tranche 0" projectcolumn contains all of Category A, most of Category B, but makes no distinction between A and B. Category C is accurately tracked (as the sum of everything else).

Discovery
Discovery has not yet had internal needs to distinguish these categories, so it would be difficult to measure any of them without tweaking our processes. We are open to tracking what needs to be tracked, although obviously would prefer to avoid heavy burdens in doing so.

17 Aug 2015 meeting
Meeting Goals 1) Figure out how to meet request for teams to report on maintenance fraction 1a) Clear standards across groups

2) Figure out what teams want to measure for their own use

3) Make sure we know how to proceed 3a) clarify vs other dimensions

Discussion Why is Terry asking for the three categories? - WMF-level planning - Katie: you want to do this to justify your hiring needs. - David: Can also use this [ongoing maintenance cost] to justify sunsetting things.

Why is Lila asking for her categories, which are slightly different? - maybe Lila wants some of this to figure out if a team belongs in which section? - Lila's categories in the notes are specific feedback to one team or role, not everybody

Is this all Engineering, or all Foundation?

What should we call Maintenance vs New Work, as opposed to the other possible dimensions? - Proposed: Maintenance Fraction.

Can we differentiate between A and B? - Greg - no - Katie - sort of - sort of have AB/Interrupt and AB/Non-Interrupt - B is debt - Does anyone have a rule for differentiating A from B that could work for most teams? - no

Is there stuff that is inward-facing that belongs to C? - no?

Does C include prototyping new things, researching existing things? -We probably have a lot of edge cases and maybe should do card sorting or other offline activity to get our collective judgment in sync

New dimension: - Does this fulfill a quarterly goal or not?

Proposed definition: - C is work that produces functionality that a non-foundation person would see/use. - This doesn't work for teams with no external customers. Those teams can try counting other Foundation teams as their Category C customers.

How are we measuring? - We will create a new tag to track this. - Some teams are mostly AB or mostly C. to make it easier, they can tag just AB or just C, and assume all other tasks are the other category. - Joel can create custom reports on other queryable factors (VE uses projectcolumn already)

Next Steps: - Joel: confirm definition (and check with Terry) - All: Send suggestions for names for tag AB and tag C. - Joel: continue/initiate email discussion on other categories - continue in email (inc. mailing list) until and unless another forum becomes better - All: Send edge case examples to Joel - how to measure followup discussion

Open Questions
Forthcoming