Distinguishing between "maintenance" and "new" work seems very gray to me. Roughly as gray as "bug" vs. "improvement".
I guess a working definition for us right now might be: Either it's part of a project in the MPL, or it is "maintenance", or there's a reasonable chance you shouldn't be doing it. Kevin Smith Agile Coach Wikimedia Foundation *Imagine a world in which every single human being can freely share in the sum of all knowledge. That's our commitment. Help us make it a reality.* On Wed, Aug 5, 2015 at 12:10 PM, Greg Grossmeier <[email protected]> wrote: > Following on to Joel's message about "interrupt" work, I'd like to start > a thread on maintenance vs new work. > > Context: In the last round of quarterly reviews it was requested that > teams be prepared to give an idea of the proportion of work that falls > into "maintenance" vs "new work". > > Now, the hard part: what are the defining characteristics of those > options? How can we quickly lock at a task/bit of work and put it into > one of them? > > Are there any teams at WMF who already have these two buckets defined? > What are your definitions? > > Greg > > -- > | Greg Grossmeier GPG: B2FA 27B1 F7EB D327 6B8E | > | identi.ca: @greg A18D 1138 8E47 FAC8 1C7D | > > _______________________________________________ > teampractices mailing list > [email protected] > https://lists.wikimedia.org/mailman/listinfo/teampractices >
_______________________________________________ teampractices mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/teampractices
