Sprint Feb 5 to Feb 16, 2024

[mariusandra]

Global Sprint Planning

3 things that might take us down

1. Django (sync) can only take a certain number of concurrent requests. 150 should be enough for anyone? We should upgrade.

Team sprint planning

For your team sprint planning copy this template into a comment below for each team.

# Team ___

**Support hero:** ___

## Retro

<!-- Grab the high and low priority items from last time and add whether that item was completed or not -->

- 

## Hang over items from previous sprint

<!-- For each item, decide to re-prioritise (and add below) or deprioritise -->

- Item 1. prioritised/deprioritise

## OKR

1. OKR, status (red/yellow/green) and action points if yellow/red


### High priority

-

### Low priority / side quests

-

[mariusandra]

Team Product Analytics

Support hero:

• Julian

Retro

• 👍 HogQL rewrite (get trends, stickiness, lifecycle, retention out) @Gilbert09 @webjunkie @mariusandra
  • ✅ Lifecycle - out
  • ✅ Retention - out
  • 🔲 Stickiness - might be out by now?
  • 🔲 Trends - largely finished, needs thorough testing
  • 🟦 Paths - mostly finished, waiting for funnels for last bit
  • 🟦 Funnels - started
• 👍 Start funnels @thmsobrmlr
• 👍 Support our users @Twixes
• 😶 Django upgrade
• 👍 Multiple celery consumers

OKR Q1 2024

1. HogQL & Data Exploration (Julian, Marius)

   • Convert ALL our insights to use HogQL as their base. ongoing
   • Improve the type system and get rid of assumeNotNull.
   • Write great docs for HogQL and data exploration nodes. ongoing
   • Proactively monitor query performance.

2. Product Analytics frontend (Thomas, Michael)

   • Clean things up now that we have PostHog 3000 and HogQL everywhere. ongoing
   • Work on the universal "Explore" view. ongoing

3. BI (Tom)

   • Support non-event data sources on HogQL insights.
   • Build the new querying experience, and/or integrate it into the "Explore" view.

Action plan

- Come January, we'll take [this list](https://github.com/PostHog/meta/issues/130), split the checkboxes between the team, and keep going till it's done. ETA: end of January. - In February (leap year, woohoo), we'll make Product Analytics ~great~ spark joy again: insights UI cleanup, unified data exploration experience, adding missing analysis features (lifecycle breakdowns, etc), and in parallel work on the BI and the HogQL editing experience. What _exactly_ we'll do and in what order is still TBD. - In March we'll keep going. The goal is to have an amazing BI / Product Analytics / Insights / Explore / HogQL experience by the end of it.

Next sprint

High priority

Rough first draft. To be discussed at standup.

• HogQL insights rewrite
  • trends - @Twixes
  • paths, funnels - @thmsobrmlr
• HogQL features & BI
  • autocomplete - @Gilbert09
  • type system, JSON support - @mariusandra

Low priority / side quests

• Django upgrade - @webjunkie

[robbie-c]

Team Web Analytics

Last sprint

• spiked sampling in web analytics, but sampling is in beta due to bad methodology (uses distinct_id rather than e.g. person_id so gives wrong results), can't use it.
• turn on a FF for us so that queries run in series rather than in parallel (enforced client-side), please lmk if you see any related weirdness

Hang over items from previous sprint

• Performance work

OKR

1. Finish the beta to-do list
2. Find 5 high-ICP reference customers

High priority

• Performance - discussions around architectural ways we can speed up queries (e.g. https://github.com/PostHog/product-internal/pull/559 or change sample key of events table to person_id.

Low priority

• Other performance work
  • stare at queries more
• sites scene Create a new "My Sites" scene #12181
• polish and be responsive to support

[pauldambra]

Team Replay

Support hero: @pauldambra

everybody is in almost the whole sprint 🚀 (@pauldambra is off one afternoon to ferry children around the countryside searching for healthy teeth)

## Retro

• still pretty hard to get feedback on session recording on android... only really had feedback from two or three that have volunteered @marandaneto
• grabbing example apps and testing it there ourselves - @pauldambra
• canvas stuff is super exciting @pauldambra
• should we open source it already @marandaneto

Hang over items from previous sprint

✅ network payload capture released for all @pauldambra
🟡 2 users using Android replay @marandaneto (we did get two testers)
✅ BETA canvas recording for replay @daibhin
🟡 AI session summary @pauldambra
✅ (Wrap up comments work) - @benjackwhite and @daibhin needs some follow-up.
✅ POC of session replay with jetpack compose @marandaneto (can't do wireframe for jetpack compose)
✅ @daibhin take over this PR to add resizeable inspector tab for the player #18378
🟡 initial POC/discovery on React Native recordings - complicated, started, but slow going

OKR

• 🟡📱 happy android replay users
  • feedback from beta testers but not a working recording from them yet 😓
• 🟡 people love replay even more
  • still more bug reports than we'd like
• 🟡 ish first class mobile support
  • not focussed here, focus is on replay
  • but making small pieces of progress
  • fixing code snippets - better RN and flutter support

High priority

• using embeddings/clustering to generate session summaries @daibhin @pauldambra
  • generating clusters
  • naming them
  • not aiming to productise but validate that we can generate magic playlists
• start iOS recording so we can pull from larger tester pool @marandaneto
• 2 more Android testers @pauldambra @marandaneto

Side quests

• contribute the network capture back to rrweb - so they don't make one that doesn't work for us - @pauldambra
• do we release comments/discussion @daibhin
• POC RN recordings @marandaneto
• ✅ mobile recording documentation update @marandaneto @pauldambra
• ✅ OMG mobile dashboards @pauldambra (@marandaneto)
• buffering/loading/performance @pauldambra

from growth review

• network payload capture on onboarding?
• adding billing limits to unsubsscribe?

[benjackwhite]

Team Infra

Support hero: @danielxnj

Retro

Hang over items from previous sprint

1. SOC2 compliance work mostly done
2. Amazon procurement stuff
3. Rollout new ingestion endpoints and static asset accessing @frankh

• ✅ Most of the legwork is done here - now its just about carefully rolling out

1. Scoped investigation into async django to relieve the concurrent requests issue @frankh @benjackwhite

• ❌ no progress here
• Could be that django upgrades help us here so lets focus on reliable canary deploys

1. Scoped investigation into Soc2 (type I or II) with Fraser @danielxnj

• ✅ mostly done now
• In addition Amazon procurement process stuff

1. Test out one of our Canary Deploy ideas

• ✅ Tested gradual rollouts on dev using Contour / Argo

OKR

1. 💪 Deploy with confidence
2. 💰 Keep costs under control
3. 👀 More Observability
4. 🎯 Soc2

High priority

1. Keep rolling out the new ingestion ingresses with client-side support @frankh @benjackwhite

• why? It is delicate and almost there - let's focus on getting it done

3. Move the final work into charts (posthog in particular) @danielxnj

• why? This is chore work but blocks some of the canary deployments and is still a lot of mental overhead.

Low priority / side quests

• Get changed CH deployment work into Terraform @danielxnj

[raquelmsmith]

Team Growth

Retro

Retro items

• We shouldn’t show pricing above $20k/yr on the pricing pages so we don’t “shoot ourselves in the foot” for larger customers who will be paying above that - @xrdt
  • Could be an experiment, does it put people off from signing up because it isn’t as transparent, or feels enterprise-y.
• Make doc for how to create the right kinds of prices in Stripe @raquelmsmith
• Experiment: redirect people to web analytics after onboarding instead of insights screen - @xrdt
• Hide replay controls for people on the old plan - @xrdt
• New product intro pages - feat(growth): [WIP] Product intro UI #19609 - @raquelmsmith
• Wrap up finished experiments - remove code, close experiment @xrdt
  • invite members https://us.posthog.com/project/2/experiments/8176
  • post-ingestion redirect to insights https://us.posthog.com/project/2/experiments/8865
• Product intro pages @raquelmsmith

OKR

• 🟡 Double activation rates for product analytics and session replay
  • ⚪ Polish onboarding flow with Cory
  • 🟡 Run 1 experiment per week
  • 🟡 Do an average of 2 customer interviews per week
• ⚪ Launch pricing for Data warehouse, queries, CDP

This sprint

High priority

• Make new celery queue for usage reports
• Full testing of the onboarding flow @raquelmsmith - snapshots done, e2e pending
• Fix mrr per product for credit-based annual customers - @raquelmsmith
• Feature flag to turn off quota limiting during billing migrations @xrdt
  • Basically done feat: use feature flag to control whether to quota limit or not #19996
• Don't drop data for 7 (or maybe 3) days until after it's done
• Start onboarding reskin based on Cory's mocks @xrdt
• Launch Teams plan @raquelmsmith
• Come up with 5 ideas to bump the session replay activation rate @raquelmsmith
• Rethink some activation metrics (remove team member invited, double check rates with diff activities) @raquelmsmith - in progress

Low priority / side quests

• Write two articles for Andy
• Expired sessions should redirect users to the login page rather than popping lots of error toasts.

Growth review items

• Add metadata to startup plan customers in stripe @raquelmsmith

[EDsCODE]

Team Data Warehouse

OKR Q1 2024

Objective

Get EU moved over to new cluster

• Key Results:
  • Terraform, ansible, data migrated over, backups, housewatch
  • Deprecate old cluster

ByConity evaluation

• Key Results:
  • Load up with all clickhouse data and benchmark

5 reference customers with qualities:

• Key Results:
  • Paying a reasonable amount
  • Tell us they’re delighted
  • Not a big edge case
  • Using our in house data import pipeline
  • Weekly queries on a data warehouse connected table
  • Saving queried tables to insights?

Data Warehouse queries are compatible with insights hogQL

Retro

Product

• postgres integration
• Side tracked with looking into flaky data import jobs due to dropped postgres connection
• data warehouse table as first class data in insights

Infra Board

• Ensure non-sharded backups backup only once - Add is_sharded bool to the configs so that we can only backup one shard if not sharded HouseWatch#61
• Finish upgrade to 23.11
• Rebuild coordinator to exactly match EU boxes due to replication warnings
• Finish incremental backing up of large tables
• Ansible configs for all EU CH nodes. Core, Coordinator, ZK

High priority

Product

• stop flaky jobs
• test postgres integration live
• experiment with adding imported data to persons table

Infra

• Debug incremental backing up of large tables
• TF configs for all EU CH nodes. Core, Coordinator, ZK
• Ansible configs for all EU CH nodes. Core, Coordinator, ZK

[xvello]

Team Pipeline

• Support: Marcus, secondaries: Xavier & Tiina

Retro

• Offsite (Tiina)
  • RFC for the future of Person Model -> We have short-term improvements queued up and continuing the discussion for V2
  • Written plan for Blobby
• Webhooks delivery system running idle in US and EU cloud (Brett, Xavier)
• PoE: Write path for the new distinctId->PersonId overrides (Ted) -> delayed due to offsite and handling splits, discussing in https://github.com/PostHog/product-internal/pull/557
• HogQL batch exports events filtering (Tomas) -> ready for one destination

Hang over items from previous sprint

• PoE: Write path for the new distinctId->PersonId overrides (Ted)

OKR 🟢 🔴 🟡 ⚪

• 🟡 Wrap up Q4 work before offsite in Jan
  • 🟡 Finish webhooks
    • 🟡 Delivery system (Brett, Tomás)
    • 🟡 Pipeline UI, apps hookup (Tiina)
    • Lots of progress was made for both, but not finished
  • 🟡 Finish POE (Ted)
    • Lots of progress, but not finished. Plan has been updated for a simpler solution
  • 🟢 Finish capture-rs (Xavier)
    • backends depend on infra ingress work planned for Q1
• 🟡 Person model doesn't slow down the pipeline + doesn't live in shared PG (Tiina)
• ⚪ Joint goal with replay team to get blobby stable (Tiina)
  • ⚪ Determine demarc lines of ownership (API layer) going forward
  • ⚪ Make our part stable

High priority

• Ramp up webhook delivery from plugin-server (goal 100% of teams), some apps will need to be rewritten to benefit from it (Brett)
• Overflow logic rework with locality: deploy on analytics, stretch goal for blobby (Xavier)
• ResearchGate on capture-rs (Brett)
• PoE: Write path for the new distinctId->PersonId overrides (Ted)

Low priority / side quests

• Pipeline UI: wrap up deployment (Tiina)
• HogQL batch exports events filtering, for remaining destinations (Tomas)
• CDP: prototype the WASM sidecar executor (TBD)
• Rust monorepo (Brett)

[neilkakkar]

Team Feature Success

Support hero: @liyiy (surveys) + @jurajmajerik
Days off:
Juraj: 2 days
Neil: 1 days
Li: 1 days

Retro

• e2e tests for experiments - @jurajmajerik - basic e2e tests there, will expand when we add more functionality & work on existing functionality again
• Experiment bug fixes, common sense boundaries for predictions, update predictions after updating metrics - @jurajmajerik -> some fixes & validation for events is in, common sense boundaries deferred till after UI revamp which will change a lot of this now.
• Statistical significance on secondary metrics & display secondary metrics charts - @neilkakkar -> Will roll over, rolling out relative date ops took longer than expected, some decide errors with cloudflare, focusing on fixing that first.
• Finish converting surveys to preact, and use it for previews in posthog app - @liyiy -> conversion will get done! Previews to follow after things are merged
• Start on event based targeting implementation (RFC here: https://github.com/PostHog/product-internal/pull/556/ )- @liyiy - will roll

Hang over items from previous sprint

---

OKRs

1. Doubling down on surveys
2. Doubling down on experiments

High priority

• Experiments UI create & view overhaul - @jurajmajerik
• Fix control is never significant in experiments - @jurajmajerik
• Survey results are squished fix; delayed surveys; nicer results loading screens; more results filtering in surveys - @liyiy
• Statistical significance on secondary metrics & display secondary metrics charts - @neilkakkar
• Refactor FeatureFlagReleaseConditions to work well with scheduled changes, surveys, and flags - @neilkakkar

Low priority / side quests

• Temporal queues for feature success - @neilkakkar

---

We'll do - Event based triggers for surveys (RFC here: https://github.com/PostHog/product-internal/pull/556/ )- @liyiy - after this sprint.