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 - Jan 22 to Feb 2, 2024 #19804

Closed
mariusandra opened this issue Jan 17, 2024 · 8 comments
Closed

Sprint - Jan 22 to Feb 2, 2024 #19804

mariusandra opened this issue Jan 17, 2024 · 8 comments
Labels
sprint Sprint planning

Comments

@mariusandra
Copy link
Collaborator

mariusandra commented Jan 17, 2024

Global Sprint Planning

3 things that might take us down

  1. Celery
  2. Tim skiing
  3. CH/infra being on fire while people are offline, sick and/or leave the company
  4. Accidentally dropping data for billing migrations and with billing limits

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 Jan 17, 2024
@mariusandra
Copy link
Collaborator Author

mariusandra commented Jan 17, 2024

Team Product Analytics

Support hero:

  • Michael

Retro

  • HogQL insights rewrite
    • All started, ongoing or close-to-completion... except for Funnels
  • Support backlog
    • Still a hog
  • Helping Pipeline with their new UI
    • There's a new UI (flagged)
  • Helping Pipeline with getting people off the last apps.
  • Pydantic update for OpenAPI

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.
    • Work on the universal "Explore" view.
  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

Low priority / side quests

  • Django upgrade
  • Multiple celery consumers
  • Overall Quality Of Life improvements

@mariusandra mariusandra pinned this issue Jan 17, 2024
@pauldambra
Copy link
Member

pauldambra commented Jan 17, 2024

Team Replay
Support hero: @marandaneto (@pauldambra supporting)

everybody is in the whole sprint 🚀

## Retro

Hang over items from previous sprint

  • ✅ make sure the plans and controls change lands well with users @pauldambra
    • quite a lot of load from people wanting ingestion controls on old plan, but conversion to paid is roughly the same
  • ✅ 2 users using and have given us feedback on Android replay
    • several users, not massive feedback yet, but getting there
  • ✅ mobile dashboard template released
    • PR waiting to land and then we can review and release this

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

High priority

Side quests

@robbie-c
Copy link
Member

robbie-c commented Jan 17, 2024

Team Web Analytics

Hang over items from previous sprint

  • n/a

OKR

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

High priority

  • Performance - spike of sampling in web analytics

Low priority

@benjackwhite
Copy link
Contributor

Team Infra

Support hero: @frankh then @danielxnj

Retro

Hang over items from previous sprint

  1. New endpoints for ingestion / static assets
  • Still in progress due to Cloudflare trickiness
  1. Celery worker deployment
  2. Testing of Contour / Envoy for ingress routing
  3. IaC for Clickhouse EU

OKR

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

High priority

  1. Rollout new ingestion endpoints and static asset accessing @frankh
  2. Scoped investigation into async django to relieve the concurrent requests issue @frankh @benjackwhite
  3. Scoped investigation into Soc2 (type I or II) with Fraser @danielxnj

Low priority / side quests

  • Test out one of our Canary Deploy ideas
  • RFC for the reverse proxy as a service @benjackwhite

@raquelmsmith
Copy link
Member

raquelmsmith commented Jan 17, 2024

Team Growth

Retro

Retro items

OKR

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

This sprint

High priority

Low priority / side quests

Growth review items

  • Add metadata to startup plan customers in stripe @raquelmsmith
  • 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

@EDsCODE
Copy link
Member

EDsCODE commented Jan 17, 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

  • onboard more users to data connectors + release hubspot integration to interested users
  • tree view interface
  • continue working through conversion from billing queries on metabase to within PostHog

Infra Board

  • Setup coordinator node for Clickhouse
  • Move a customer to this for performance feedback
  • Begin Terraforming coordinator
  • Upgrade cluster to 23.11 from 23.6

High priority

Product

  • postgres integration
  • data warehouse table as first class data in insights

Infra Board

  • Ensure non-sharded backups backup only once
  • Finish incremental backing up of large tables
  • Ansible configs for all EU CH nodes. Core, Coordinator, ZK

@neilkakkar
Copy link
Collaborator

Team Feature Success

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

Retro

Hang over items from previous sprint


OKRs

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

High priority

Low priority / side quests

@tiina303
Copy link
Contributor

Team Pipeline

  • Offsite 22-26. Jan
  • OOO: Tiina 29-31. Jan
  • Support: Marcus, secondaries: Brett & Ted

Retro

  • Finish webhooks
    • Delivery system testing in dev (Brett, Tomas)
    • Deployment and monitoring (Xavier)
    • Make plugin-server delegate to hooks (Xavier->Brett)
  • Pipeline UI (Tiina)
    • data pipelines unsubscribe option
    • new UI released
      • WIP but not yet released, needed to pick up support as Marcus was off
  • Finish POE (Ted)
    • Write RFC for persons splits
    • Move forward with backfill plan
      • triggered from the splits write-up we now have a simplified model for PoE distinct-id -> person-id overrides
    • Continuing write ramp up

Hang over items from previous sprint

  • Webhooks & PoE & Pipeline UI will all be continued after the offsite.

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 (Dave)
  • ⚪ Joint goal with replay team to get blobby stable (Dave)
    • ⚪ Determine demarc lines of ownership (API layer) going forward
    • ⚪ Make our part stable

High priority

  • Offsite (Tiina)
    • RFC for the future of Person Model
    • Written plan for Blobby
  • Webhooks delivery system running idle in US and EU cloud (Xavier)
  • PoE: Write path for the new distinctId->PersonId overrides (Ted)

Low priority / side quests

  • HogQL batch exports events filtering (Tomas)

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