Phlogiston/Meeting Notes/2016-04-08-Roadmap
tl;dr: Joel, Kevin, and Kristen met to sketch out steps that will allow us to make an informed decision about the fate of Phlogiston. We came up with the framework for a proposal, determined next steps, and will continue discussing at a follow-on half-hour meeting. The juicy details follow.
Meeting Metadata
editMeeting Description: Gathering of key Phlogistators past and present to discuss the steps to determine how to proceed with Phlogiston development.
Agenda:
- Intro/framing
- Discussion: How will we decide how to proceed with Phlogiston development?
- Draft proposal for how to get to a decision and determine timeline
- Review decisions made, next steps, and action items
Decisions to be made: Decide how we will decide to proceed with Phlogiston development
Decision rule: Consensual twinkle
Who needs to know?: TBD
Meeting highlights
editProposal for deciding:
- Lay out possible outcomes for the photo of Phlogiston
- Cost/Benefit Analysis:
- Quantify Benefits
- Is Phlogiston valuable to Group Heads (Product, Tech,...) for planning and evaluation?
- Is Phlogiston valuable for individual team planning and evaluation?
- Quantify Costs
- (for prototype to date): .33 TPG FTE (6-8 months), 1/10 of other support (devops, releng)
- (for stable product): .5 TPG FTE for 1 year, ? other support
- Quantify Benefits
- Timeline: before end of quarter, at latest
- Decision rule for deciding: TBD
Next Steps
edit- 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