Meeting Notes/2015-12-29 Reading Web Phlogiston

Adam, Bryan, Joel, Jon

What does Reading web want in terms of dashboards and metrics?
Jon: Not clear what we want from burnups, progress, etc. Hoping to start visualizing what's possible. I'm interested in how I can translate the existing Phabricator dashboard into this tool. https://phabricator.wikimedia.org/dashboard/manage/125/

See the relative effort we are investing for the different goals. When we do sprints we don't always finish everything. We estimate stories but at the end of the sprint maybe not everything is done, but also the sense we were distracted by other things; want to see where the effort is going. would be good to be able explain what happened.

Adam: Echoing what Jon said. don't want to do too complex of things; want to understand the burn rate. Understand what work we ought to be committing to. Some sense of core and maintenance versus new and strategic. The part I'm less clear on is, how sophisticated our input needs to be in order to track work for specific goals.

Jon: looked at prototype Phlogiston, the categories don't quite make sense so would like to fix that in this meeting if we can.

Bryan: Very broad scope of work, tied into very many things. would like at some point to make that manageable. Adding projects, deleting projects, filtering, e.g. "we want things in this project tracked but not if they are in that project". Those will become important questions down the road, though not at the initial kickoff.

Review Phlogiston Reading Web charts as-is
3) Review what Phlogiston can provide (burnups, progress vs milestones, maintenance fraction, velocity backcasts & completion forecasts)

4) Review what to consider changing in Reading Web Phabricator & Phlogiston config