Kevin: I have started tracking maintenance vs. new work in the Cirrus Sprint project[1] (which is a Kanban-style eternal sprint).
https://phabricator.wikimedia.org/tag/discovery-cirrus-sprint/
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | • JAufrecht | T99958 [EPIC] Five teams sample their maintenance fraction and two teams track it throughout the quarter | |||
| Resolved | • ksmith | T110551 Generate Discovery burnup and maintenance fraction charts | |||
| Resolved | • JAufrecht | T110705 refactor burnup SQL for consistency across different projects |
Event Timeline
Comment Actions
Note that none of the tasks have story point estimates, so any charts will have to be based on task counts.
Comment Actions
Kevin, Phlogiston is ready to tackle Discovery again. Which projects should I include?
Comment Actions
Also, I see a few stories with points and a lot with zero. Is there a default value I can assign to 0-point stories?
Comment Actions
@JAufrecht: The only Discovery project that has reliably been using story points is #search-and-discovery-research-and-data-sprint. There shouldn't be any/many 0-point stories there, but it would be interesting to know if there are. We aren't actually using the story points much, so I haven't paid close enough attention to them to know if there is a reasonable default value.
Comment Actions
Notes from review with Kevin:
Discovery Analysis is standalone, uses story points. Maps uses count, not points. cirrus uses count, not points. Lumping them together is unhelpful. Cirrus is doing maintenance fraction.
Comment Actions
To be clear, Maps-Sprint, Discovery-Search (Current work), and Discovery-Wikidata-Query-Service-Sprint are the other projects that could legitimately produce count-based charts. And it is Discovery-Search (Current work) that has been tracking maintenance fraction. Maps and WDQS are entirely new work, and Analysis was entirely new work for several months, but is just now starting to maintain the products they created this summer.
Comment Actions
New charts are being generated for four Discovery teams. Please review at http://phlogiston.wmflabs.org/ and let me know of any tweaks or fixes.
Comment Actions
Can you add maintenance fraction to the cirrus-sprint output?
Everything else looks reasonable, although obviously the story-point-based graphs are not very interesting for teams not reliably using story points. And the "milestones" aren't meaningful either, since they are based on workflow columns (to do, doing, needs review, done).
It will be interesting to have the various teams look at each others' charts and possibly ask "hey, that's a cool graph--what would it take for us to be able to get one like it?"
Comment Actions
Although a prettier chart would be helpful, this is done, and I have emailed the results to the Discovery and TPG teams.
By prettier, I'm specifically referring to having the bars somehow reflect the total scope of work completed that week, to distinguish between a 50% bar that represents 40 tasks next to a 100% bar representing a single task.