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.

Sign up for GitHub

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

Jump to bottom

Sprint - Mar 10 - Mar 21 #29477

Closed
ioannisj opened this issue Mar 4, 2025 · 12 comments
Closed

Sprint - Mar 10 - Mar 21 #29477

ioannisj opened this issue Mar 4, 2025 · 12 comments
Labels
sprint Sprint planning

Comments

@ioannisj
Copy link
Contributor

ioannisj commented Mar 4, 2025

Sprint Planning

List of incidents + any action items that haven't been scheduled yet

Team sprint planning

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

# Team ___

**Support hero:** ___

## OKR

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

## Retro

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

### High priority

-

### Low priority / side quests

-
@ioannisj ioannisj added the sprint Sprint planning label Mar 4, 2025
@ioannisj ioannisj pinned this issue Mar 4, 2025
@ioannisj
Copy link
Contributor Author

ioannisj commented Mar 4, 2025 •
edited
Loading

Team Surveys

🟢=finished 🟡=in progress 🔴=won't finish ⚪=not started

Retro

Retro - Team Notes

  • Feeling grateful! ❤️ - @ioannisj
  • Feels like SDK issues keep surfacing making it hard for me to stay focused on high-priority tasks. Need to block out some days of the week for deep high-priority work @ioannisj
  • Made an effort to be more active and engaged in PRs but there's still room for improvement @ioannisj
  • iOS multiple SDK instances is finally out @ioannisj
  • PR reviews have been really helpful to make sure we're covering all changes @lucasheriques

Retro - Tasks

High priority

Low priority / Side quest

Goals

  • 🟡 Improve quality
  • 🟡 Mobile Surveys
  • 🟡 Talk to customers
  • 🟡 Finish up WIP features

High priority

Low priority / Side quest

@MichaelKutsch-ph
Copy link
Contributor

MichaelKutsch-ph commented Mar 5, 2025 •
edited
Loading

Team infra

Support: @frankh

Retro

High priority

  • ✅ ArgoCD improve DX for rollingSync @MichaelKutsch-ph
  • ✅ Signed up with DoIt Essentials
  • ✅ new notifications for deployments in argo @danielxnj
  • ✅ Performance improvement Grafana/Loki
  • 🟡Move non-capture steps to Warpstream @frankh - prod-us is tomorrow, huzza!
  • 🟡 helping to get dagster up @bciaraldi
  • 🟡karpenter upgrade among other upgrades @bciaraldi
  • ⚪ (maybe) Move apps to RollingSync @MichaelKutsch-ph
  • ⚪ Move last services from posthog chart to new chart (migration, ingestion) @danielxnj
  • ⚪ plan central grafana / alerting? (maybe)

Low priority / side quests

  • ⚪ move old capture to new capture @MichaelKutsch-ph
  • 🔴 Evaluation of Robusta.dev (better alerts, AI and fancy things...) - killed
OKR
  1. 🏃 Next level ArgoCD - Continuous Delivery
  2. ☁️ 🕸️ Scalable networking
  3. 💰 Mr. Bezos, bring down those costs!
  4. 🎮 A stable pre-prod environment

High priority

  • Move apps to RollingSync @MichaelKutsch-ph
  • Migrate asset upload to argo @MichaelKutsch-ph
  • Migrate migration job to argo and new chart @danielxnj
  • Move non-capture steps to Warpstream on all prods @frankh
  • Move ingestion services to argo/new chart @danielxnj
  • Rollout new subnets on prod @bciaraldi
  • Purchase warpstream from AWS marketplace (cost savings / ppa)
  • Check other things to purchase from marketplace (cost savings / ppa)

Low priority / side quests

  • plan central grafana / alerting?

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

@veryayskiy
Copy link
Contributor

veryayskiy commented Mar 5, 2025 •
edited
Loading

Team RePAAy

Support hero: @pauldambra

Retro
  • i'll just repeat mine
    • OMG support load -> Support is more or less under control @pauldambra 🚀
    • CI has been horrible @pauldambra - > CI team?
  • not convinced we can get through all of our goals given other distractions @annikaschmid
  • worried about support and rrweb distractions @veryayskiy

## what we shipped
chunking
a lot from paul :)

High priority

  • 👩‍🔬 Goal 2: Churn and retention exploration
    • 🟡 PLAYLIST COUNTERS - can we process all playlists that have filters (Saved filters) once a day so we can say "X new recordings in the last 24 hours" @pauldambra - yes we can ✅
  • 🎤 Goal 3: Watch less and get more value making filters better
  • 💀 Goal 4: Squash distractions @pauldambra
    • 🟡 move E2E tests from Cypress to Playwright - @pauldambra
      • get as much as possible done
      • but also get other folk set up to keep this going

Side quests and lower priority

  • 🟡 🎤 Goal 3: Watch less and get more value
    • ❌ link from analytics (particularly funnels) to replay @pauldambra ]
    • ✅ chat with recordings - getting feeback / fixing bugs
OKRs 🟡
  1. OKR, status (red/yellow/green) and action points if yellow/red
  • ✅ 🚀 Goal 1: Get Alex rocketing
  • 🟡 👩‍🔬 Goal 2: Churn and retention exploration
    • talking to users and picking metrics
  • 🟡 🎤 Goal 3: Watch less and get more value
    • in the short term, looking at playlists and filters to see what we can get
  • 🟡 💀 Goal 4: Squash distractions
    • need support to be less tricky-things-heavy

High priority

  • 👩‍🔬 Goal 2: Churn and retention exploration
    • PLAYLIST COUNTERS - roll out to all projects @pauldambra
  • 🟡 🎤 Goal 3: Watch less and get more value making filters better
    • Beta "mark similar recordings as watched" @veryayskiy
    • Analize and tweak prompts "chat with recordings" @veryayskiy
  • 💀 Goal 4: Squash distractions @pauldambra
    • move E2E tests from Cypress to Playwright - @pauldambra
      • get as much as possible done
      • but also get other folk set up to keep this going

Side quests and lower priority

* split saved filters and playlists @veryayskiy (with @pauldambra  supporting)
* add-on: research store recordings longer paid feature @annikaschmid 
* RN - stop of recordings (we have it in web) @veryayskiy

what might we do? -> https://posthog.slack.com/archives/C03PB072FMJ/p1739953734791699

@benjackwhite
Copy link
Contributor

benjackwhite commented Mar 5, 2025 •
edited
Loading

Team CDP

Retro

  • 🟢 Rollout Logs and Testing tools for retrying failed functions @benjackwhite @MarconLP
  • 🟢 Get GeoIP moved to using S3 mounted bucket (makes it more deterministic) @benjackwhite
  • 🟡 Return to the purge @benjackwhite
    • Bunch of mini purges done to remove jobs, schedules and old ingestion
  • 🟢 Make the Hog Function API public and that the documentation isn't too bad @meikelmosby @benjackwhite
  • 🔴 Add legacy plugins comparison logic to validate it is all 1-1 @meikelmosby @benjackwhite
  • 🟡 Move over to WS with Infra peeps @benjackwhite
  • 🟢 GET requests for prop defs go via API and not the DB @eli-r-ph
  • 🟡 Focus on finishing integrations @MarconLP
    • 🟢 Google ads work (nested accounts)
    • 🟡 Slack app submission finalised
    • 🟢 Release Reddit / snapchat with warning about rate limit
    • 🔴 TikTok
    • 🟢 Intercom
  • 🔴 Move existing templates to Nodejs @MarconLP
  • 🟡 Feature parity with Blobby v1 @pl
    • Get Team 2 reading from Blobby v2
    • Parity with Blobby v1 for events tables
    • Comparison testing to ensure all end data is the same as before
    • Realtime polling from client for S3 data

Out-of-plan

  • Pivot to investigating missing prop defs @eli-r-ph
  • Issues with slack channel loading

Discussion

OKRs

  • 😍 People choose us for their CDP first 🟡
  • 🖕 Plugins be gone 🟢
  • 🚀 Warpstream for events 🟢
  • 🎈 Write-optimized session replay ingestion 🟢
  • 💪 We make changes and improvements to the Node services with confidence 🟢

High priority

  • Add legacy plugins comparison logic to validate it is all 1-1 so we can move off of @benjackwhite
  • Migrate all existing Zapier hooks to hog functions @benjackwhite
  • Release Hog based transformations @meikelmosby
    • Load test the hog function based transforms to ensure it is release ready
    • Work with docs team to get transforms and destinations good for release
  • Try to hook up Segment destinations to PostHog @MarconLP
  • TikTok Ads destination @MarconLP
  • Fix the Slack integration channel selection widget @pl
  • Feature parity with Blobby v1 @pl
    • Get Team 2 reading from Blobby v2
    • Parity with Blobby v1 for events tables
    • Comparison testing to ensure all end data is the same as before
    • Realtime polling from client for S3 data
  • Improve metrics and reliability of prop-defs ingestion @eli-r-ph
    • Goal would be that we can verify for any event if the properties were written or not and why
    • Get the node based comparison service up and running @benjackwhite
  • Get prop-defs api working and used via django @eli-r-ph

Low priority

  • Playwright tests for creating, modifying hog functions (would have caught a bunch of bugs this week)
  • Add RBAC to Hog Functions? @PostHog/team-cdp
  • Move existing templates to Nodejs @MarconLP

@mariusandra
Copy link
Collaborator

mariusandra commented Mar 5, 2025 •
edited
Loading

Team DevEx

OKR

  • 🟡 Build a framework where we can have 50+ products? @mariusandra
    • 🟡 Defining and splitting the common layer from the rest of the apps
    • 🟡 Defining and implementing boundaries between apps
    • 🟡 UX changes to support the new structure
    • ⚪ Every product is able to export operations (backend) and widgets (components) => AI, notebooks etc.
    • 🟡 Testing independently - if you change things on one product, we only run tests for that product
  • 🟡 Levelling up our product quality. @adamleithp
    • Design system that is self documenting
    • Mobile support
    • Finally figure out (explain) modals vs drawers
    • More standardised components
  • 🟢 Anti-goal for Q1: @corywatilo
    • Fixing CI when it randomly breaks (each team owns their tests)
    • Rewrite everything
    • Implement everything ourselves

Retro

  • Cory
    • Fine tune the new layout / sidebar
      • Waiting for implementation
  • Adam
    • Implement the new layout's frontend (design & interactions, dnd, etc)
      • Progress with tree view, more changes to come
  • Marius
    • Implement the new layout's backend (file tree backend persistence, new node sync)
      • Mostly there, still missing pagination
    • Make our tests not suck
      • Tests still suck

High priority

This is for the ongoing week and the next one

  • Marius
    • Get the project tree feature complete and into testing with some real users.
  • Adam
    • Implement the new layout
  • Cory
    • Continuous feedback and iteration

Low priority / side quests

  • Marius
    • Continuous Hog/QL support
  • Adam
    • Tailwind v4 upgrade

@timgl
Copy link
Collaborator

timgl commented Mar 5, 2025 •
edited by orian
Loading

Team ClickHog

Objective

Goals for Q1:

  • Query Scheduling Service
    • Paid API use case is covered
    • We should have all queries running through this
    • Basic load shedding
    • Differentiate API queries based on $
  • Iceberg continuation
    • Keep on top of Altinity builds for CH
    • Query logs into Iceberg
    • Ingestion pipeline work (monitoring & automation)
  • Cluster topology consolidation and cost reductions
    • We are on one cluster
    • Query performance is equivalent
    • Costs are down
    • Schema management
  • Ongoing HogQL/Performance improvements
    • Query Scheduling
    • Productizing Performance Tooling
    • Better query attribution (in query comments)
      • By end of query we do not run queries with no annotations
      • Some sort of Type for queries that will run

Board

https://github.com/orgs/PostHog/projects/85/views/2

Retro

🔥 Incidents 🔥

Happy cluster. Happy Life.

Last Sprint's Goals

  • 🔴 Duplication investigation @tkaemming
  • 🟢 Expose whether or not a new query is utilizing indexes @orian
    • Only need to be exposed in the UI but the API returns it
  • 🔴 Clickhouse in K8s @Daesgar
    • will be issues with NVME, so either we switch US to EU topology, or we try to use s3backedmergetree with TTL setup to move off of NVME.
  • 🟢 Finish standing up EU Offline replica set @Daesgar
  • 🔴 Backups to Dagster @fuziontech
  • ❓ Metabase dashboard for delete compliance @fuziontech
    • Table data is available in ClickHouse, but not sure about the Metabase dashboard
  • 🟢 Clean up weekend EU disk alerts @fuziontech @Daesgar
    • Tuned the alert, but still can page. We can't tune it more so we need to provide enough storage for weekend mutations.
  • 🟡 Backfill Person Properties into a map on US @tkaemming
    • This is still in progress? We are backfilling, but still need to complete it
  • ❓ HogQL printer/ast/visitor improvements @orian
  • ❓ Turn on/off logic/button for "Query as a Service" @orian

This Sprint's Goals

TL;DR

  • Duplication investigation @tkaemming
  • Move backups to Dagster @Daesgar
    • Backups are flaky right now in HouseWatch and hardly retriable
  • Rework ClickHouse on-calls / update runbooks while Jams is out @Daesgar
    • Of course, we need to agree as a team, but I'll send a proposal
  • Analysis of date partitions hit by event queries @Daesgar
  • Add created_at to person table (link) @Daesgar
  • Add QaaS usage reporting to billing @orian
  • Switch between free / paid QaaS based on billing data @orian

@Twixes
Copy link
Member

Twixes commented Mar 7, 2025

Team Max AI

Support hero: @skoob13

OKR

Replace 10 full-time data analysts around the world with AI

Retro

High priority

  • ✅ Semantic search on actions MVP shipped @skoob13
  • ✅ SQL insights support (based on current code from the SQL editor) @Twixes
  • 🟠 Natural language "Add insight" on dashboards @Twixes
  • 🔴 History of conversations @skoob13
  • 🟡 Fix other issues identified in our Feedback review @Twixes @skoob13

Low priority / side quests

  • ➡️ Prototype integrating @PostHog/team-replay's recordings search into core Max (RFC on how teams can add Max skills)

High priority

  • General release for Teams+Enterprise users
    • Add indication of Max can and can't do in UI @Twixes
  • Semantic search on cohorts @skoob13
  • History of conversations @skoob13
  • Integrate Max throughout app: @Twixes @skoob13
    • AI "Add insight" on dashboards
    • AI "Edit/explain insight" on insight
    • AI "Edit SQL" on SQL editor
    • 👆 Based on above, RFC on how product teams can implement AI
  • Question clustering script to group questions coming up @skoob13

Low priority / side quests

@daibhin
Copy link
Contributor

daibhin commented Mar 7, 2025 •
edited
Loading

Team Error Tracking

Retro

🟢 Successful week onboarding Hugues in London
🟢 Source map upload cli v1 planned & almost built (needs cymbal changes)
🟡 Progress on framework specific bugs but looks like there is a lot more to tackle here
🔴 Did not realise how close to the end of the quarter we are

OKR

🟠 Migrate PostHog off Sentry
🟠 Ship the damn thing

High priority

Migrate PostHog off Sentry @daibhin

  • Track exceptions in EU & US (carried over)
  • Remove everyone from Sentry (except for tracing, on-call engineer)
  • Add it to the billing repo (in-person)

Ship the damn thing

  • Source map uploads @oliverb123
    • Cymbal changes and e2e flow working
    • posthog-cli release automation (optional)
    • Another round of bug hunting
  • Issue page UI improvements @hpouillot
    • Move date range filter
    • Select earliest / latest exception
  • Move to public beta
    • Onboarding flow
    • Quickstart guide (optional)
    • Add product intents
    • Pricing exploration
  • Separate SDKs for specific frameworks
    • Starting with NextJS
    • Work with @joshsny on wizard to make framework specific changes

Low priority / side quests

  • Bulk actions (resolve, assign, etc)
  • Decide on launch extras for marketing
  • Resolve forever e.g. drop exceptions by issue id (expensive to do in cymbal given current pipeline, but imo a blocker to release given impact on billing)

@EDsCODE
Copy link
Member

EDsCODE commented Mar 10, 2025 •
edited by phixMe
Loading

Team Data Storehouse

OKR Q1 2025

Objective

Objective: World class query experience

  • Key Results:
    • SQL copilot
    • Draft mode
    • Data modeling and lineage controls

Objective: Data Visualizations

  • Key Results:
    • Complete suite of charting options
    • External data for all insights

Objective: Extensible sources

  • Key Results:
    • Repeatable and easy to build data import source pattern
    • Revised source configuration experience

Priorities

  • graceful shutdown of temporal workers @tomasfarias
  • release bigquery source @tomasfarias
  • live testing of sources @phixMe
  • allow users to define trigger time of syncs @phixMe
  • final memory fixes across all sql sources @Gilbert09
  • query run state—dont rerun long queries and local cache as optimistically as possible @EDsCODE

@robbie-c
Copy link
Member

robbie-c commented Mar 12, 2025 •
edited by lricoy
Loading

Team Web Analytics

Support hero: @lricoy

OKRs

  • 🟡 Finish cookieless mode
  • Build marketing analytics
    • 🟡 Add revenue data to web analytics
    • 🟡 Get ad spend data into data warehouse and use it for per-channel analytics
  • Build per-page reports
    • 🟢 Core web vitals

Retro

  • 🟡 dogfood reddit & snapchat pixels, fix problems @robbie-c
  • 🟡 Cookieless next steps - decide endpoint @robbie-c
  • 🟡 Page reports @lricoy
  • 🟢 Finish Host selection UI @rafaeelaudibert
  • 🟢 Clickhouse dictionary for currency @rafaeelaudibert
  • 🟢 add a CDP function to block CIDR IP address ranges @robbie-c
  • 🟢 charts visualization option for web analytics' stats tables @lricoy
  • 🟡 improve docs (e.g. docs on bounce rate) @lricoy
  • 🔴 CSP violation report @lricoy

Extra:

Next sprint

High priority

Low priority

  • improve docs (e.g. docs on bounce rate) @lricoy
  • Add a source for revenuecat

@joshsny
Copy link
Contributor

joshsny commented Mar 17, 2025 •
edited
Loading

Team Growth

Support hero: week 1 - @joshsny , week 2 - @zlwaterfield

OKR

Goal 1: Make it easier for users to onboard into multiple products
Goal 2: Understand better how user's are using multiple products
Goal 3: Make setting up the PostHog SDKs easier

Retro

✅ Get to a useful POC of using AI to setup PostHog SDKs @joshsny
✅ Data warehouse experiment in product analytics onboarding @joshsny
✅ Finish off session replay privacy in onboarding @joshsny
🟡 Improve/add activation metrics for other products @joshsny
✅ Ship the install page experiment @joshsny
✅ In-app credit card flow @zlwaterfield

Side quests:
🔴 Explore demo data usage

High priority

  • Self serve account deletion @joshsny
  • Add React support to the setup wizard @joshsny
  • Investigate suggested insights in product analytics based on ingested event data + user paths - goal is to onboard product analytics users into a useful insight they can edit @joshsny
  • Review in-app credit card flow experiments @zlwaterfield

Low priority / side quests

Time off

@joshsny - 24th-28th March

@dmarticus
Copy link
Contributor

dmarticus commented Mar 17, 2025 •
edited
Loading

Team Faffing, Late, in Arrears, Glacial Sprint planning (FLAGS)

Previous sprint Retro

We shipped quota limited flags, we're running into some issues with rolling out new flags (long tail of infra challenges), and we've had to ship a lot of observability fixes to help us better support customer pain that we've noticed thanks to some of our customers running into scaling issues

What went well

  • @haacked
    • shiping posthog-dotnet 1.0
    • implementing concurrency controls for feature flag editing
    • my first Support Hero tour of duty
  • @havenbarnes
    • support cycles with a high priority customer led to some great finds and fixes around scalability + observability
  • @dmarticus
    • trying out some new flags infrastructure to solve the pgbouncer issue with new flags
    • quota limited flags have been released and we haven't seen a massive influx of support volume, so that's good

What could've gone better

  • @dmarticus new flags is taking a long time to roll out – first it was the infra issue with pgbouncer I mentioned above, then it was this issue with migrated types. It's finally ready as of March 17 but it's been a slow journey to get there.
  • @havenbarnes
  • @haacked - having better insights into flag usage and how they're evaluated would speed up support ticket investigations.

This sprint

Themes: Roll out new flags, work on Java SDK, help out our high-priority customers, continue to ship better observability features for flags

  • @dmarticus

  • @havenbarnes

    • Launching new posthog-java SDK
    • RFC writing for upcoming work

  • @haacked

    • /decide?v=4 which will provide observability improvements
    • Client support for v4 across the board
    • Surface evaluation reason in $feature_flag_called events.
    • Port holdout_groups support to /flags

Support

Q1 2025 Objectives

(I'm going to turn these into sub-issues so I don't have to type so much)
✅=finished 🟡=in progress 🔴=won't finish ⚪=not started

🟡 Performance & Reliability
🟡 Customer-Driven Innovation
⚪ Strategic Research
  • Identify and analyze key user segments:
  1. Current active users
  2. Competitor users
  3. Custom solution implementers
  4. Potential users unaware of feature flagging
  • Conduct customer interviews to identify gaps and growth opportunities
  • Document findings and recommendations for product roadmap.
  • More context here
🟡 SDK Spike
🟡 User Experience Improvements

Low-hanging, medium-impact, and largely context-free fruit that can be picked up by any team member during available capacity:

@daibhin daibhin closed this as completed Mar 24, 2025
@daibhin daibhin unpinned this issue Mar 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
sprint Sprint planning
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests