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 - Apr 15 to Apr 26, 2024 #21456

Closed
pauldambra opened this issue Apr 10, 2024 · 8 comments
Closed

Sprint - Apr 15 to Apr 26, 2024 #21456

pauldambra opened this issue Apr 10, 2024 · 8 comments
Labels
sprint Sprint planning

Comments

@pauldambra
Copy link
Member

Global Sprint Planning

3 things that might take us down

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

-
@pauldambra pauldambra added the sprint Sprint planning label Apr 10, 2024
@pauldambra pauldambra changed the title Sprint - Apr 15 to Apr 26 Sprint - Apr 15 to Apr 26, 2024 Apr 10, 2024
@pauldambra pauldambra pinned this issue Apr 10, 2024
@pauldambra
Copy link
Member Author

pauldambra commented Apr 10, 2024 •
edited by daibhin

Team (funny)Re(name)play

Support hero: Manoel

  • Paul - out for a few days (I don't remember why for a couple so might cancel them 🤣)
  • Manoel 2 days at a conference

Retro

  • are we getting someone to triage/1st-line our support questions? (should be but we don't know when... we think plan is for Steven to onboard and get settled first) @marandaneto
  • good to see Xavier working on blobby changes
  • David and Paul are going to concentrate on getting to a "good stopped" state so the next sprint can be focussed on HogQL filtering for replay

items from previous sprint

High priority

  • 🟡 @pauldambra is writing up an error tracking RFC so we're ready to rock and roll
  • 🍝 Paul is building heatmaps 3000 with Ben
  • we've got a backlog of nits and improvements to Android replay getting ready for advertised open beta
  • we've got a heavy support backlog
  • ✅ so we're starting the quarter with a :fix all the things: sprint
    • some excellent css-in-jss fangling from @daibhin
    • @marandaneto working through the bugs from the last round of replay testing
    • support queue is down from 23 to 16 issues

OKR

  1. OKR, status (red/yellow/green) and action points if yellow/red
  • 🟡 quality and consolidation
    • mobile replay open beta
    • replay captures every site
    • people can find the valuable recordings
  • 🟡 Error tracking MVP
  • 🟡 Hire 2 amazing colleagues
    • 1 interview and 3 super days this week 🫠

High priority

Low priority / side quests

@Twixes
Copy link
Collaborator

Twixes commented Apr 10, 2024 •
edited

Team Pro(fessional)duct Analytics

Support hero: @mariusandra

Retro

  • Thomas: Support & Rolling out HogQL-based insights & HogQL support ✅
  • Michael: Project environments & support rollover Support ✅
  • Julian: Legacy logic/filter cleanup, improve dashboard logic & reloads. ➡️ Async querying and smaller improvements
  • Tom: HogQL & Data Warehouse. Type system? ✅

Hang over items from previous sprint

  • Roll out HogQL-based Paths (time scale depends on whether we find compatibility issue)
  • Reworking dashboardLogic

OKR

  • HogQL-based querying

    • Convert the remaining legacy queries to HogQL and release to public (Thomas, Julian, Marius)
      • 🟢 Insights – will be done this sprint with the rollout of Paths
      • ⚪ Cohorts 👈 some time later
    • Remove legacy querying backend (Thomas, Julian)
      • 🟠 Clean up or rewrite dashboardLogic 👈 this sprint
      • ⚪ Convert filters to query (insights, notebooks, activity log, experiments)
    • Missing Product Analytics features (Thomas, Julian)
      • ⚪ Breakdowns (multiple) in literally everything
      • ⚪ Make a list based on GitHub issues from customer requests…
    • Missing HogQL features (Tom, Marius)
      • 🟠 Type system, JSON 👈 Data Warehouse is on this
      • ⚪ Missing things when building funnels

  • Querying and processing performance (Thomas, Julian)

    • Global performance overview dashboards
      • ⚪ Insights
      • ⚪ Exports
      • ⚪ Cohort recalculations
    • Query request tracing
      • ⚪ Possibly query runner Python optimizations
      • ⚪ Exports improvements
    • ⚪ Identify top 5 query optimizations in terms of impact

  • Artificial Hog / Post Intelligence (Michael)

    • ⚪ Ask a question to get a magical insight (aware of your taxonomy)
    • ⚪ Figure out infra for upgrading queries and models
    • ⚪ Product-wide framework for opting into sharing with OpenAI

  • Activation (side quest: Michael)

    • ⚪ Michael to work with Growth to identify optimizations to getting started with Product Analytics

High priority

  • Marius: Support
  • Michael: Project environments
  • Julian: Dashboard logic rework
  • Tom: Effectively Data Warehouse

Low priority / side quests

  • Start converting filters to query, probably for Julian

@neilkakkar
Copy link
Collaborator

Team Feature Success

Support hero: @neilkakkar
Days off:
Juraj: 1 days
Neil: 1 days

Retro

  • Collect feedback on the new Experiments UI from our top users - @jurajmajerik -> survey is out, some good feedback already, most people love it! Will potentially do some individual reaching out next sprint.
  • Continue improving Experiments UI - @jurajmajerik
    • no results empty state: show checklist for what events are missing. Explore button in the middle of empty state. ✅
    • banners for what to do next - ✅
    • data collection participants bug - set default to 20% for happy path, 50% for edges - no, will rollover.
    • Tooltips (stretch)
    • link to docs (stretch)
    • investigate MAI calculator (stretch)
  • Add property filters [and exact date matching] to event matching in cohorts - @neilkakkar -> ✅
  • Find a good flow for restricting users to exposed users in secondary metrics for experiments - @neilkakkar -> 🔄
  • RFC for feature flags rewrite - @neilkakkar -> ✅

Hang over items from previous sprint

OKRs

  1. Make sure feature flags can handle 10x current scale
  2. Polish new experiments UI & collect feedback
  3. Add most requested surveys functionality

High priority

Low priority / side quests

@tiina303
Copy link
Contributor

tiina303 commented Apr 10, 2024 •
edited

Team Pipeline

Off:
Support: Ted

Retro

High priority

  • Person processing add-on phase 1 (Brett)
  • PoE: Helping out with HogQL migration (Ted)
  • Pipeline UI (Tiina)
    • good progress, but lots of distractions with planning and person processing add-on

OKR

✅=finished 🟢=on track to finish this quarter 🟡=might not finish 🔴=won't finish

WIP we're still doing the planning this week.

High priority

  • Person processing add-on phase 2 (Brett)
  • Batch exports metrics, logs and notification improvements for users (Tomas)
  • Pipeline UI (Tiina)
  • capture-rs mirrors the /batch traffic (without writing to Kafka) and its error rate matches the python version (Xavier)

Low priority / side quests

  • Changing what data pipeline add-on covers (Tiina)

@danielxnj
Copy link
Contributor

Team Infra

Support hero: @danielxnj

Hang over items from previous sprint

  1. 🟢 Spontaneous look into AZ aware routing to try and reduce our biggest cost centre
  • We are stuck because Aurora only provides one AZ endpoint for the writer instance so we can not remove the cross AZ traffic.
  1. 🔴 Purchase reserved RDS instances @frankh
  • why? Risk vs cost works out - to be fully confirmed with pipeline team
  1. 🟡 Get app onto Canary deploys now that we are on contour @danielxnj
  • app.dev is on argo rollouts (not actually canarying but deploying correctly)
  1. 🔴 Test out capture-rs traffic with contour @frankh
  • Had enough ingress issues the last week or so that we took a pause here
  1. 🟡 Get flagged PoC for proper permissions out @benjackwhite
  • So close - just tests to finalise to get merged.
  1. 🟢 Add OOM and restart alerting for all deployments @danielxnj

OKR

  1. 💪 Deploy with confidence 🟡
  • Finalize our Canary Deploy process 🟡
  • Support rust capture to full release using traffic shaping
  1. 🚨 Improved alerting and monitoring
  2. 🔒 Deeper Security
  3. 💰 Continued cost control
  4. 🖖 Splitting up the monolith

High priority

  1. Secret management tooling
  • why? All secrets are leaked in the pods @danielxnj
  1. Interviews. @benjackwhite
  2. Canary roll out to every deployment @frankh
  3. Work with Xavier and the pipeline team on traffic mirroring using contour @frankh

Low priority / side quests

  • Improve Kafka alerting

@robbie-c
Copy link
Collaborator

robbie-c commented Apr 10, 2024 •
edited

Team Web Analytics

Support hero: n/a

Retro

High priority

  • personless events posthog-js changes
    • ready for first set of users
  • personless events UI problem solving whack-a-mole
    • ongoing
  • Write more docs for web analytics (e.g. what is a Channel Type?) and add more tooltips to web analytics

Low priority

  • Session filters for all posthog events
    • WIP
  • Add session properties to the property definition endpoint
    • WIP

Hang over items from previous sprint

  • personless events UI problem solving whack-a-mole
  • Session filters for all posthog events
  • Add session properties to the property definition endpoint

OKR

⚪ Make querying fast enough for large customers
⚪ Do personless events work where necessary (unknown amount of work)
⚪ Iterate on customer feedback
⚪ Product management work

High priority

  • personless events UI problem solving whack-a-mole

Low priority / side quests

  • Session filters for all posthog events
  • Add session properties to the property definition endpoint

@EDsCODE
Copy link
Member

EDsCODE commented Apr 10, 2024 •
edited

Team Data Shack

OKR Q2 2024

Objective

Release data warehouse to everyone

  • Key Results:
    • Integration first experience
      • schemas are reliable
      • modeling of each integration is clear
      • Good automatic roll up views and joins
      • Wizard to onboard people
    • Establish a solid pattern to build integrations
    • Complete data warehouse experience in the rest of the app (insights, feature flags, experiments)

James as a Service -> Clickhouse as a Service

  • Key Results:
    • Better Visibility
      • Regularly testing backups
      • Monitoring/alerting
      • Mutations
      • Moves
    • Management
      • Managing/killing mutations
    • Self Serve
      • Schema design feedback (James non blocking
      • Schema management
    • Automation
      • Replace/Upgrade replicas
      • Upgrading to 24.04
      • Disk configs

Retro

Product

  • @EDsCODE High/medium priority fixes suggested by @annikaschmid here Data warehouse feedback #21105
  • @EDsCODE release data warehouse on trends. This is mostly implemented. Need to make sure everything is working after some of the schema issues that we've been fixing
  • Awaiting hogql release for data warehouse on experiments
  • @Gilbert09 property typings for data warehouse tables (for autocomplete)
  • @Gilbert09 zendesk integration v0.2. Support more granular sync selections when first setting up
  • **WIP new onboarding wizard and sync pattern

Infra
Big outage last week that disrupted work on the last two here

  • Add new way to delete data using a join table instead of inline in query (thanks @timgl)
  • Pulumi integration with housewatch -> make sure that when we recreate instances, the volumes are deterministic
  • Mutation visibility in housewatch

High priority

Product

  • @EDsCODE WIP property typing system for hogQL. This has been a struggle with internal and external usage where unknown types have caused errors so worth working through
  • @EDsCODE multiple joins in a query and multiple level views
  • Figure out Incremental syncs
  • @Gilbert09 finish onboarding wizard. Will give new users a solid understanding of how to take advantage of the data warehouse capabilities in posthog

Infra

  • 🧑‍🔬 Pulumi + CH testing for new cluster
  • 🔍 Investigate why we are having data drift between replicas and have plan to fix when it happens

@raquelmsmith
Copy link
Member

raquelmsmith commented Apr 10, 2024 •
edited by zlwaterfield

Team Growth

Retro

Retro items - [x] Team offsite!

High priority

OKR

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

  1. ⚪ Create a flow in product analytics onboarding to fill out a dashboard template using actions (Raquel)
  2. 🟡 Simplify our subscription flows (Zach, supported by Raquel)
  3. Launch pricing changes (Bianca, Raquel)
    • 🟡 Personless events - will help us reach more customers at an affordable price
    • Data warehouse - it's becoming pretty useful, we should charge for it
    • Session replay - we can reduce costs to improve retention and reach more people

This sprint

  • @raquelmsmith
    • Support billing for person processing addon - get it to a launch-able spot this week. See https://github.com/PostHog/billing/issues/504 for status and tasks
    • Feature gating for activity panel
      • Migrate customers
    • Feature gating for automatic provisioning
      • Migrate customers
  • @xrdt
    • Session replay pricing change plan:
      • Legacy paid customers all get controls
      • New prices PR up
      • Working with Annika to nail down migration strategy
      • Continuing to look into snags I ran into last time with compare_prices script
    • Invoice syncing and revenue issues
      • Revenue drop over weekend
      • We seem to lose invoices when billing cycles roll over
      • Sentry error about type → id
    • Move customer <> (stripe_customer_id, stripe_sub_id) to a One to Many relationship, pr in progress
  • @zlwaterfield
    • Billing changes - auto-subscribing users to all products (starting with new users)
    • Plan the pricing/plan/product structural changes - how do we convey plans vs products?
    • Spend time improving annual/credit Stripe webhooks - these are almost all of the Sentry errors left
    • Update Slack message for growth dashboard
    • Follow up on Next.js proxy issue with Vercel and update Next.js documentation for a note on the reverse proxy bug
    • Metrics to watch:

@Twixes Twixes unpinned this issue Apr 29, 2024
@Twixes Twixes closed this as completed Apr 29, 2024
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
8 participants
@tiina303 @pauldambra @robbie-c @Twixes @neilkakkar @EDsCODE @raquelmsmith @danielxnj