Talk:Team Practices Group/Measuring Types of Work

Categories A and B in "Maintenance vs New Work"
I am unclear about the current distinction between "Keeping the lights on" and "Maintenance". I am also unclear what the value would be in defining these as separate classifications. Khorn (WMF) (talk) 20:17, 17 August 2015 (UTC)

Maintenance vs New work - Uncategorized
A few comments of my own about this section
 * Prototyping/Research - I don't know that I have ever seen "prototyping" that wasn't new work. Research should probably be its own line: It can easily go either way, depending on what is being researched or analyzed.
 * Tech Debt - Definitely maintenance
 * responsive correction - What is this?
 * meta-work - I'm not sure what this is either.

Khorn (WMF) (talk) 20:22, 17 August 2015 (UTC)

Interrupt vs planned
I think the main characteristic of "Interrupt" is that it was a thing we didn't know we were going to have to address as an "unbreak now". Frequently, we are well aware of fragile components in the system (and have sparsely-worded cards about beefing them up in our backlog), but the rapid escalation in the severity of the problem is a surprise. On the other hand, they can also be complete surprises. The value in tracking interrupts is to be able to pad out planning estimations to account for work we didn't think we had to do deliberately at that time, whether or not those things were on the radar for a farther-off future. Khorn (WMF) (talk) 20:28, 17 August 2015 (UTC)

Tasks that indicate significant effort for several teams

 * Example?
 * Are there any big enough to matter?

Tracking tasks

 * Example?
 * Should be excluded from reporting

New Work - for projects in maintenance vs in development
Hello, this may already have been answered but I could not find it anywhere - for Category C type work, are we talking about new features being added to projects that have been completed and in maintenance mode or just things that are in progress? In Language Engineering, we have a clear distinction between projects that are in these 2 phases (e.g. ULS in maintenance, CX in development). Projects in maintenance have type AB work and C is mostly (at present) deferred in favour of all work for the in-development project. For the project in development too we have AB work as its in use as a beta tool. Considering all AB work can be identified with one tag, we would require some distinction for C in-maintenance and on going C for in-development projects. Thanks.--Runa Bhattacharjee (WMF) (talk) 18:05, 20 August 2015 (UTC)
 * Can you link a few specific tasks like this? JAufrecht (WMF) (talk) 18:31, 21 August 2015 (UTC)
 * C in-development would be everything on this board and a few things related to deployment needs. Examples of C in-maintenance are T104912 and T70077. Thanks. --Runa Bhattacharjee (WMF) (talk) 18:55, 21 August 2015 (UTC)

Re: "keep search ticking"
There seems to be some non-general leftover of some previous incarnation of this advice. --Nemo 07:50, 27 August 2015 (UTC)

Re: Endogenous vs Exogenous
I can't make sense of the sentence "Developers/Maintainers and Upstream_projects and who (if anyone) is tasked with fixing bugs in extensions/code that no existing team/individual is currently (officially) working on". Among other things, it lacks a main proposition. --Nemo 07:50, 27 August 2015 (UTC)

Phabricator projects
The decision at T109492 is quite noisy and certainly unreliable. Anyway, the descriptions of those projects refer to this page, which however doesn't seem to explain how to use them. --Nemo 07:50, 27 August 2015 (UTC)

Fwd: Add support for task types
How does all this relate to T93499: Add support for task types? --Nemo 07:55, 27 August 2015 (UTC)