12.3 Fulfillment Planning
SSOT for 12.3 priorities: Fulfillment board
Please add your holiday dates below for the 12.3 release period and don't forget to add to the Fulfillment calendar!
- Tim: None
- James: 12-22 August
- Tyler: None
- Vitaly: None
- Ammar: 12-08-2019 -> 14-08-2019
Feature Functionality and Improvements
- Design Discovery: Automatically bill for newly added group members on GitLab.com - this is currently in UX's camp, but the focus for UX here is primarily to understand what is required around messaging and understanding the possible impact this may have on our customers. I'm hoping we could handle the implementation for this in 12.3 as well as the UX work. @rdavila already has a good grasp on what needs to be done on the backend side of things here and has completed some of the work already.
- Potential follow on MVC's from the discovery work completed in 12.2 in this issue.
- I anticipate that this will slip, so this will continue to be a big priority in 12.3.
Why are these important?
Fulfillment is responsible for our customers very first experiences with GitLab. It is vital that we prioritise fixing our trial and purchase flows in order to reduce dropout and churn and increase customer happiness and adoption. In addition, we are currently missing out on millions of dollars in revenue due to the fact that we are not automatically billing (actually not billing them at all) our users on GitLab.com who have gone over their initial purchased user count.
We now have our second Product Designer - @esybrant! Along with the aforementioned Product Discovery issue around automated billing, we (Product & Design) will spend time working through this process to start creating and grooming a backlog of work that aligns with our vision as a group, ready for the rest of the team to work on.
Technical Debt 🧳
There should be space in this plan for things to slip from %12.2 (link) but it's too early to say right now what they might be other than the trial improvements.