Sprint - Apr 15 to Apr 26, 2024

[pauldambra]

Global Sprint Planning

3 things that might take us down

1. 2. 3.

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

-

[pauldambra]

Team (funny)Re(name)play

Support hero: Manoel

• Paul - out for a few days (I don't remember why for a couple so might cancel them 🤣)
• Manoel 2 days at a conference

Retro

• are we getting someone to triage/1st-line our support questions? (should be but we don't know when... we think plan is for Steven to onboard and get settled first) @marandaneto
• good to see Xavier working on blobby changes
• David and Paul are going to concentrate on getting to a "good stopped" state so the next sprint can be focussed on HogQL filtering for replay

items from previous sprint

High priority

• 🟡 @pauldambra is writing up an error tracking RFC so we're ready to rock and roll
  • 🍝 Paul is building heatmaps 3000 with Ben
    • https://github.com/PostHog/posthog/issues/21099
    • we've got a plan and have started the typing ⌨️
  • we've got a backlog of nits and improvements to Android replay getting ready for advertised open beta
  • we've got a heavy support backlog
  • ✅ so we're starting the quarter with a :fix all the things: sprint
  • some excellent css-in-jss fangling from @daibhin
  • @marandaneto working through the bugs from the last round of replay testing
  • support queue is down from 23 to 16 issues

OKR

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

• 🟡 quality and consolidation
  • mobile replay open beta
  • replay captures every site
  • people can find the valuable recordings
• 🟡 Error tracking MVP
• 🟡 Hire 2 amazing colleagues
  • 1 interview and 3 super days this week 🫠

High priority

• add an optional screenshot capture option to Android replay for people that want to trade performance for fidelity @marandaneto
• make usage report changes for mobile replay @pauldambra
• UX improvements https://github.com/PostHog/posthog/issues/21302#issuecomment-2045882184 @daibhin

Low priority / side quests

• persistent replay queue in posthog-js @pauldambra
• [x] Ben's data loading refactor https://github.com/PostHog/posthog/pull/20632 @daibhin
• [ ] playlist logic refactor @daibhin (unlocks ephemeral playlists)

[Twixes]

Team Pro(fessional)duct Analytics

Support hero: @mariusandra

Retro

• Thomas: Support & Rolling out HogQL-based insights & HogQL support ✅
• Michael: Project environments & support rollover Support ✅
• Julian: Legacy logic/filter cleanup, improve dashboard logic & reloads. ➡️ Async querying and smaller improvements
• Tom: HogQL & Data Warehouse. Type system? ✅

Hang over items from previous sprint

• Roll out HogQL-based Paths (time scale depends on whether we find compatibility issue)
• Reworking dashboardLogic

OKR

• HogQL-based querying

  • Convert the remaining legacy queries to HogQL and release to public (Thomas, Julian, Marius)
  • 🟢 Insights – will be done this sprint with the rollout of Paths
  • ⚪ Cohorts 👈 some time later
  • Remove legacy querying backend (Thomas, Julian)
  • 🟠 Clean up or rewrite dashboardLogic 👈 this sprint
  • ⚪ Convert filters to query (insights, notebooks, activity log, experiments)
  • Missing Product Analytics features (Thomas, Julian)
  • ⚪ Breakdowns (multiple) in literally everything
  • ⚪ Make a list based on GitHub issues from customer requests…
  • Missing HogQL features (Tom, Marius)
  • 🟠 Type system, JSON 👈 Data Warehouse is on this
  • ⚪ Missing things when building funnels

• Querying and processing performance (Thomas, Julian)

  • Global performance overview dashboards
  • ⚪ Insights
  • ⚪ Exports
  • ⚪ Cohort recalculations
  • Query request tracing
  • ⚪ Possibly query runner Python optimizations
  • ⚪ Exports improvements
  • ⚪ Identify top 5 query optimizations in terms of impact

• Artificial Hog / Post Intelligence (Michael)

  • ⚪ Ask a question to get a magical insight (aware of your taxonomy)
  • ⚪ Figure out infra for upgrading queries and models
  • ⚪ Product-wide framework for opting into sharing with OpenAI

• Activation (side quest: Michael)

  • ⚪ Michael to work with Growth to identify optimizations to getting started with Product Analytics

High priority

• Marius: Support
• Michael: Project environments
• Julian: Dashboard logic rework
• Tom: Effectively Data Warehouse

Low priority / side quests

• Start converting filters to query, probably for Julian

[neilkakkar]

Team Feature Success

Support hero: @neilkakkar
Days off: Juraj: 1 days Neil: 1 days

Retro

• Collect feedback on the new Experiments UI from our top users - @jurajmajerik -> survey is out, some good feedback already, most people love it! Will potentially do some individual reaching out next sprint.
• Continue improving Experiments UI - @jurajmajerik
  • no results empty state: show checklist for what events are missing. Explore button in the middle of empty state. ✅
  • banners for what to do next - ✅
  • data collection participants bug - set default to 20% for happy path, 50% for edges - no, will rollover.
  • Tooltips (stretch)
  • link to docs (stretch)
  • investigate MAI calculator (stretch)
• Add property filters [and exact date matching] to event matching in cohorts - @neilkakkar -> ✅
• Find a good flow for restricting users to exposed users in secondary metrics for experiments - @neilkakkar -> 🔄
• RFC for feature flags rewrite - @neilkakkar -> ✅

Hang over items from previous sprint

---

OKRs

1. Make sure feature flags can handle 10x current scale
2. Polish new experiments UI & collect feedback
3. Add most requested surveys functionality

High priority

• Write RFC for Surveys branching logic, create wireframes, and talk to YC & RG - @jurajmajerik
• Get the surveys preview fix over the line https://github.com/PostHog/posthog/pull/20321 - @jurajmajerik
• Data collection participants bug - set default to 20% for happy path, 50% for edges - @jurajmajerik
• Explore experiment metrics easily in insights - @neilkakkar
• Learn Rust, and minimal PoC of new feature flags service - @neilkakkar

Low priority / side quests

• Fix some Surveys bugs: one, two - @jurajmajerik
• Temporal queues for feature success - @neilkakkar
• Setup instrumentation for flip-flopping problem of experiment significance - @neilkakkar

[tiina303]

Team Pipeline

Off: Support: Ted

Retro

High priority

• [x] Person processing add-on phase 1 (Brett)
• [ ] PoE: Helping out with HogQL migration (Ted)
• [ ] Pipeline UI (Tiina)
  • good progress, but lots of distractions with planning and person processing add-on

OKR

✅=finished 🟢=on track to finish this quarter 🟡=might not finish 🔴=won't finish

WIP we're still doing the planning this week.

High priority

• [ ] Person processing add-on phase 2 (Brett)
• [ ] Batch exports metrics, logs and notification improvements for users (Tomas)
• [ ] Pipeline UI (Tiina)
• [ ] capture-rs mirrors the /batch traffic (without writing to Kafka) and its error rate matches the python version (Xavier)

Low priority / side quests

• [ ] Changing what data pipeline add-on covers (Tiina)

[danielxnj]

Team Infra

Support hero: @danielxnj

Hang over items from previous sprint

1. 🟢 Spontaneous look into AZ aware routing to try and reduce our biggest cost centre
   • We are stuck because Aurora only provides one AZ endpoint for the writer instance so we can not remove the cross AZ traffic.
2. 🔴 Purchase reserved RDS instances @frankh
   • why? Risk vs cost works out - to be fully confirmed with pipeline team
3. 🟡 Get app onto Canary deploys now that we are on contour @danielxnj
   • app.dev is on argo rollouts (not actually canarying but deploying correctly)
4. 🔴 Test out capture-rs traffic with contour @frankh
   • Had enough ingress issues the last week or so that we took a pause here
5. 🟡 Get flagged PoC for proper permissions out @benjackwhite
   • So close - just tests to finalise to get merged.
6. 🟢 Add OOM and restart alerting for all deployments @danielxnj

OKR

1. 💪 Deploy with confidence 🟡
   • Finalize our Canary Deploy process 🟡
   • Support rust capture to full release using traffic shaping
2. 🚨 Improved alerting and monitoring
3. 🔒 Deeper Security
4. 💰 Continued cost control
5. 🖖 Splitting up the monolith

High priority

1. Secret management tooling
   • why? All secrets are leaked in the pods @danielxnj
2. Interviews. @benjackwhite
3. Canary roll out to every deployment @frankh
4. Work with Xavier and the pipeline team on traffic mirroring using contour @frankh

Low priority / side quests

• Improve Kafka alerting

[robbie-c]

Team Web Analytics

Support hero: n/a

Retro

High priority

• [x] personless events posthog-js changes
  • ready for first set of users
• [ ] personless events UI problem solving whack-a-mole
  • ongoing
• [x] Write more docs for web analytics (e.g. what is a Channel Type?) and add more tooltips to web analytics

Low priority

• [ ] Session filters for all posthog events
  • WIP
• [ ] Add session properties to the property definition endpoint
  • WIP

Hang over items from previous sprint

• personless events UI problem solving whack-a-mole
• Session filters for all posthog events
• Add session properties to the property definition endpoint

OKR

⚪ Make querying fast enough for large customers ⚪ Do personless events work where necessary (unknown amount of work) ⚪ Iterate on customer feedback ⚪ Product management work

High priority

• personless events UI problem solving whack-a-mole

Low priority / side quests

• Session filters for all posthog events
• Add session properties to the property definition endpoint

[EDsCODE]

Team Data Shack

OKR Q2 2024

Objective

Release data warehouse to everyone

• Key Results:
  • Integration first experience
    • schemas are reliable
    • modeling of each integration is clear
    • Good automatic roll up views and joins
    • Wizard to onboard people
  • Establish a solid pattern to build integrations
  • Complete data warehouse experience in the rest of the app (insights, feature flags, experiments)

James as a Service -> Clickhouse as a Service

• Key Results:
  • Better Visibility
    • Regularly testing backups
    • Monitoring/alerting
    • Mutations
    • Moves
  • Management
    • Managing/killing mutations
  • Self Serve
    • Schema design feedback (James non blocking
    • Schema management
  • Automation
    • Replace/Upgrade replicas
    • Upgrading to 24.04
    • Disk configs

Retro

Product

• [x] @EDsCODE High/medium priority fixes suggested by @annikaschmid here https://github.com/PostHog/posthog/issues/21105
• [ ] @EDsCODE release data warehouse on trends. This is mostly implemented. Need to make sure everything is working after some of the schema issues that we've been fixing
• [ ] Awaiting hogql release for data warehouse on experiments
• [ ] @Gilbert09 property typings for data warehouse tables (for autocomplete)
• [x] @Gilbert09 zendesk integration v0.2. Support more granular sync selections when first setting up
• [x] **WIP new onboarding wizard and sync pattern

Infra Big outage last week that disrupted work on the last two here

• [x] Add new way to delete data using a join table instead of inline in query (thanks @timgl)
• [ ] Pulumi integration with housewatch -> make sure that when we recreate instances, the volumes are deterministic
• [ ] Mutation visibility in housewatch

High priority

Product

• [ ] @EDsCODE WIP property typing system for hogQL. This has been a struggle with internal and external usage where unknown types have caused errors so worth working through
• [ ] @EDsCODE multiple joins in a query and multiple level views
• [ ] Figure out Incremental syncs
• [ ] @Gilbert09 finish onboarding wizard. Will give new users a solid understanding of how to take advantage of the data warehouse capabilities in posthog

Infra

• [ ] 🧑‍🔬 Pulumi + CH testing for new cluster
• [ ] 🔍 Investigate why we are having data drift between replicas and have plan to fix when it happens

[raquelmsmith]

Team Growth

Retro

Retro items

- [x] Team offsite! ### High priority - @raquelmsmith - [x] Support billing for person processing addon - this took up all of my time - [x] Support addon features for paygate mini - [x] [feat: point people to contact sales for enterprise from pricing page](https://github.com/PostHog/posthog.com/pull/8164) - [ ] Dashboard creation from onboarding - [ ] Feature gating for activity panel - Migrate customers - [ ] Feature gating for automatic provisioning - Migrate customers - @xrdt - [ ] Session replay pricing change plan: in progress, see below for details - @zlwaterfield - [x] RFC for simpler upgrading - comments done, starting work on it - [x] Move the Growth 2.0 dashboard to a Notebook and finish it the charts we have data for - https://us.posthog.com/project/2/notebooks/mw9VwBA0 - [ ] Helping Ian improve Next.js documentation - found proxy error and created issue with next https://github.com/vercel/next.js/issues/63948, no documentation changes yet - [x] Continue email verification investigation - rates here have lowered, shipped verification support modal - [ ] Review / test Michael’s dark mode PR: https://github.com/PostHog/posthog/pull/21149 - no movement here - [x] Looking at some recurring Sentry bugs (e.g https://github.com/PostHog/billing/pull/499) - logs of bugs fixed and number of errors it much lower

OKR

✅=finished 🟡=in progress 🔴=won't finish ⚪=haven't started

1. ⚪ Create a flow in product analytics onboarding to fill out a dashboard template using actions (Raquel)
2. 🟡 Simplify our subscription flows (Zach, supported by Raquel)
3. Launch pricing changes (Bianca, Raquel)
   • 🟡 Personless events - will help us reach more customers at an affordable price
   • Data warehouse - it's becoming pretty useful, we should charge for it
   • Session replay - we can reduce costs to improve retention and reach more people

This sprint

• @raquelmsmith
  • [ ] Support billing for person processing addon - get it to a launch-able spot this week. See https://github.com/PostHog/billing/issues/504 for status and tasks
  • [ ] Feature gating for activity panel
    • Migrate customers
  • [ ] Feature gating for automatic provisioning
    • Migrate customers
• @xrdt
  • [ ] Session replay pricing change plan:
    • [ ] Legacy paid customers all get controls
    • [x] New prices PR up
    • [ ] Working with Annika to nail down migration strategy
    • [ ] Continuing to look into snags I ran into last time with compare_prices script
  • [ ] Invoice syncing and revenue issues
    • [ ] Revenue drop over weekend
    • [ ] We seem to lose invoices when billing cycles roll over
    • [ ] Sentry error about type → id
  • [ ] Move customer <> (stripe_customer_id, stripe_sub_id) to a One to Many relationship, pr in progress
• @zlwaterfield
  • [ ] Billing changes - auto-subscribing users to all products (starting with new users)
  • [x] Plan the pricing/plan/product structural changes - how do we convey plans vs products?
  • [x] Spend time improving annual/credit Stripe webhooks - these are almost all of the Sentry errors left
  • [x] Update Slack message for growth dashboard
  • [x] Follow up on Next.js proxy issue with Vercel and update Next.js documentation for a note on the reverse proxy bug
  • Metrics to watch:
    • How many organizations sign up without a name: https://us.posthog.com/project/2/insights/SmImt4r7 (see if this is an indicator of lower chance to subscribe to paid plan)
    • Sign up benefits - generic, vs product analytics focused vs logos: https://us.posthog.com/project/2/experiments/24738
    • Email verification support tickets https://us.posthog.com/project/2/experiments/26053