Page MenuHomePhabricator

Update iOS burnup project list to make it accurate and useful
Closed, ResolvedPublic8 Estimated Story Points

Description

Followup from T108280: Create Mobile burnups:

okay, do I have this right? List of projects that contain iOS tasks is:

project_list = Wikipedia-iOS-App-Product-Backlog,Wikipedia-iOS-App-Development

List of distinct categories of work is:

Bug Backlog
Engineering Backlog
Product Backlog

The other categories are actually states, not orthogonal categories of work/goals? Those would be useful in a cycle time chart, but Phlogiston isn't currently doing those.

You can see the Phlogiston settings at https://github.com/wikimedia/phlogiston/blob/master/ios_source.py and https://github.com/wikimedia/phlogiston/blob/master/ios_recategorization.csv.

Event Timeline

JAufrecht assigned this task to MBinder_WMF.
JAufrecht raised the priority of this task from to Needs Triage.
JAufrecht updated the task description. (Show Details)
JAufrecht subscribed.

Yes, those 2 projects have the iOS work (there are other random boards here and there for quarterly goals, but the 2 are the main flow).

Yes, those are the distinct backlogs, but I can imagine a scenario in which something skips straight from "Needs Triage" to a column that is not an "official" backlog. I'm not sure how to remedy that, beyond insisting to the team that triage is a distinct step that happens before analyzing work ("Needs Acceptance Criteria," "Needs Design," "Needs Estimation," etc.

Writing up Friday discussion: those columns address status information. Currently Phlogiston only cares about Status Field = Open or Resolved; it ignores other Status Field values and cannot use status information in columns. (Cycle Time charts would, but currently none are implemented, and even then the other charts still wouldn't.)

Phlogiston wants to see different milestones/goals. So we identified three other iOS Phabricator boards/projects as more suited: iOS-5-app-alpha
iOS-5-app-beta
iOS-5-app-production

See also https://github.com/wikimedia/phlogiston/blob/master/ios_recategorization.csv for configuration details.
The burnup charts are now based on this information: http://phlogiston.wmflabs.org/ios.html

Responded to JAufrecht by email.

MBinder_WMF lowered the priority of this task from High to Medium.Dec 9 2015, 7:40 PM
MBinder_WMF edited projects, added Team-Practices (This-Week); removed Team-Practices.
MBinder_WMF moved this task from To Do to Needs Review on the Team-Practices (This-Week) board.

Next step, reach out to Josh (iOS PO) on how we can leverage Phlogiston.

Next step: Joel and Max to meet and review.

iOS will be parenting tasks as tagging the grandparents as milestones via the Mobile-App-Goals board

JAufrecht set the point value for this task to 8.Mar 10 2016, 6:53 PM

@JAufrecht I think it is from the original task perspective. The iOS team will likely be switching from parenting to tagging soon.

MBinder_WMF subscribed.

@JAufrecht do we want to keep this task open as the iOS team transitions to tracking project tags (rather than parenting), or shall we set up a new task for that (assuming we need one)?

I think new task. Nobody wins when tasks stay open forever, except BIG PHAB.

If this is moot for now, let's close this and open a new one if necessary in the future.