Skip to content

Sprint April 21 to May 2 #31278

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
Closed
ioannisj opened this issue Apr 16, 2025 · 15 comments
Closed

Sprint April 21 to May 2 #31278

ioannisj opened this issue Apr 16, 2025 · 15 comments
Labels
sprint Sprint planning

Comments

@ioannisj
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

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

ioannisj commented Apr 16, 2025 •
edited by lucasheriques
Loading

Team Surveys

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

Retro

Retro - Team Notes

What could've been better

  • lots of support on mobile SDKs across all products, but its time consuming @marandaneto
  • lot of time spent on support tickets @lucasheriques

What went well

  • getting more familiar with flutter and tools, but progress is slow @ioannisj

Retro - Tasks

High priority

  • 🔴 Survey partial responses @lucasheriques
    • 🟢 Figure out a way to allow continue filling a survey in the same session if it closes due to refreshes/url changes
    • ⚪ Update all other charts and data table to consider partial responses (consider only one response per response id)
    • ⚪ Update surveys usage to only consider one event per response id.
  • ⚪ 🐛 Don't calculate NPS score for non-NPS questions @lucasheriques (other stuff took priority)
  • 🔴 Android surveys - UI views and beta release/docs @marandaneto
  • 🟡 Flutter surveys - This depends on the output of the next couple of days but minimum goal is to integrate with iOS SDK and show a dummy view when a survey is activated @ioannisj
    • Getting familiar with dart and tooling - small sample apps, tutorials etc
    • Experimented with showing a bottom sheet and taking advantage of existing PostHogWidget - needs polishing
    • Next step: wire the two together (BasicMessageChannel?)

Low priority / Side quest

Mobile replay and Mobile SDKs

Goals

Click to expand quarterly goals

High priority

Low priority / Side quest

@veryayskiy
Copy link
Contributor

veryayskiy commented Apr 16, 2025 •
edited
Loading

Team ReP[au]lay

Support hero:
@pauldambra

Retro

## what we shipped

  • saved filters
  • UI for heatmaps
  • Fixed issue with "screens" in events list
  • prototype for summarization

High priority

  • 👩‍🔬 Goal 2: Churn and retention exploration
    TBC
  • 🟡 🎤 Goal 3: Watch less and get more value making filters better
    TBC
  • 💀 Goal 4: Squash distractions @pauldambra
    • 🟡 move E2E tests from Cypress to Playwright - @pauldambra
    • 🟡 testing our own rrweb with our own recordings
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.

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

  • watch recordings from where they are

    • a lot of people use persons as the entry point for recordings, want to improve that @veryayskiy
    • better "not found" state for recordings @veryayskiy
      • e.g. TTL passed, or recording might be sampled, etc etc

Side quests and lower priority

* add-on: research store recordings longer paid feature @annikaschmid 
* RN - session timeout - stop of recordings (we have it in web) @veryayskiy 
* Digest email @pauldambra

@daibhin
Copy link
Contributor

daibhin commented Apr 16, 2025 •
edited
Loading

Team Error Tracking

@hpouillot @daibhin @oliverb123 off 1 day

Retro

🟢 Launched without any major issues
🟢 Working HogVM, hoping to have our first advanced feature out (auto assignment)
🟢 CLI supports indexed maps
🟢 Shipped new issue page & omnisearch
🔴 Planned work on Linear destination usurped by UI rework
🔴 Custom server side issue grouping (reprioritised auto assignment)

OKR

✅ Launch with pricing

Be the default choice for the languages we support

⚪️ Make it easier to integrate
🟢 Improve product quality
🟢 Build advanced features for larger customers

High priority

Make it easier to integrate

  • Make decision RFC on JS package structure @hpouillot
  • Make it easier to search for issues (Correctly instrument) @daibhin
  • Improve the Python SDK & Django integration @daibhin
    • Stack trace ordering
    • User context from request
  • Fix issues uploading larger source maps (21MB limit)

Build advanced features for larger customers

Improve product quality

  • Add platform display and filter to issues (draft PR) @hpouillot
  • Finish GitHub integration & external issue creation @daibhin

Side quests

  • Investigate adding git context to symbol sets during CLI upload (commit / tags) @oliverb123

@benjackwhite
Copy link
Contributor

benjackwhite commented Apr 16, 2025 •
edited
Loading

Team CDP

Support hero: @benjackwhite

OKR

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

😍 OMG so many destinations
💖 Data pipelines UI sparks joy
🤑 Pricing thats works for everyone

Retro

  • ✅ Release Hog based transformations @meikelmosby
    • By end of week should have all in place to release
  • 🟡 Start using HogTemplate code instead of copying it into each hog function @meikelmosby
    • RFC done will start on this next week
  • 🔴 Figure out what to build for community Templates @annaszell @meikelmosby
    • Anna leaving to other team so didn't do much hear. This is dependent on templates in the DB anyways
  • 🟡 moving ad destinations to node and convert them to use mappings @MarconLP
    • PRs up just fixing some remaining issues
  • 🔴 figure out a way to test pixels in node @MarconLP
  • 🟡 Try to hook up Segment destinations to PostHog @MarconLP
    • Some progress here investigating stuff
  • 🔴 CDP pricing @annaszell
  • 🟢 getting slack app verified @MarconLP
  • 🔴 rolling out site_destinations out publicly @MarconLP

Other

  • @benjackwhite very ingestion focused wrapping things up to handover
  • @benjackwhite scaling the cyclotron stuff, rate limiting of bad webhooks

High priority

  • Bring cyclotron fetch into node and add all of our protections that apply to normal hog processing @benjackwhite
  • Migrate legacy plugins and zapier webhooks finally to CDP @benjackwhite
    • We can then finish the purge and remove VM2
    • Means we don't have to support legacy plugins in the UI
    • Timebox other options for cyclotron
  • Co-ordinate more closely with team-messaging on the architecture @benjackwhite
  • Implement the templates-in-db approach @meikelmosby
  • PoC out the AI generated destinations using Max AI to start with @meikelmosby
  • Hook up the Segment destinations @MarconLP
  • Roll out site destinations (can we remove the opt in flag) @MarconLP

Low priority / side quests

  • figure out a way to test pixels in node @MarconLP
  • is there low hanging fruit to integrate hog function errors into the error tracking product? @meikelmosby
  • Change the webhook template to by default throw on errors

@MichaelKutsch-ph
Copy link
Contributor

MichaelKutsch-ph commented Apr 16, 2025 •
edited
Loading

Team ClickOps

Support:

Retro:

High priority

Infra:

  • ✅ Finalize move to argo flow @MichaelKutsch-ph @danielxnj
    • ✅ Move ingestion services to argo/new chart with Eli (cdp/ingestion took over)
  • ✅ Analyze cost spike in March: this seems to be legit, we were just getting way more load
  • 🟡 Re-prio: scaling up US (two additional readers) for feature flags
  • 🟡 moving persons off postgres: test logical replication running on dev @danielxnj
  • 🟡 fix CIDR overlap for new subnets @bciaraldi
  • 🟡 Test S3 tiered storage on MSK @frankh
  • 🟡 Review and extend runbooks w/ team infra @Daesgar
    CH:
  • ⚪ Hand off deduplication @tkaemming -> ingestion is taking over
  • 🟡-> Prop defs to CH -> RFC @tkaemming @bciaraldi
  • 🟡 Pair incidents with infra/ch @Daesgar @PostHog/team-infra - started it, a topic with no concrete end date
  • ✅ Dump events to iceberg @Daesgar - done, next steps to be defined.
    • testing s3, Glue, s3tables
  • 🟡 Get started with upgrade clickhouse version @tkaemming - started, need to look into fixing tests
  • Pawel/DW: observability improvements to create better visibility. Performance issues: should we add limits?

Low priority / side quests

  • 🔴 Making clickhouse parts smaller @Daesgar -> more likely: resharding
  • 🟡 investigate: what grinds query exec. to a halt sometimes? @tkaemming - throttling vs scaling: decision necessary
  • 🟡 Fix missing events in livestream @orian
OKR Infra

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

OKR CH
  • Query Observability and Performance Improvements
  • Make ClickHouse ops easy
  • Use Altinity Antalya in production for events

High priority

Infra:

  • moving persons off postgres: test logical replication running on dev @danielxnj
  • fix CIDR overlap for new subnets @bciaraldi
  • Move over to s3 tiered storage on MSK @frankh
  • DX: argocd @MichaelKutsch-ph
  • Find a replacement for loki (up for grabs)

CH:

  • Prop defs to CH -> RFC @tkaemming @bciaraldi
  • Testing antalya @Daesgar
  • Continue: Get started with upgrade clickhouse version @tkaemming
  • Explore thread/cpu limits for clickhouse, define priorities (idea: make SQL queries low prio, API Queries high prio - take it from there) @tkaemming @orian
  • Check / improve Ingestion-rate @Daesgar

Low priority / side quests

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

@pl
Copy link
Contributor

pl commented Apr 16, 2025

Team Ingestion

Retro

  • 🟢 Onboarding Nick in Vancouver 7th-11th of April @pl @eli-r-ph
  • 🟢 Move ingestion to ArgoCD
  • 🟡 Continue rollout of Blobby V2 @pl
  • 🟡 Roll out batch write changes to propdefs @eli-r-ph
  • 🟡 Land the caching changes @pl
  • 🟡 Isolate the database in the propdefs-v2 deployment @eli-r-ph

Low priority

  • Investigate data migration options @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

  • Improve defensive measures for ingestion @PostHog/team-ingestion
  • Investigate discrepancies between Blobby V1 and V2 session recordings @pl
  • Continue persons migration @pl
  • Investigate event duplication @nickbest-ph
  • Investigate removing capture django @eli-r-ph

@Twixes
Copy link
Member

Twixes commented Apr 18, 2025 •
edited
Loading

Team Max AI

OKR

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

Retro

  • 🟢 Proxy LLM calls @kappa90
  • 🟢 Port static analysis to new extension @kappa90
  • 🟢 Simplify code agent @kappa90
  • ⏸️ New query planning architecture, incl. evals for SQL fallback @Twixes
  • ⏸️ Run evals in CI @Twixes 

  • ⏸️ Integrate PostHog UI (probs iframe)
@Twixes
    • Deprioritized above in favor of data warehouse tool and editor blockers
  • 🟢 Codebase indexing MVP @skoob13
  • 🟢 Smooth creation of personal API key @joshsny (guest)

High priority

  • Code editing improvements @kappa90
  • PostHog subagent in the editor @kappa90
  • Make Max onboarding spark joy step by step @kappa90
  • Conversations history @skoob13
  • Release action semantic search for all projects @skoob13
  • Cohort semantic search out @skoob13
  • Codebase indexing shipped @skoob13
    • Combine semantic and grep search
  • Feature extraction based on codebase @skoob13
  • Run evals in CI @Twixes 

  • New query planning architecture, incl. evals for SQL fallback @Twixes
  • Integrate PostHog UI
into extension @Twixes

Low priority / side quests

  • Autocomplete improvements (fine-tuned model?) @kappa90

@rafaeelaudibert
Copy link
Member

Team Revenue Analytics

Retro

High priority

  • 🟢 Initial views in the database
  • 🟠 Decide on how we choose between using charges or invoices in the view
  • 🟢 Initial UI for Revenue Analytics with basic MRR/ARR

Low priority

  • 🔴 Migrate the config to a separate table

OKRs

  • 🟢 Web-Analytics-like dashboard for metrics tracking
  • 🟡 Expose streamlined revenue DW view to allow customers to improve on top of it
  • ⚪ Streamline Stripe connection

This sprint

https://github.com/orgs/PostHog/projects/122/views/3

Sprint will also be focused in heavily collecting feedback on what we should build here

High priority

  • Integrate events
  • Add permissions
  • Allow to choose which events/views customers want to see data from

Low priority

  • Improve onboarding

@mariusandra
Copy link
Collaborator

mariusandra commented Apr 22, 2025 •
edited
Loading

Team DevEx

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)

High priority

Project tree last 20%

  • Shift + click mutiselect
  • Breadcrumbs
  • Move "new..." menu higher in the context menu
  • Save as dialog
  • Inline textfield for new folders (no window.prompt)
  • Bug: moving while in search mode doesn't update results
  • "Move to" dialog
  • Save as dialog for ALL products
  • Bug: creating folders under "save to" is broken
  • Sorting (with pagination)
  • Table view looking good
  • Update/delete tree entries when updating/deleting objects
  • Make it faster
  • Show users with faces
  • Filter search results by type
  • History (to activity log)

@andehen
Copy link
Contributor

andehen commented Apr 22, 2025

Team experiments

Support

@rodrigoi first week
@andehen second week

OKR's

🟢 All new experiments use the new query engine
⚪ Add frequentist method + other requested features
🟢 Implement a fair and transparent pricing model
⚪ AI-Powered experimentation workflow

Retro

Rodrigo:

  • Much more comfortable with the domain.
  • Delivered the Running time calculations.

Anders:

  • New experimentation engine is now in public beta 🎉 7 distinct organizations now with active experiments on the new engine
  • Docs created
  • Bunch of bugfixes
  • Bunch of experiments migrated to new engine
  • Easter holiday

This sprint

Rodrigo:

  • Keep working on the support channel.
  • Fix the reported bugs and UI improvements.
  • The delta chart has some important issues that need to be addressed.

Anders:

  • Work on feedback from beta users on the new engine
    • Show raw stats in the new engine
    • Make it easier to migrate experiments / metrics (?)
    • Query performance?

Annika (experiments pricing):

  • Decide on PostHog pricing, calculate expected costs for existing customers (so we know how realistic it is)

@dmarticus
Copy link
Contributor

dmarticus commented Apr 23, 2025 •
edited
Loading

Team Flying, Leaping, and Galloping (FLaGs)

Retro

Theme: tuning `/flags` performance and rolling out new API response to all SDKs.

What went well

  • @haacked

    • finally got every SDK to latest version of our API
    • wrote RFC/meta issue around all the various inconsistencies in our SDKs, and how customers run into bugs around our SDKs

  • @dmarticus

    • shipped flags out to 1.5% of all global flag evaluation traffic. Performance metrics look great (about 2x faster with significantly less resource consumption)
    • worked with infra to understand scaling issues with /decide and stopped us from being hammered by off-hours load spikes (see the line going down below)
    • fixed several bugs with the /flags rollout, getting really close to the functional parity that will get me excited to roll it everwhere
Image

What could've gone better

  • A few functional issues with flags that have come up during the rollout, so I'm glad I'm keeping it to a relatively small scope for now. But, it meant we couldn't roll flags as broadly as we wanted to.

This sprint

Themes: Roll out new flags everywhere, finish /decide?v=4 support for all clients, start on behavioral targeting, and anything else on the docket.

High Priority

Low Priority

  • Will try and get to behavioral cohort targeting assuming all goes well with /flags rollout
  • Stuff around stateless flag abstractions and cache

Support

Time Off

@haacked from 04/10 to 04/14

Q2 2025 Objectives

(Details here)

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

@lricoy
Copy link
Member

lricoy commented Apr 23, 2025 •
edited by robbie-c
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: @lricoy

High priority

  • @lricoy page report iteration based on post-release feedback (released 7th April) 🔴 (Dropped to work on query performance after high-profile support tickets appeared)
  • @robbie-c onboarding @jabahamondes! 🟢
  • @jabahamondes joining!! 🟢

Low priority

This sprint

Support hero: @robbie-c

High priority

  • @lricoy use pre-aggregated query performance tables for web_overview and web_stats queries
  • @jabahamondes keep working on the active hours component to add more dimensions
  • @robbie-c
    • Add property mangling to posthog-js (reduces bundle size by 13.5%!)
    • Fix issues with cookieless mode counting unique users

@annaszell
Copy link

annaszell commented Apr 25, 2025 •
edited
Loading

Team Product Analytics (4/28-5/12)

Retro

  • Sandy

    • 🟡 Finish Optional Funnel Steps
      • Coding
    • 🔴 Investigate Tim's Async Query Runner
    • 🔴 Improve Exports
      • Move them to temporal
      • Better alerting when fail (tell the user why, especially OOM, suggest less columns)
      • Think about increasing limits or helping the user with pagination
      • Exports not showing up in UI until refresh

  • Anirudh

    • 🟡 slack notifications for alerts (integrate with cdp destinations)
    • ✅ retention docs
    • Support
      • 🔴 insight edit mode

  • Thomas

This sprint

Support hero: @thmsobrmlr & @aspicer

  • @aspicer

    • Support

  • @anirudhpillai

    • Wrap up Alerts CDP integration
    • Revamp alerts UI
      • move away from popup into sidebar
    • Start statistical analysis

  • @thmsobrmlr

    • Support
    • Query node migration system
      • Likely use Temporal to for a backfill task that migrates outdated query nodes in insights, notebook, activity log, ...
      • Endpoint for validating/migrating frontend queries from URLs/local storage
    • Prep a bit for Tulum hackathon, potentially improve taxonomic filter suggestions with Max AI

  • @annaszell

    • Activation next steps / Onboarding improvements

@joshsny
Copy link
Contributor

joshsny commented Apr 28, 2025 •
edited
Loading

Team Growth

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

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

  • 🟢 Work on the editor project
  • Setup wizard:
    • 🟠 PR workflow
    • 🟢 Cursor rules
    • 🔴 Environment variables workflow for Vercel users
  • 🟢 Vercel integration: Start integration for flags in Vercel
  • 🟠 RFC for vibe coding integrations + explore existing integrations (e.g. Supabase etc.): Decided to meet directly with their teams first to discuss integration rather than do an RFC
  • 🟠 Add E2E tests for the onboarding flow
  • 🟢 Fix bugs reported in onboarding whilst away

@zlwaterfield

  • 🟢 Will be shipping environments & access control stuff!

Sprint

@joshsny

  • 🟢 Lovable: Meet with their team to discuss integration
  • Vercel: Create example app for PostHog in Vercel repo and ship the PostHog flags adapter
  • 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
  • 🟠 (Extra) Make a start on OAuth provider flow

@zlwaterfield

  • Fully rollout in app cc experiment

Time off: None

@zlwaterfield
Copy link
Contributor

zlwaterfield commented Apr 28, 2025 •
edited by pawel-cebula
Loading

Last sprint plan as a jumping-off point: https://github.com/PostHog/billing/issues/1226

Team Billing

Retro

Retro items
  • @zlwaterfield
    • 🏗️ more environments w/ Ben
    • 🏗️ quota limiting event properties
    • rbac
      • ✅ bugs from Ada
      • ✅ global access controls PR
    • ✅ make sure Big Time Data is onboarded
  • @patricio-posthog
    • ✅ Support week 1
    • ✅ Changes for Mobile replay pricing (adding Flutter to GA)
    • ✅ New version of billing api (v2)
    • ✅ Issue with get_last_period_invoices in February (edge cases)
    • ✅ Revenue issues in general
    • 🟡 LMM obversability pricing coming next, I may already start working on this
  • @pawel-cebula
    • ✅ Support Week 2
    • ✅ Finalize startup and YC program migration
    • 🏗️ New page with usage breakdown by project/product/time (more context from our brainstorm on this here)
  • @minekansu
    • ✅ IWA updates - work with bigtimedata on business needs re revenue (credits as cost) and churn
    • ✅ Contraction deep dive -> focused more on retention
    • ✅ Data backfill - PostHog-Clay sync, add harmonic and business shutdown data -> harmonic in progress (Zach will check deployment with infra)
    • ✅ Sales ops - set up metrics for onboarding specialists, work with Scott and the sales team re SFDC tasks plan, new lead triggers from harmonic.ai data, update annual plan setup flow

Q2 2025 Objectives

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

  • Pato

    • Pricing changes
      • ⏸️ API queries (new)
      • ✅ Error tracking (new)
      • ⏸️ Identified / Non identified (modification)
      • LLM Observability (new)
      • Experiments (new / modification)
      • Max AI (new) [Seat based]
      • there may me more
    • IWA and revenue reporting solution
    • 🟡 Billing runbooks and docs (internal) (we can all work on this)

  • Zach

    • 🟡 RBAC - finish rollout + Enterprise add-on
    • 🟡 Quota limiting improvements (Temporal)
    • 🟡 Usage report improvements (Temporal + better pipelines)
    • Evaluate Orb
    • 🟡 Environments - finish rollout
    • High level scaling plans (usage reports, quota limiting, etc.)
    • Trial changes - do not bill
    • Unsubscribe workflow - remove access + show used features

  • Pawel

    • ✅ Finish startup program application (if not already done)
    • 🟡 Usage on billing page - per project/product breakdowns
    • 🟡 Billing page - compress/improve UI
    • Spike alerts system
    • Zapier annual plan workflow - bring into billing

  • Mine

    • 🟡Standardized reporting on lifecycle stages (churn, contraction, new revenue, expansion)
    • Help make sure PostHog BI is on par with Metabase and accurate
Extras (nice to haves if we have time or feel inspired)
  • Login QoL improvements (US/EU, last login method)
  • No more Stripe UI (edit cards, view invoices, etc.)
  • Proper callbacks for time-sensitive checks
  • Case insensitive emails

This sprint

Time off: @zlwaterfield and @pawel-cebula - 1 day

  • @zlwaterfield
    • Support Week 1
    • RBAC
      • rollout to all teams
      • figure out global access control logic
      • get actions resource live
      • make plan for non resource access control (web analytics)
    • Finish the in app cc rollout (with payment intent error handling)
    • New platform add-ons
    • Keep on top of environments requests
    • Help Mine deploy the Harmonic script
    • Billing → PostHog sync
    • if time
      • Quota limiting event properties
      • Quota limiting clean up
  • @patricio-posthog
  • LLM Observability and Max AI launches
  • @pawel-cebula
    • Support LLM observability launch
    • Ship new usage and spend pages to the first users
    • Monitor startup and YC program and troubleshoot where needed
  • @minekansu
    • bigtimedata, work with team to get the final sow
    • sales ops - work with contractor to get things started
    • harmonic <> posthog direct integration
    • sales and cs growth review prep

@mariusandra mariusandra mentioned this issue Apr 30, 2025
Closed
@lucasheriques lucasheriques unpinned this issue May 14, 2025
@daibhin daibhin closed this as completed May 19, 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