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