Phlogiston/Meeting Notes/2016-04-19-Roadmap

Last Meeting
https://www.mediawiki.org/wiki/Phlogiston/Meeting_Notes/2016-04-08-Roadmap
 * Type up and circulate meeting notes KL DONE


 * Schedule next 1/2 hour meeting JA DONE


 * Lay out possible outcomes KS T132366


 * Explore options for someone to help us do this research (e.g. in a product/market research capacity) (proposed) AWJR T132360


 * Enumerate possible customers for benefit evaluation (proposed) AWJR

Agenda

 * 1) Review action items from last meeting
 * 2) Lay out possible outcomes KS https://phabricator.wikimedia.org/T132366
 * 3) Done.  7 possibilities.  https://etherpad.wikimedia.org/p/Phlogiston_possible_outcomes
 * 4) Arthur: for option 7, could also get a non-WMF
 * 5) Joel: maybe useful to consider re-framing in terms of pilot vs production
 * 6) Joel: What else are we doing with this list?
 * 7) Kevin: identify next steps, things to research
 * 8) Joel: identify cost/benefit for all options
 * 9) Kristen: we already did this for some parts
 * 10) Explore options for someone to help us do this research (e.g. in a product/market research capacity) (proposed) AWJR T132360
 * 11) No progress - blocked by time, and not sure what they are.
 * 12) Kristen: plan was to figure out cost/benefit.  Did some cost; big work is to quantify the benefits.
 * 13) Is Phlogiston valuable to group heads for planning and evaluation?
 * 14) Is Phlogiston valuable to individual team heads for planning and evaluation?
 * 15) Arthur: so what's the task?
 * 16) Kristen: Find someone within WMF who might be good at this.
 * 17) Kevin: Find a way to make this happen.
 * 18) Kevin: quantify doesn't necessarily mean dollar benefit.  Could be, these X benefits to these Y teams is worth spending 0.5 FTE.
 * 19) Arthur: quantify benefits, and also costs?  No, just benefits.
 * 20) Enumerate possible customers for benefit evaluation (proposed) AWJR
 * 21) No progress - blocked by time, and not sure what they are.
 * 22) Kristen: This is, figure out who that marketing expert from the last question should talk to.
 * 23) Next steps on existing work:
 * 24) for Arthur's two items: meet again in a week.
 * 25) Kevin: want refinement pass on options.
 * 26) Joel: could try and fit in the pilot vs production model, and also, maybe sketch out some benefit areas for Arthur to consider.
 * 27) Kristen: after review is done, plug that into a spreadsheet.
 * 28) Notify TPG (but not required) Joel to make tracking tasks
 * 29) Should we start doing triage now?
 * 30) Could use some help triaging current incoming requests while Phate is lingering?
 * 31) Arthur: should we do that as part of team review?
 * 32) Joel: Triage Wednesday, Review Thursday?  Yes.
 * 33) Joel: helpful.  when I have customer attention, want to give turnaround faster than that.
 * 34) Kevin: seems odd (not necessarily bad) to make Joel's pilot, experimental project a TPG-wide thing
 * 35) Kristen: [...]
 * 36) Kevin: [...]
 * 37) Joel: #1 motivation is to help me catch things that are shiny but not necessary for where we are for pilot
 * 38) Arthur: Should we try and triage some current tasks tomorrow?
 * 39) Arthur: let's try doing some team-wide triage this week and see how it goes.
 * 40) Joel to find tasks that he is currently on the fence about and put in TPG for triage.

= Next steps: =
 * 2 arthur tasks
 * https://phabricator.wikimedia.org/T132360
 * Joel to make tracking tasks to invite TPG to review Kevin's work
 * https://phabricator.wikimedia.org/T132366
 * Joel to select Phlog tasks in TPG backlog for TPG triage
 * Joel to post notes