Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sprint Feb 19 to March 1, 2024 #20328

Closed
mariusandra opened this issue Feb 14, 2024 · 9 comments
Closed

Sprint Feb 19 to March 1, 2024 #20328

mariusandra opened this issue Feb 14, 2024 · 9 comments
Labels
sprint Sprint planning

Comments

@mariusandra
Copy link
Collaborator

mariusandra commented Feb 14, 2024

Global Sprint Planning

3 things that might take us down

  1. Ted running a PG migration (posted in #dev)
  2. DNS - Terraform all of cloudflare -- already on the list

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 mariusandra added the sprint Sprint planning label Feb 14, 2024
@mariusandra mariusandra pinned this issue Feb 14, 2024
@mariusandra
Copy link
Collaborator Author

mariusandra commented Feb 14, 2024

Team Product Analytics

Support hero:

  • Tom

Retro

  • 👍 HogQL rewrite
    • ✅ Lifecycle - out
    • ✅ Retention - out
    • ✅ Stickiness - out (this is new)
    • 🔲 Trends - being thoroughly tested, hope to wrap up this week
    • 🟦 Funnels - started, strong progress
    • 🟦 Paths - waiting for funnels for last bit
  • 😍 HogQL Autocomplete
  • 😍 Django 4.1

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.

Next sprint

  • @Gilbert09
    • Support
    • Linking external data warehouse tables with joins
  • @thmsobrmlr
  • @mariusandra
    • HogQL trends and persons (if still todo)
    • Follow up on type system changes
    • Better JSON handling in HogQL
    • Filters refactor (move the frontend to queries-only)
  • @Twixes
    • Copying dashboards between projects
    • Performance optimisations into HogQL
  • @webjunkie
    • Async queries (celery autoscaling?)
    • Django 4.2 upgrade
    • API docs (get them into posthog.com)
    • Support rollover
    • Debounced filters in the UI

@robbie-c
Copy link
Member

robbie-c commented Feb 14, 2024

Team Web Analytics

Last sprint

  • Added path cleaning
  • Fixed mobile layout (note web analytics traffic is 2% mobile, compared to 3% ac
  • Open queries as a new insight or modal
  • Added a concurrency limit to queries

Hang over items from previous sprint

  • Still thinking a lot about performance and architecture

OKR

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

High priority

  • Performance and architecture
  • Add ability to separate sites (e.g. Sites scene or saved filters)

Low priority

  • polish and be responsive to support

@pauldambra
Copy link
Member

pauldambra commented Feb 14, 2024

Team Replay-i

Support hero: David

Retro

  • stuff carried on without me which is a good signal @pauldambra
  • risk of blob incidents worrying when on call @marandaneto
  • CH knowledge still not widely spread (in this team) @daibhin

Hang over items from previous sprint

  • 🟡 RN recordings - we know what we need to do after spiking @marandaneto
  • 🟡 using embeddings/clustering to generate session summaries @daibhin @pauldambra
  • ✅ mobile dashboards @pauldambra @marandaneto
  • ✅ mobile recording documentation @marandaneto
  • ✅ we started iOS recording so we can pull from larger tester pool @marandaneto
  • 🟡 2 more tester/user for android replay
    • Inarix started Android testers - lots of good feedback
    • we're going to double down on finding apps we can test ourselves to try and ramp up the feedback cycle
  • 🟡 do we release comments/discussion @daibhin
    • 15ish people enabled it but not really using it
    • we want to follow-up with folk that turned this on in feature preview
  • ✅ buffering/loading/performance @pauldambra

OKR

  1. OKR, status (red/yellow/green) and action points if yellow/red
  • 🟡📱 happy android replay users
    • had feedback from 3 beta testers
    • 1 elected to keep it switched on
    • still looking for sweet spot between capturing right info and setting expectations
  • 🟡 people love replay even more
    • still more bug reports than we'd like
    • canvas replay is out
    • some rrweb bugs patched directly
  • 🟡 first class mobile support
    • not focussed here, focus is on replay
    • but making small pieces of progress
    • continuing to crank out improvements & features to mobile SDKs

High priority

  • iOS session replay have first captured recording @marandaneto
  • 5 Open Source Android apps tested with android replay @pauldambra
  • get "show similar recordings" out for our team @daibhin @pauldambra
    • start generating clusters from recording embeddings for our team
    • figure out the UI for how to surface this to folk
    • measure performance needs of crunching all of this data

Low priority / side quests

  • contribute the network capture back to rrweb - so they don't make one that doesn't work for us - @pauldambra
  • network payload capture on onboarding? @pauldambra
  • adding billing limits to unsubscribe? @pauldambra
  • how much embedding/clustering can we do just with session recording metadata (when can we avoid Open AI) @daibhin

@benjackwhite
Copy link
Contributor

benjackwhite commented Feb 14, 2024

Team Infra

Support hero: @frankh

Hang over items from previous sprint

  1. 🟡 Keep rolling out the new ingestion ingresses with client-side support @frankh
  • Lots of small edge case issues still taking time to investigate
  • JS is ready to go with new endpoints - just needs testing it
  • Goal is to do that rollout and then only use Cloudflare for assets (direct to NLB otherwise)
  1. 🟡 Move the final work into charts (posthog in particular) @danielxnj
  • Almost there but caused an incident 😱 due to unforeseen way that helmfile works
  1. ✅ Zero downtime kafka rollover for EU

OKR

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

High priority

  1. Finalise charts movement and get Argo CD canary deploys working @danielxnj
  • Make web the focus (capture as next target)
  1. Rollout all clients to new capture endpoints @frankh
  • And keep on top of remaining edge cases

Low priority / side quests

@benjackwhite
Copy link
Contributor

benjackwhite commented Feb 14, 2024

Team CDP

Hang over items from previous sprint

  • ✅ Detour to sort out Django security and personal api keys
  • 🟡 Support swapping from "memory" to "cookie" storage in JS

High priority

  • Finish the CDP RFC roadmap
  • Support Robbie with scaling Web Analytics
  • Sites or Saved Filters for Web Analytics (influences CDP sources work)
  • PoC out the alternative $person ingestion work

@neilkakkar
Copy link
Collaborator

neilkakkar commented Feb 14, 2024

Team Feature Success

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

Retro

  • Experiments UI create & view overhaul - @jurajmajerik -> pushed into next sprint, taking longer to sort out designs. Instead working on allowing N experiments pre-subscription.
  • Fix control is never significant in experiments - @jurajmajerik -> done
  • Survey results are squished fix; delayed surveys; nicer results loading screens; more results filtering in surveys - @liyiy -> delayed surveys will roll over, rest getting done. Preact refactor 90% there.
  • Statistical significance on secondary metrics & display secondary metrics charts - @neilkakkar -> done
  • Refactor FeatureFlagReleaseConditions to work well with scheduled changes, surveys, and flags - @neilkakkar -> in progress, will roll over a day or two, higher priority to decide billing issues

Hang over items from previous sprint


OKRs

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

High priority

Low priority / side quests

@EDsCODE
Copy link
Member

EDsCODE commented Feb 14, 2024

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

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

Infra

  • Debug & fix incremental backing up of large tables (to be deployed)
  • Correct number of backups for sharded vs non-sharded tables (to be deployed)
  • Ansible configs for existing clusters
  • Ansible configs for new clusters

High priority

Product

  • @EDsCODE data warehouse data in trends
  • @Gilbert09 View/table linking precursor to linking data warehouse data to person models

Infra
@fuziontech is out for 1/2 of next sprint

  • Adapt current Ansible playbooks to new cluster configs starting with Coordinator
  • TF Coordinator and have at least 2 running behind a load balancer

@raquelmsmith
Copy link
Member

raquelmsmith commented Feb 14, 2024

Team Growth

Retro

Retro items Lots of things in progress / left over ### High priority - [x] Make new celery queue for usage reports - [ ] Full testing of the onboarding flow @raquelmsmith - partially done - [x] Fix mrr per product for credit-based annual customers - @raquelmsmith https://github.com/PostHog/billing/pull/461 - [x] Feature flag to turn off quota limiting during billing migrations @xrdt - Basically done https://github.com//pull/19996 - [ ] Don't drop data for 7 (or maybe 3) days until after it's done - needs a relaunch - [ ] Onboarding reskin based on Cory's mocks @xrdt - in progress - [ ] Teams plan @raquelmsmith - in progress - [ ] 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 - [ ] Overlap in billing gauge projected / current / billing limit lines. https://posthoghelp.zendesk.com/agent/tickets/10070

OKR

  • 🟡 Improve 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

  • Product intro experiment is doing poorly! @raquelmsmith
  • Full testing of the onboarding flow @raquelmsmith - partially done
  • Don't drop data for 7 (or maybe 3) days until after it's done
  • Onboarding reskin based on Cory's mocks @xrdt - in progress
    • config screen
    • products screen
  • Teams plan @raquelmsmith - in progress
  • 21M events free plan @raquelmsmith - in progress
  • Rethink some activation metrics (remove team member invited, double check rates with diff activities) @raquelmsmith - in progress
  • Come up with 5 ideas to bump the session replay activation rate @raquelmsmith @xrdt

Low priority / side quests

  • Write two articles for Andy

@tiina303
Copy link
Contributor

tiina303 commented Feb 14, 2024

Team Pipeline

Off: Xavier (1 week)
Support: Tomas & Brett

Retro

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)
    • re-prioritise once Xavier is back from vacation
  • ResearchGate on capture-rs (Brett)
  • PoE: Write path for the new distinctId->PersonId overrides (Ted)
    • overflowing to next sprint

Low priority / side quests

  • Pipeline UI: wrap up deployment (Tiina)
    • overflowing to next sprint
  • HogQL batch exports events filtering, for remaining destinations (Tomas)
    • backend side all done, UI not done will be done only in 3000
  • CDP: prototype the WASM sidecar executor (TBD)
    • reprioritisation - this will be in Q2
  • Rust monorepo (Brett)

OKR

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

  • ✅ Wrapped up Webhooks Delivery system - Brett
  • ✅ Wrapped up capture-rs posthog-js rollout - Xavier
  • 🟢 Wrapped up New Pipeline UI - Tiina
  • 🟢 Wrapped up PoE (with backfills and squashes) - Ted
  • 🟢 Volume spikes on session reply do not hurt other users - Xavier
  • 🟢 Person property updates don't slow down ingestion - Brett
  • 🟢 Requested data deletion is complete and reliably executed going forward - Tiina

High priority

  • PoE: Write path for the new distinctId->PersonId overrides - Ted
  • Backfill implemented and verified for teams with large number of distinct IDs - Ted
  • Ran squash for a single team - Tomas
  • Batch Export for cloud to cloud migrations - Brett
  • pipeline UI available for beta testers - Tiina

Low priority / side quests

  • Person property updates don't slow down ingestion - Brett
  • backfill topic incident follow-ups - Tiina

@marandaneto marandaneto unpinned this issue Mar 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
sprint Sprint planning
Projects
None yet
Development

No branches or pull requests

9 participants