Page MenuHomePhabricator

Set up Phlogiston for Analytics
Closed, ResolvedPublic

Description

notes from review: Analytics has inconsistent backlog names. Wouldn't be useful for Research or Design Research; Analytics has a weird kanban situation, is going through some changes - ask again in a week. No maint fraction data.

Event Timeline

JAufrecht claimed this task.
JAufrecht raised the priority of this task from to Needs Triage.
JAufrecht updated the task description. (Show Details)
JAufrecht added a project: Phlogiston.

Grace: we use only Analytics-Backlog, Analytics-Kanban, Analytics-Cluster (in that precedence order).
Maybe Analytics-Dashiki and Analytics-Engineering and Analytics; Grace to check with Kevin.

ggellerman added a subscriber: Milimetric.

+ @Milimetric , + @kevinator

  1. re-assigning to @kevinator
  2. see email from me to internal-analytics list, "Maintenance fraction follow up"

Joel to turn on Phlogiston for listed projects so team can review and react instead of working in a vacuum.

Preliminary charts are now available at http://phlogiston.wmflabs.org/an.html
Things that are easily adjustable:

  • the list of Phabricator projects included
  • how the categories are concatenated from "Project Projectcolumn"
  • sort order

I take a bit of exception to "so team can review and react instead of working in a vacuum". We have been tracking our velocity and reacting to it for a long time now (years). We've changed the way we track things to better suit our team and make everyone happy, and we all really enjoy working within our current process. We're always happy to improve but I don't love it when we're characterized as "working in a vacuum". If there's any perception of vacuousness, perhaps we should work cross-team at Scrum of Scrums to eliminate that perception.

I beg your pardon - I wrote poorly. I meant a vacuum about Phlogiston, not about burnups. I turned on the Analytics Phlogiston report so you could see how Phlogiston works, how it renders Phabricator projects, what reports it calculates, etc, and then decide what projects should be included, how they should be summarized and sorted, how to handle unpointed stories, and what date cutoffs to use.

Thanks @JAufrecht, it was interesting to take a look at Phlogiston. We'll have to take a deeper look as a team during one of our retros or staff meetings.

Discussed in Nov 12 TPG team meeting.

Phlogiston is set up, so we will open a new task if there are any follow on tasks.