Skip to content

Sprint May 19 to May 30 #32200

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
Open
lucasheriques opened this issue May 14, 2025 · 13 comments
Open

Sprint May 19 to May 30 #32200

lucasheriques opened this issue May 14, 2025 · 13 comments
Labels
sprint Sprint planning

Comments

@lucasheriques
Copy link
Contributor

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

-
@lucasheriques lucasheriques added the sprint Sprint planning label May 14, 2025
@lucasheriques lucasheriques pinned this issue May 14, 2025
@lucasheriques
Copy link
Contributor Author

lucasheriques commented May 14, 2025 •
edited by marandaneto
Loading

Team Surveys (WIP)

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

Retro

Retro - Team Notes

What could've been better

  • Partial responses queries caused an incident. Wish I'd worked better to make it easier to rollback with a ff instead of reverting the whole PR @lucasheriques
  • Focused a bit on session replay performance on iOS this sprint. Trial and error along with profiling sample apps took time but there’s now an open proposal on the table for a potentially major performance improvement — currently awaiting team feedback. @ioannisj
  • Adding support for capturing console logs on iOS ended up being more challenging than anticipated and slowed things down for me. @ioannisj
  • Tried a side-quest-first approach this sprint, which kind of backfired. I didn't get back to surveys until later in the sprint, which also required picking up momentum to where I left off. I figure less context switching works better for me, so I'll try the opposite approach this sprint @ioannisj
  • I feel I’ve slowed down a bit lately — probably just some signs of burnout creeping in. I’ve booked a couple of days off this sprint to regroup, recharge and spend some time with the fam @ioannisj
  • my 3 days sprint was pretty much working on customer tickets/SDK bugs @marandaneto

What went well

  • Console log capture for iOS is now supported for session replay, which is a big win for debugging @ioannisj
  • the offsite :D @marandaneto

Retro - Tasks

High priority

Mobile replay and Mobile SDKs

Low priority / Side quest

Goals

Click to expand quarterly goals

High priority

  • Option to show multiple questions within the same view - vertically aligned @lucasheriques
  • Save custom templates
  • Add a onRenderSurvey handler/delegate in survey configuration for iOS and Flutter. @ioannisj
    • Users can use this to take control of rendering/showing a survey when a survey is activated by conditions
    • The default handler will be the default sdk survey implementation on iOS/Flutter
    • This is used by Flutter SDK to take control of iOS survey display, so we may as well expose it properly
  • Finish default Flutter surveys UI @ioannisj
    • Finish view layout of all question types
    • Test and handle keyboard avoidance
    • Handle survey style/appearance
  • Android surveys - release beta version @marandaneto

Mobile replay and Mobile SDKs

Low priority / Side quest

@pauldambra
Copy link
Member

pauldambra commented May 19, 2025 •
edited
Loading

Team All your replay are belong to us

Support hero:
@sortafreel (@pauldambra supporting support)

mostly all in... spring bank holiday in UK

Retro
  • offsite 💖
  • hackaton was amazing

## what we shipped

  • Collections

High priority

  • Many of our customers have lots of recordings, but struggle to find the "useful" ones.

    • ➡️ set metrics (KPI) and add them to the dashboard @sortafreel
    • ✅ keep improving summaries with user feedback @sortafreel

  • Make it super easy to see what filters have results to watch - "show me, don’t make me figure it out"

    • ✅ show recordings in activity by time in the "figure out what to watch" tab @pauldambra
    • out behind a flag, can start to test

  • ✅ watch recordings from where they are @veryayskiy

    • turns out the insight that made us think persons page had lots of traffic was wrong so we punted this
    • finished split of collections and saved filters out to people

Side quests and lower priority

  • ➡️ RN - session timeout - stop of recordings (we have it in web) @veryayskiy
  • ➡️ Digest email @pauldambra
  • better "not found" state for recordings @veryayskiy
    • e.g. TTL passed, or recording might be sampled, etc etc
  • ➡️ lazy load session recording in the SDK @pauldambra
OKRs 🟡
  1. OKR, status (red/yellow/green) and action points if yellow/red

  • ✅ 🚀 Goal 1: Get Alex 2 rocketing 2

    • it's great to have Alex 2 on the team... let's make it a success

  • 👩‍🔬 Goal 2: Find the needle in the haystack

    • Many of our customers have lots of recordings, but struggle to find the "useful" ones. We want to test and iterate on a bunch of different ideas to get customers to value faster.
    • Understand the needles that people are looking for using user interviews, data analysis and more
    • Better options for users to watch recordings from where they are (e.g. in funnels or experiments)
    • Some people are scared of filtering, some people have no patience for it - give them ways to avoid it
    • Make it super easy to see what filters have results to watch - "show me, don’t make me figure it out"

#30460

High priority

  • Many of our customers have lots of recordings, but struggle to find the "useful" ones.

    • some simple tracking of beta usage @sortafreel
      • are they retaining? is it sticky already?
    • keep improving summaries with user feedback @sortafreel
    • and on support this sprint!

  • Make it super easy to see what filters have results to watch - "show me, don’t make me figure it out"

    • show recordings in activity by time in the "figure out what to watch" tab @pauldambra
    • new filters UI without a modal? @pauldambra
    • Digest email out and sending @pauldambra
      • want to test just collections
      • want to test just saved filters

  • watch recordings from where they are

Side quests and lower priority

  • RN - session timeout - stop of recordings (we have it in web) @veryayskiy
  • better "not found" state for recordings @veryayskiy
    • e.g. TTL passed, or recording might be sampled, etc etc
  • lazy load session recording in the SDK @pauldambra
  • CSP reporting finished - live and revenue (robbie and lucas doing most of this - hurrah) @pauldambra

@daibhin
Copy link
Contributor

daibhin commented May 19, 2025 •
edited
Loading

Team Error Tracking

@daibhin off for most of the sprint
@hpouillot off the first few days

Mid-quarter checkin

✅ Launch with pricing

  • Released and charging customers!

🟢 Build advanced features

  • Really good progress on rules. Mostly done, need to be tested and released
  • Moving onto versioning info

🟢 Product quality

  • Tons of UI and performance improvements
  • Focusing on integrations with other products next

🟢 Make it easier to integrate

  • Improved docs
  • Improved structure of JS lite to support edge environments
  • Focusing on a NextJS specific package next (very common support topic)

High priority

@hpouillot

  • TBD for when you're back

@daibhin

  • Reach out to highly engaged customers
  • Prep rules for release
    • Custom grouping UI
    • Release internally
    • Write docs

@oliverb123

  • Symbol set versioning
    • CLI / Upload context
    • Exception event enrichment

@joshsny
Copy link
Contributor

joshsny commented May 19, 2025 •
edited
Loading

Team Growth

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

Q2 Goals

  • Installation & SDK experience: Automate the setup of 50% of PostHog installations

    • Setup wizard
      • 🟢 Support more integrations
      • 🟢 Uploading environment variables to common hosting providers
      • 🟢 PR workflow
      • Github action
      • 🟠 Automatic event instrumentation
    • 🟠 Be the default analytics provider for vibe coders
    • 🟠 Be the default option in boilerplates for NextJS, React & React Native
    • 🟠 Improve the onboarding experience for self hosting users

  • Make it easier to use multiple products

    • Project homepage: make this a good place to see an overview of all your products
    • Gather common pitfalls from user onboarding calls and replays in each product and remove them

  • Launch a creative product experiment once a month!

Retro

@joshsny

  • 🟢 Lovable: Meet with their team to discuss integration
  • 🔴 Vercel: Create example app for PostHog in Vercel repo and ship the PostHog flags adapter - Vercel are dragging their feet on this PR
  • Setup wizard:
    • 🟢 Get it on the homepage
    • 🟢 Ship some improvements based on feedback
    • 🟢 Finish off PR workflow
  • 🟢 Automate beta workflow: Send events when users move from one stage to another in a preview beta so that they can be used in Customer.io
  • 🔴 Investigate why product intents are not activating for some products - investigated, my logs PR has some funky stuff going on
  • 🟢 (Extra) Make a start on OAuth provider flow - made more progress than I thought

@zlwaterfield

  • Fully rollout in app cc experiment

Sprint

@joshsny

  • AI DX:
    • 🟢 Enable error tracking by default for the frontend
    • 🟢 Sync with Danilo on next steps
    • 🟢 Lovable / Replit B2B2C RFC + meetings
  • MCP server:
    • 🟠 Move deployment setup into posthog cloud infra / charts
    • 🟢 Fix authentication issue and deploy MCP server on Cloudflare
    • 🟢 List on marketplaces
    • 🟢 Document installation into Claude, ChatGPT, Cursor + Windsurf
    • 🟠 Add as optional step to all wizard installations using a PAT token - made progress on the wizard side, we need to think about PATs and how we communicate that, as the MCP server needs wide scopes
  • OAuth Applications:
    • 🟢 Ship OAuth models for new applications
    • 🔴 Ship authorize and token endpoints + authorization page
  • 🟢 Remove ability to delete account with a PAT
  • 🟢 Vercel flags provider: Create example app
  • 🟠 Debug celery issue with event previews

@zlwaterfield
TBC

@daniloc

  • AI DX:
    • Draft and post: devtools advice in the age of robots (re: the Karpathy post about docs)
    • Draft and post: MCPs and you
    • Sponsorship for starters: scout the landscape and draft a budget
    • Test out a couple PRs for PostHog in starter projects
    • Quick thoughts on ideal customer
  • DeskHog:
    • Cleanup some of the OTA update UI
    • Small launch tasks for Joe
    • Special edition cases for elite customers

Time off: @zlwaterfield - 2 days
@daniloc - 1 day
@joshsny - 2 days

@mariusandra
Copy link
Collaborator

mariusandra commented May 19, 2025 •
edited
Loading

Team DevEx

Work in progress - will be finalized durning standup later today.

OKR

  • 👷 Build the "Product OS"
    • 🟢 New layout and "file-based" project view. Almost done
    • ⚪ Nested nodes within nodes Notion style
    • 🟡 Every product is able to export operations (backend) and widgets (components) => AI, notebooks etc.
    • 🟡 Shortcuts and suggestions
    • ⚪ Permissions
    • ⚪ Keep iterating on shared UI components. Split out Lemon UI and Lemon Components.
  • ⏱ Improve dev tooling in PostHog
    • 🟡 Roll out "product folders" for all teams
    • ⚪ Convert E2E tests to playwright
    • ⚪ Tests take 5-10min max
    • ⚪ Standardize dev tooling (vscode, flox, docker, self hosted)

Retro

Last issue

Fixed a lot of project tree feedback, added shortcuts, and had a great offsite in Tulum.

High priority

  • Project tree
    • Split "project tree" logic into "data" and "instance" logics (better file pickers, etc)
    • Bring back data management
    • Shortcuts.
      • Figure out an approach that works. Having them default on is jarring to some.
      • Drag and drop?
    • All other feedback
    • Environments
  • Product folders
    • Document the best practices in a README (structure, migrations, etc)
    • Run python tests standalone
    • Encourage people to start moving products over

Low priority

  • Project tree
    • Pinning
    • History / activity log
  • Table view - we're keeping the product listing views for now, so this is fine.

@jurajmajerik
Copy link
Contributor

jurajmajerik commented May 19, 2025 •
edited
Loading

Team Experiments

Support

@rodrigoi

OKR's

Retro

Juraj

  • Catching up after the leave
  • Added support for experiment conclusion
  • Some MDE calculator fixes

Anders:

  • support
  • Bug fixes
    • allow more than 4 steps in funnel metrics
  • Holiday
  • Offsite!

Rodrigo

This sprint

Juraj

  • Understand feature flags pricing + support Annika with new pricing
  • Fix bugs in the exposure features
  • Research: how should the UI support the Frequentist method?

Anders:

  • Implement the backend for frequentist method
  • Look into making the new engine default for new users
  • New engine fixes:
    • Improve UX when there is not enough data
    • Fix preview of action metrics
    • support shared metrics in MDE calculator

Rodrigo

@MichaelKutsch-ph
Copy link
Contributor

MichaelKutsch-ph commented May 19, 2025 •
edited
Loading

Team InfrAllTheFun

Retro:

High priority

  • MSK tiered storage success 🥳 - almost no failovers anymore
  • 🟡 SOC2 Audit @danielxnj - waiting for request for evidence etc. Cleanups and follow ups necessary on open topics.
  • 🟡 make RDS proxy work @danielxnj - created in dev - paused for now. prioritzing persons move
  • 🟡 Move persons out asap @danielxnj - replication issues caused incident with blocked table / DMS. Checking other migration tooling.
    Isolating new persons DB to own AWS account and locked down networking. already deployed to dev. testing other migration tooling now
  • 🟡 taking care of single point of failure redis @MichaelKutsch-ph: scaled up, adding tracing now to see what is happening to start untangling this. Added quickwit, jaeger, otel
  • 🟡 replace loki with a (managed?) logging - incl SIEM @frankh -> victoria logs
    -> LOGHOG FTW. Clickhouse FTW
  • ✅ RDS switching to new instance types and optimizing sizing @bciaraldi
  • 🟡 cross-az costs spiking @bciaraldi - diving deeper into cross AZ costs, plus diving into savings plans and RIs
OKR Infra

🏃Improve build times for posthog apps
💽 Splitting RDS
🔒 AWS Account and networking re-work

High priority

Low priority / side quests

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

@haacked
Copy link
Contributor

haacked commented May 19, 2025 •
edited
Loading

Team Fortuitous Launches Avoid Gaffes (FLAGs)

Retro

Theme: Getting `/flags` ready for prime time, making local evaluation more robust.

Last sprint: #31747

What went well

Tulum offsite!

  • @haacked

    • Deployed feature flags secure token
    • WASM hackathon - conclusion, not ready for prime time.

  • @dmarticus

What could've gone better

  • Didn't finish support old /decide fields for flag so rollout for flags is halted for now. That's top priority.
  • TODO

This sprint

Theme: Support legacy /decide response fields for /flags, scale up infra to support wide rollout, and roll new flags everywhere; improve local_evaluation.

High Priority

  • @dmarticus

    • ???
      Question: What's the status of Behavioral Cohorts?

  • @haacked

    • Fix bug in flags paging on the person page
    • Port /local_evaluation to Rust.

Low Priority

  • Look into how competitors instrument feature flags
  • [ ]

Support

Time Off

@dmarticus on 5/19 - 5/23
@haacked on 05/26 - 5/30

Q2 2025 Objectives

(Details here)

  • 🟢 Flag Stability, Consistency, and Resiliency
  • ⚪ Behavioral Cohort Targeting
  • ⚪ AI IDE Integration

@pl
Copy link
Contributor

pl commented May 20, 2025 •
edited
Loading

Team Ingestion

Retro

  • 🟡 Switch off blobby v1 @pl
  • 🟢 Understand performance issues with persons with large number of distinct IDs @nickbest-ph
  • 🟢 Continue work on moving to capture-rs @eli-r-ph

Discussion

OKRs

  • 🟡 Fix property definitions service
  • 🟢 Finish moving to capture-rs
  • ⚪ Develop ownership of ingestion incidents
  • 🟢 Improve infrastructure for deployments

High priority

  • Implement event deduplication in ingestion @nickbest-ph
    • Figure out how much we can cache in memory
    • Find out what's the deduplication window we can support
  • Trial optimistic updates in groups @jose-sequeira
  • Update autovacuum configuration @jose-sequeira
  • Switch off Blobby V1 @pl
  • Move to KEDA @pl
  • Start looking into SDKs @pl

@havenbarnes
Copy link
Contributor

havenbarnes commented May 20, 2025 •
edited by abheek9
Loading

Team Messaging

Retro

n/a

OKRs

  • 🟡 Launch Messaging v1

High priority

This sprint

Abheek:

  • Get comfortable with development
  • Understand and add liquid support for gaps in unlayer
  • Onboard with Product Team

Mahamad:

Moustafa:

@fuziontech
Copy link
Member

Team Clickhouse

Support:

##Retro:

High priority

Done:

  • Adding team deletes dagster job @Daesgar

Almost done:

Deprioritized:

  • Have partitioning and schema ready for iceberg @Daesgar
    • Write a job that takes last full day of data from clickhouse, moves it to iceberg, with materialized columns

Low priority / side quests

Almost done:

  • Continue: Get started with upgrade clickhouse version @tkaemming

Not much progress:

  • Have a look at which other materialized columns we can get rid of @tkaemming
OKR CH
  • Query Observability and Performance Improvements
  • Make ClickHouse ops easy
  • Use Altinity Antalya in production for events

High priority

Low priority / side quests

  • Continue: Get started with upgrade clickhouse version @tkaemming
  • Have a look at which other materialized columns we can get rid of @tkaemming

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

@k11kirky
Copy link
Contributor

Team LLM Observability

Support hero: @k11kirky

OKR

🔴 Evals : havent started yet
🟡 Launch: pushed back until further resourcing

High priority

  • Support queue to 0
  • Launch playground to team 2 and lovable
  • Upgrade to support new python sdk version
  • Update node to support responses api

Low priority / side quests

-Add posthog tracking to LLM O product + intent triggers.

@robbie-c
Copy link
Member

robbie-c commented May 27, 2025 •
edited by lricoy
Loading

Team Web Analytics

OKRs

  • 🟡 Make Cookieless mode production-ready

    • 🟢 Add batching to redis calls
    • Fix associating unidentified users who have allowed cookies

  • 🟢 Page reports

    • 🟢 Iterate UX based on feedback after general release
    • 🟢 Error tracking cross-sell

  • 🟡 Marketing analytics

    • Get ad spend data from 2-5 data warehouse connectors (most likely Google Ads and CSV files, then other ad platforms that we can dogfood)
    • Build out the 80/20 of marketing analytics insights, e.g. total revenue and spending per channel and per campaign
    • Show GSC data via the API or batching with no filters

  • 🟡 Query performance

    • Add sampling to web vitals
    • Experiment with pre-aggregating query results
    • Improve sessions table join

  • 🟡 HogQL virtual fields

    • Add support for person initial channel type
    • Experiment with how to add e.g. CPA (average for channel) as a virtual person property

Retro

Support hero: @robbie-c

High priority

  • @lricoy 🟢 continue working on dagster jobs for pre-aggration
  • @lricoy 🟢 move some of the web analytics queries to using pre-aggregation
  • @jabahamondes 🟢 continue working on the new insight for CalenderHeatMap (name TBD)
  • @robbie-c 🟢 Continue fixing issues with cookieless mode counting unique users
  • @robbie-c 🟢 Batch redis operations in cookieless implementation

This sprint

Support hero: @robbie-c

High priority

stretch goal

  • @annaszell user research for marketing analytics (ask sales "who are some customers that have mature marketing motions (who probably use batch exports also, or significant amounts of revenue)")

Note: we're not actively on page reports to focus on query performance, but are collecting feedback for when we switch back to this

@mariusandra mariusandra mentioned this issue May 28, 2025
Open
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