GitLab Analyze:Product Analytics Team Meetings, 16 May 2023

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Product Analytics 16.2 Refinement/Planning Kickoff

Description

Walk through first thoughts on the Theme and Objectives for the 16.2 Milestone for Product Analytics.

A

Hey team I wanted to take a minute and talk through 16-2 Milestone plan and we just finished 6.0 we're just kicking out 16-1, never too early to start talking about the next Milestone, though today just talking about themes and objectives, though um so to uh as a reminder, our big theme for 16-1 is more customer feedback.

A

um So the objective there is getting upwards, the ability to add an existing visualization to a custom dashboard, so that would be enabling this customer dashboard the custom, dashboard creation, the visualization creation, um the designer for that and then being able to save a visualization and put it into a dashboard. So we have some to use. There I think we're missing a couple from the list, but we'll get this filled in and then on my side, collecting feedback from two or more customers, who've been on boarded.

A

So that's a big thing that, as infrastructure is wrapping up and we get those first customers on board collecting some feedback from them initial Impressions, what they're finding it they use that they set up, making sure that onboarding is really smooth, then into 16-2.

A

um The theme that I've set is get ready for beta. We do have a pretty short um phase for experiment, uh our exit criteria being five or six weeks after we get the first customer onboarded, um so it'll be a pretty quick uh iteration for us to get ready for beta, so the mouth of objectives.

A

um Some of these will have issues some won't uh collecting feedback from three more customers that we've onboarded, so our total targeted by customers in the experimental phase, five different companies, the projects that are collecting data and building dashboards or using the built-in dashboards. Getting that feedback um incorporating the feedback that we've received from the already onboarded customers. Until we receive some, we are not going to have issues, and so it might end up being a stretch for where this milestone and then infrastructure Readiness for beta.

A

uh Then, as and team, going to look to you to figure out what we need to do: From runberg perspective or changing Health charts or whatever. It is that we need to do to get the stack ready for beta and ensuring that we're good to go there uh on my side practicing and packaging Readiness.

A

Taking the data that we collect from the experiment as far as the event volume, what the costs are of the cluster, bringing that into a recommendation for the pricing team, how we think we should structure this uh for our customers and then for Kevin and I prototyping. The next two features um that we think we should go build to determine viability for the general availability release.

A

um Quick prototypes could be clickable prototypes could be just designs, but something that we can use to validate with a customer. Is this the thing that they value and then validate with engineering? Is that something that we think we can build? And how long is it going to take us to do that so that we can start to pick up the pace a little bit and creating more valuable features for the customer base? So that's what I'm, initially thinking for our theme and objectives, probably subject to change based on feedback.

A

um So you can leave me comments here in the 16-2 Milestone planning issue or send me a slack as a response to this video after I posted in the channel. Thanks.