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 - Dec 25 to Jan 5 #19410

Closed
timgl opened this issue Dec 19, 2023 · 7 comments
Closed

Sprint - Dec 25 to Jan 5 #19410

timgl opened this issue Dec 19, 2023 · 7 comments
Labels
sprint Sprint planning

Comments

@timgl
Copy link
Collaborator

timgl commented Dec 19, 2023

Global Sprint Planning

3 things that might take us down

None from last week.

  1. Django updates - not doing this until we can do some type of canary roll out
  2. Adblock - we've moved app to us., we need to be careful not to let anyone use us.posthog.com as the ingestion endpoint. Frank has this as a goal.
  3. Clickhouse EU struggling - kafka cutting out every 2 hours - Jams looking into this

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

-

@timgl timgl added the sprint Sprint planning label Dec 19, 2023
@timgl timgl pinned this issue Dec 19, 2023
@mariusandra
Copy link
Collaborator

mariusandra commented Dec 20, 2023

Team Query Engine Product Analytics

Who's working:

  • 🟡🟡🔴🔴🔴 Christmas week: 1/5 Thomas working some days, Tom as well, everyone else is OOO.
  • 🟢🟢🟡🔴🔴 New year 1st week: 3/5 Michael, Tom, Marius working. Not on the 1st though. Thomas & Julian OOO.
  • 🟢🟢🟢🟢🟢 The sprint after this, new year 2nd week: 5/5 everyone's here.

🟢 - working 4+ days
🟡 - working 1-3 days
🔴 - off the entire time

Support hero:

  • Christmas week: Thomas
  • New year 1st week: TBD (or Marius)

Retro

  • 🟢 Release BI to some users
    • It's a feature preview now!
  • 🟡 Get retention and trends released.
    • Retention is almost over the line. Persons modal HogQL bugs caused delays.
    • Didn't get to trends sadly.
  • 🟡 Great docs for the /api/:project_id/query endpoint, including HogQL and other data exploration nodes.
    • Some really cool progress
    • Won't be done by end of sprint

Hang over items from previous sprint

  • Queries to HogQL
  • API docs

OKR Q1 2024

  1. HogQL & Data Exploration (Julian, Marius)

    • Convert ALL our insights to use HogQL as their base.
    • Improve the type system and get rid of assumeNotNull.
    • Write great docs for HogQL and data exploration nodes.
    • 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.

Next sprint

High priority

  • Christmas week: keeping the lights on.
  • New year 1st week: HogQL insights rewrite.

Low priority / side quests

  • Everything else.

Q1 action plan

We have identified the non-HogQL legacy insights code to be a big source of bugs and wontfix-s. We must keep a lot of old contagious code around to support both old and new insights. To remove it all, we must get rid of the old filters object, which all legacy insights rely on. Rewriting all the queries to HogQL will do just that.

Action plan:

  • Come January, we'll take this list, 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.

@robbie-c
Copy link
Member

Team Web Analytics

Lost some time last sprint to illness and support

Hang over items from previous sprint

OKR

🟢 Build the dashboards to match 80% of functionality

High priority

@benjackwhite
Copy link
Contributor

benjackwhite commented Dec 20, 2023

Team Replay

Support hero: @daibhin (would have been paul but swapping due to holiday)

(Manoel, Ben, Paul out for xmas week. David around for non public holidays)

Retro

  • @daibhin Enjoyed the planning session for Replay - enjoyed having Tim there
  • @marandaneto +1 to above, especially being in person
    • Working closely with Paul has a nice fast feedback loop.

Hang over items from previous sprint

  • 🟢 Q1 Planning
  • 🟢 Alpha release for Android replay that we can start trialling with people for feedback @marandaneto @pauldambra

OKR

  • 📱 Mobile Replay 🟡
    • Android PoC (alpha) is the goal for end of year

High priority

Side quests

@timgl timgl changed the title Sprint - Dec 25 to Jan 12 Sprint - Dec 25 to Jan 5 Dec 20, 2023
@EDsCODE
Copy link
Member

EDsCODE commented Dec 20, 2023

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 5-10 beta users. We've had 5 teams try the connector and successfully sync'd some data
  • 🟥 Track row counts. Up next!
  • 🟩 Better chunking solution. async pipelines run now
  • 🟩 Custom field selection in UI (choose what sources to return from connector)
  • 🟩 MVP'd billing queries in hogql

Side quests

  • 🟥 Start schema drift handling

Infra

  • Complete EC2 Instance type benchmarking
  • Begin TF + Ansible configs for EU on prem cluster
  • Add projection for historical exports

High priority

Product

  • billing/row limits (otherwise large volume customer jobs can run forever)
  • add all schemas as options for stripe connector
  • release to more teams

Infra Board

@raquelmsmith
Copy link
Member

raquelmsmith commented Dec 20, 2023

Team Growth

Retro

Retro items - [x] Finalize activation work & RFC @xrdt - [RFC](https://github.com/PostHog/product-internal/pull/539) is up. - [x] Add step to onboarding for inviting a teammate @xrdt - [x] MRR per product is wrong for feature flags - [x] Should we change MRR per product reporting to be calculated based on usage, not invoice line items? Discussing [here](https://docs.google.com/document/d/1QY3BWjMfd6NvyeOSpPTDwB_zbCj5NPupBpf7Kke0UsY/edit). Shared doc with Neil.

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

  • Add metadata to startup plan customers in stripe @raquelmsmith
  • ctas on billing for customers over 1k/mo
    • Bundling discounts
    • Team training
    • Roadmap chit chat
  • 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
    • Could be an experiment, does it put people off from signing up because it isn’t as transparent, or feels enterprise-y.

@neilkakkar
Copy link
Collaborator

neilkakkar commented Dec 20, 2023

Team Feature Success

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

Retro

Hang over items from previous sprint


OKRs

  1. Get 5 reference customers for surveys
  2. Get reference customers for feature flags and experiments

High priority

  • Fix mismatch between experiment person modal & user count in funnel - @jurajmajerik
  • SDK updates for relative date targeting & targeting by distinct id - @neilkakkar
  • e2e tests for surveys & timer for delayed surveys - @liyiy

Low priority / side quests

@xvello
Copy link
Contributor

xvello commented Dec 20, 2023

Team Pipeline

Retro

  1. Capture-rs @xvello
    • 🟡 Finish rollout to big teams (make sure there’s no issues with proxies) -> Delayed due to memory leak concerns, that are fixed now, should be safe to rollout next sprint
    • end2end probe revamp -> RFC started
  2. 🟡 element_chain:rollout to 100% except exclusions @davemurphysf -> done on all but 20 teams
  3. POE
    • ✅ Simplify person_overrides schema to remove mapping table and drop exclusion constraint, migrate existing data to new table @tkaemming -> running migrations this week
    • 🟡 Start running/testing squashes @tkaemming
  4. Webhooks
    • ✅ Finish consumer
    • Testing in general (load, etc…)
    • Provisioning

Next sprint (25th -> 5th)

Luigi: Tomás then Xavier

  1. Webhooks -> running for team2 prod (sending one event to slack)

    • Support for non-tx and tx modes (we may commit to one or the other later).
    • Hook-consumer metrics.
    • Finishing up hook-janitor work for cleaning-up jobs and emitting metrics.
    • Deployment: Dockerfile, chart, PG
  2. PoE:

    • Ramp up new override path with more teams
    • We have a plan for the backfill
  3. Capture-rs:

    • US rollout for the 20 remaining teams
    • EU rollout (first all teams but one, then that last one)

@mariusandra mariusandra unpinned this issue Jan 17, 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

8 participants