Closed marcushyett-ph closed 2 years ago
In anticipation of the planning session tomorrow, I prepared this doc for Correlation Analysis on industry benchmarking. @neilkakkar & @marcushyett-ph in particular I think it's worth you checking it out.
I'm off today and might not make it to the sprint planning, so sharing thoughts in advance.
I basically agree with the proposed goals. However as they are above, in team core experience, Rick and Alex will most likely continue work on session recordings, leaving Paul, Michael and myself free to take up other issues.
For what these other issues should be, I have two three themes, that I'd like to divide between Paul, Michael and myself:
"Nail Fix Work In Progress Flags, Feature"
We have a few flags in active development:
correlation-analysis
new-paths-ui
new-paths-ui-edge-weights
6050-remove-sessions
And a few that have been pending for weeks:
6063-rename-filters
5733-funnel-vertical-breakdown
3408-saved-insights
5898-split-persons
hackathon-dive-dashboards
posthog-toolbar-feature-flags
5730-funnel-horizontal-ui
5440-multivariate-support
5720-plugins-ui-jobs
3638-trailing-wau-mau
A lot of these fall under core experience. I'd like to bring all of them over the line. This would make for a nice new release!
"Nail Trends"
"Nail API"
Just nail it already.
What does "Nail API" entail? @mariusandra
Feel free to edit if you have examples of API tasks that should get done.
I basically meant whatever is still needed to do so we can open multiple projects in different tabs, if anything. Then there's a thing with toolbar API access that's flakey (separate temporary_token
system, probably should replace with expiring personal API keys), we should do personal API key encryption, I'd be interested in stronger typings for API responses (mostly for insight queries I guess), and so on.
Quick retro from my perspective:
Retro:
Paths: released. Sitting tight waiting for users to flow through. We released to 50% of all users and got a few dozen visits the first day. Will continue to monitor follow up users. Goal is 5. What's paid and what's not paid?
Correlation analysis: MVP up along with property breakdowns. Been in testing. UI still needs work
Performance:
Group analytics:
Prioritized: Regex Replacement #6488
Data Integrity Querying - Eric Goal:?
Paths - Eric Goal: Get X more recurring users
Quantitative Analysis - Neil (Harry, Li) Goal: Get 3 users to LOVE correlation analysis
Group Analytics - Karl Goal: Group analytics MVP enabled for 5 alpha customers
TL;DR
Very good progress. Everything in is place for achieving: "Ensuring we can easily track and recover dropped events" and we also gained some good ground on other issues.
Highlights
We merged https://github.com/PostHog/posthog/pull/6193, https://github.com/PostHog/posthog/pull/6230, and https://github.com/PostHog/plugin-server/pull/596 is ready to deploy.
The final steps here are adding alerting for the dead letter queue size (the statsd metric already exists).
We also made progress on other fronts regarding data integrity. Most notably, we identified 2 more significant issues. One was inconsistent processing of event batches (fixed in #6230) and the other one is person rows being collapsed incorrectly in ClickHouse, leading to wrong cohorts (work on this has started, see https://github.com/PostHog/plugin-server/pull/597).
Finally, we also made progress on https://github.com/PostHog/plugin-server/issues/371. We merged https://github.com/PostHog/posthog/pull/6259 and the most important PR for this is coming tomorrow. https://github.com/PostHog/product-internal/pull/191 was also created.
What could have gone better
I personally ended up being pulled in a lot of different directions (demos, support, etc.). A lot of this was circumstantial, so not necessarily anything actionable here.
We also:
For the next sprint, there are 2 data integrity goals to consider:
In addition to the recordings goals above, team Core Experience has two more goals for this sprint:
Breakdown by multiple properties (Owner @pauldambra)
Nail Seamless Analytics Experience (Owner @Twixes)
Why? Insights and dashboards are very sluggish and inconsistent to use.
Steps:
Footnotes:
## Retro Rick - good to work on related yet separate things with Alex, didn’t conflict - speeding up session recordings: should have had a high level discussion and discuss priorities more before starting - improvement: breaking work down before doing it before doing it... - improvement: should have asked feedback from core analytics (e.g Karl with all the experience in building recordings) about how to do filters/queries/etc sooner in the process Alex: - planned too much work for the first week - a lot of things to do in the playback experience, many edge cases (e.g. adding a caching layer), still things to fix - improvement: higher level discussion on the strategy would help Michael: - off 1 week, did a lot of refactoring and bugfixes - wanted to get to the end of the projects api/frontend task - was good to talk through approaches today and figure out Chris: - still navigating being allocated between two teams Marius: - glad the team is functioning well and everyone was delivering ## Next sprint goals and prorities: Alex Rick - Session recordings - Why recordings are missing? @rcmarron has found interesting things... 10k/day. - distinct_id issue (merging recordings by person_id) - Playback experience 5 second goal - Custom seekbar with highlights, events, thumbnail previews?, etc. - Session recording list filter by cohorts and few other things to get parity with old solution Paul - Breakdown by multiple properties Michael Marius - “Make it so that when you go from a dashboard to an insight it loads in 0.1 seconds.. .and back the same way with also the same impressive speed” - Saved insights - Dashboards - IA beginnings - Settings page Chris - Do things
Global Sprint Planning
Retro: Status of Outcomes from Previous Sprint
Retro: What can we do better next sprint?
Focus on what went well and can improve for Quantitative Analysis? @neilkakkar @hazzadous @clarkus @EDsCODE @paolodamico feel free to update this comment in advance with your thoughts.
Sprint priorities
Plan: Proposed Goals for Next Sprint
Each goal should have a single owner. Owner can only be an engineer.
Team sprint planning
For your team sprint planning copy this template into a comment below for each team.