Page MenuHomePhabricator

Cycle time for a task entering a column to resolution, with support for wildcards
Open, LowPublic20 Story Points

Description

iOS uses release boards, a la iOS-app-v5.3.0-Welsh-Dragon . The final column is "Ready for PM Signoff". We would like to track how long it takes a task to be resolved once it enters that column. The tracking would have to accept wildcards just like any other tracking in the recat file, but also recognize that the column is always the same name.

Not a high priority.

Event Timeline

Restricted Application added a subscriber: Aklapper. · View Herald TranscriptOct 20 2016, 10:55 PM
JAufrecht renamed this task from Phlogiston: Request -- Cycle time for a task entering a column to resolution, with support for wildcards to Cycle time for a task entering a column to resolution, with support for wildcards.Oct 26 2016, 5:44 PM
JAufrecht triaged this task as Low priority.
JAufrecht added a project: Team-Practices.

@MBinder_WMF What is the priority for this? What other activities is it blocking?

I am interested in this for teams who are interested in a kanban approach. But not sure I would call it high priority...

JAufrecht moved this task from To Be Triaged to Reporting on the Phlogiston board.Oct 26 2016, 6:17 PM
JAufrecht edited projects, added Phlogiston (Reporting); removed Phlogiston.

What Kristen said. The main thing that Phab does not do well when it comes to kanban is cycle time.

There are varying levels of scope here. In order:

  1. Build a cycle time report that works for just this project, with custom cycle steps
  2. Try to genericize the cycle time report steps, so that it works for this project but is a starting point for future projects.

Cost:

  • We will have to build the report more or less from scratch, including data definition, data storage, chart definition, and workflow
  • This will apply only to this specific Phabricator project; other Phabricator projects will need their own column setup to document steps in the cycle (copying from this example or inventing their own), and Phlogiston will need some way to define them.

Benefit:

  • direct berefit to the team asking for it
  • Having a live example of this report could help other teams understand its benefits
  • Should be much cheaper to replicate this report for other projects

Build a cycle time report that works for just this project, with custom cycle steps

This would work as an experiment, but is not sustainable for a team (such as iOS) that frequently changes release boards.

Try to genericize the cycle time report steps, so that it works for this project but is a starting point for future projects.

This is preferable, so that a team like iOS could have the same column on each of their release/sprint boards and have it automatically picked up by Phlog (the way wildcards pick up the new boards themselves).

Per monthly grooming, removing this from Team-Practices knowing that it can be found on the Phlogiston board. @JAufrecht please adjust this action as need (and kindly describe your reasoning for keeping it on Team-Practices if you do restore it to that board).

JAufrecht set the point value for this task to 20.Dec 12 2016, 8:31 PM
JMinor removed a subscriber: JMinor.Jul 27 2018, 6:53 PM
JAufrecht removed JAufrecht as the assignee of this task.Jul 27 2018, 11:26 PM