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 - Oct 28 to Nov 8 #25746

Closed
Phanatic opened this issue Oct 23, 2024 · 13 comments
Closed

Sprint - Oct 28 to Nov 8 #25746

Phanatic opened this issue Oct 23, 2024 · 13 comments
Labels
sprint Sprint planning

Comments

@Phanatic
Copy link
Contributor

Global Sprint Planning

3 things that might take us down

Urgent incident follow-ups

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

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

-
@Phanatic Phanatic added the sprint Sprint planning label Oct 23, 2024
@Phanatic
Copy link
Contributor Author

Team Surveys

Retro

✅ Beta testing no-code experiments with customers
✅ Global CSS for Surveys
✅ Various small UI fixes for Surveys

Side Quests

OKRs

  1. Implement Enterprise-ready features for Surveys
  2. Increase adoption of Surveys.

High priority

  • Continue beta testing no-code experiments with customers.
  • Custom Survey templates at the team level
  • Investigate support for mobile surveys in posthog-react-native library

@mariusandra mariusandra pinned this issue Oct 23, 2024
@pauldambra
Copy link
Member

pauldambra commented Oct 23, 2024 •
edited by ioannisj
Loading

Team Everyone in PostHog comes to Spain

Another 1 week shipping, 1 week travelling sprint

Support hero: @richard-better with @pauldambra supporting

Retro

  • lots of diversions this sprint, ES6 bundling in posthog-js, rrweb upgrades, support driving a lot of small changes (24 PRs in 2 weeks 🤯), lots of small pieces is pretty tiring @pauldambra
  • feeling slow, switching context, and getting used to answering tickets, gathering requirements for mobile autocapture @ioannisj
  • 3 days sprint for @marandaneto due to a medical leave

Mobile

  • 🔁 get mobile recordings into billing_usagereport @pauldambra
    • need a bit more clarity here first
  • ✅ track size of mobile recordings so we understand better how expensive mobile ingestion / storage is @pauldambra
  • 🔁 get first alpha of flutter replay out @marandaneto
    • no progress due to short sprint (medical leave) and focused those days on fixing issues after user interviews and bug reports.
  • ✅ implement the swift ui masking from last sprint's experiment @ioannisj
  • ✅ auto capture for element interactions in iOS Element interactions auto capture support posthog-ios#179 @ioannisj
    • Swift UI is pending
  • gathering mobile replay feedback @annikaschmid

Replay

  • ✅ roll out the URL trigger
  • 🔁 and adding a URL denylist @richard-better

Low priority / side quests

OKR

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

🟡📱Goal 1: People think of PostHog as a mobile solution
🟡 📹 Goal 2: Replay playback 3000
- delayed-ish till Nov and Cory time in Valencia
🟡 🎤 Goal3: Ship the things users keep asking for

High priority

  • nobody is lost or arrested in Valencia
  • Valencia offsite is now pretty large (~12 people) so making sure everyone gets heard and feels it was valuable
    • treat it as three offsites at the same time that sometimes overlap so that we don't have 12 people always doing everything together

Mobile

Replay

  • replay URL denylist @richard-better
  • a brief diversion before querying network data - wrap websockets as well as fetch @pauldambra
    • this should include making it safer to roll out changes to recordings dependencies

Low priority / side quests

@mariusandra
Copy link
Collaborator

mariusandra commented Oct 23, 2024 •
edited
Loading

Team Crabs Ducks Pigeons

  • Support: Marcus
  • Marius off first week
  • Ben is back from Tuesday

Retro

  • 🟡 CDP pricing @annaszell @mariusandra
    • We decided to keep the current pricing structure, and reduce costs slightly.
    • Details still in progress.
  • 🟢 Figure out what to build with messaging (and build v0.0.1-alpha) @mariusandra
    • Long RFC. Started building. Proof of concept ready. Alpha ready end of this sprint.
  • 👍 Error tracking & support. Cross team support, not a lot of feature work (on CDP). @oliverb123
    • Little bit of progress. Olly did a lot of support work that took most of his time.
  • 👍 Google & Meta ads destinations, help with messaging UI @MarconLP
    • Out, but waiting for Google approval.
    • Bunch of other destinations
    • No progress on the messaging UI

OKRs

  • Widespread usage of the new CDP
  • Messaging V1
  • Ingestion is rock solid

Sprint focus

High priority

  • @mariusandra Get messaging v0 ready for dogfooding.
  • @benjackwhite CDP UI/UX + coming back from holiday (odds/ends)
  • @oliverb123 Olly 80% on error tracking. Improve live debugging of CDP.
  • @MarconLP Support sprint + new destinations

@daibhin
Copy link
Contributor

daibhin commented Oct 23, 2024 •
edited
Loading

Team Trackers of Errors

@daibhin EU on-call Week 1
@daibhin @oliverb123 Valencia offsite in Week 2
@neilkakkar working on Experiments / off second week

Retro

🟡 Storing resolved source map frames @oliverb123

  • Made good progress but CDP support was busier than expected
  • Source map external fetching & resolution. Storage modelling in place
  • At risk of not finishing reading / writing to S3

🟡 Overrides table for issue merging @daibhin

  • Deciding on approach took longer than expected
  • Open PRs to create the necessary tables
  • Hoping to write new JOIN queries by the end of the week

🟡 Advanced fingerprinting in Rust @neilkakkar

  • First version ported over from plugin server
  • Need to add logic to decide on
  • Fingerprinting logic (e.g. exclude unresolvable stack frames if trace includes resolvable frames)

⚪️ Add language tag to frames on the JS & Python client @daibhin
✅ Choose persistent key / value store for stack frame resolution (Postgres or Dynamo or something else) @oliverb123
✅ Rename stack trace properties on JS SDK (beware: Sentry integration relies on some of this) @neilkakkar
✅ Generate stack traces for synthetic exceptions @daibhin
✅ Fix stack traceless 'Script error.' reported by customer @daibhin

OKR

🟢 Human readable stack traces for Javascript
🟢 Ensure scalability of query time issue grouping
⚪️ Alerting via CDP
🟢 Launch

High priority

Stack trace demangling enabled for PostHog team

  • Fix serialisation issues now that cymbal is deployed
  • Writing / Reading source maps via S3 (Rust) @oliverb123
  • In-app source map uploading @daibhin
    • Button on unresolved frames to add a source map
    • Writing source maps via S3 (Django)
    • Hook up invalidation of frames in Postgres (cascade delete)

Fingerprint to issue lookup flow

  • Postgres client / queries @oliverb123
  • Wiring up fingerprinting & issue lookup to demangling flow @daibhin

Low priority / side quests

  • Frontend query caching to improve page load speed @daibhin

@zlwaterfield
Copy link
Contributor

zlwaterfield commented Oct 23, 2024 •
edited by raquelmsmith
Loading

Team Growth

Retro

Retro items
  • @raquelmsmith
    • Fix forecasting bug that says peoples' forecast is much higher than what they see on billing page
    • Fix bugs with product analytics onboarding flow
    • Personless default change
    • Make sure metrics move didn't break wnything
    • Re-up activation metrics for product analytics - try using insight saved instead of insight created
    • Use new product intent table in activation metrics
  • @patricio-posthog
    • Continue working with the sync invoices changes to use webhooks instead of a daily sync using Stripe API
    • Check billing limit bug raised by jdoodle (support ticket)
    • May investigate slow load times in billing page and try to optimize them (confirm first if it only affects ElevenLabs)
  • @zlwaterfield
    • RBAC
      • Finish v1 of the RFC for billing
      • Start working on it - decide if we should continue on Ben's PR or start from scratch and do it piece by piece - get at least 1 PR merged for it
    • Finish up the Technical Exercise RFC - resolve comments and get merged, share out
    • Get the CC entry PR shipped
    • Adding user id to billing token for events
    • Adding Hogfetti component
    • Growth review (if time permits)
      • We had a number of “accidental” signups that got refunded in sept, which might show up as churn
      • Teams plan survey after they subscribe
      • Use new ICP data to compare with CC activations - are high ICP people still subscribing at the same rate?
      • Add is subscribed bool and mrr to org group

Q4 Goals

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

  1. 🟡 Get to a 4/10 in Enterprise platform support (Zach)
    • 🟡 Release Enterprise addon and iterate with sales to find a pricing model that makes sense
    • 🟡 Build RBAC
  2. 🟡 Make revenue & forecasting more reliable (Patricio)
    • 🟡 Rejig how we do sync_invoices so we don’t see big drops - respond to webhooks instead of large syncs
    • ⚪ Evaluate temporal vs celery for usage reports and billing tasks so we can adhere to rate limits better
    • ⚪ Side hustle, if time permits: Rejig how anonymous / identified events are billed, as the current implementation is confusing.
  3. 🟡 Activation: reverse trials, analytics onboarding flow, understand CC activation (Raquel)
    • ⚪ Dig into the data, watch replays to figure out why CC activation rate has been falling
    • ⚪ Add reverse trial to onboarding
    • 🟡 Add reverse trial to billing page for teams

This sprint

Time off: Raquel (1/2 day)

  • @zlwaterfield
  • @raquelmsmith
    • Slowly roll out personless default change, deal with any issues
    • Fix bugs with product analytics templates onboarding flow
    • Ship session replay "templates" screen
    • Write data warehouse activation query
    • Think about how to redo onboarding so people can pick multiple products at once
    • Respond to customer about projects-on-invites
  • @patricio-posthog
    • Billing limit: Get this bug fixed once and for all so we can move on
    • Forecasting bug: Fix forecasting and if it's a good idea, reimplement it with a new version
    • Improve current billing API endpoints (optimize or spit current ones into separate endpoints)
    • Check if the webhooks for invoices are working fine (check events at Posthog) / turn off the daily sync to test that.

@Gilbert09
Copy link
Member

Gilbert09 commented Oct 23, 2024 •
edited
Loading

Team Data Storehouse

OKR Q4 2024

Objective

Query 3000

  • Key Results:
    • Autocomplete
    • Increase general BI experience/product BI meta#157
    • Declutter the data warehouse UI and make the features intuitive to find

Data Modeling MVP

  • Key Results:
    • Infrastructure decided and implemented
    • Integrating external data with feature flags
    • External data everywhere in insights/persons/cohorts
    • Get billing team to use modeling in posthog for their invoices_with_annual table

Retro

eric second week

Priority

eric out first week

  • Using warehouse person properties in experiment metrics
  • SQL editor @EDsCODE @Gilbert09
  • release dashboard insight variables to everyone @Gilbert09
  • BigQuery source release to everyone @Gilbert09
  • Investigate reducing temporal-data-warehouse pod size @Gilbert09
  • Resolving batch exports replication lag - some solution, working with team clickhouse @tomasfarias
  • More onboarding tasks @rossgray
    • Release chargebee source
    • Select series colors in BI
    • HogQL ambiguous query error when joining tables with the same field names
    • BI breakdowns

@Twixes Twixes changed the title Sprint Oct 28th-Nov 8th Sprint - Oct 28th-Nov 8th Oct 23, 2024
@Twixes Twixes changed the title Sprint - Oct 28th-Nov 8th Sprint - Oct 28 to Nov 8 Oct 23, 2024
@fuziontech
Copy link
Member

fuziontech commented Oct 23, 2024 •
edited
Loading

Team 🧊 Data

image

OKR Q2 2024

Objective

Goals for Q4:

  • Improve elasticity and flexibility of our data store by putting all our data in Iceberg
    • Work with Altinity effectively to ship read path for Iceberg on ClickHouse - Brett Hoerner
    • Setup infrastructure to ship all of our data to Iceberg on S3 - James Greenhill
    • Shipping Query logs to Iceberg - James Greenhill
  • Continue improving CH operational expertise
    • Upgrade to a later version of Clickhouse - James Greenhill
    • Capacity planning - James Greenhill
    • Automation - Daniel Escribano
    • Put some of the basic mitigation operations in runbooks - Daniel Escribano
  • Schema management
    • Tool for schema migration (coordinator schemas) - Daniel Escribano
    • Tool for long running mutations - Daniel Escribano
  • Continued investment in performance
    • Tooling for other teams to understand which queries are slow and why - Ted Kaemming
    • Investigate variability of queries - Ted Kaemming
    • Per-team limits on queries/query complexity (needs product work) - Ted Kaemming

Offsite week 2 Nov 4->8 in Miami!

Board

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

Retro

🔥 Outages 🔥

Last Sprint's Goals

This Sprint's Goals

TL;DR

Offsite

  • Eat Cuban Food @tkaemming
  • Hang out with Pitbull
  • Café Cubano
  • 360 Feedback session
  • Hackathon

@timgl
Copy link
Collaborator

timgl commented Oct 23, 2024

Team Infrastructure

Support hero: @xneyder

Retro

Hang over items from previous sprint

  • Item 1. prioritised/deprioritise

OKR

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

High priority

  • Finish ArgoCD migration @bciaraldi
  • Finish spot instances (at least for Decide and events, which are most expensive and can handle random load the best) @xneyder
    • After that see if we can convince Oliver/Paul to try it as well
    • Can use it for web
  • Reserve instances @xneyder
  • Move most web/workers to same AZ as Clickhouse + easy failover.

Low priority / side quests

  • Docker cache (working with Tom as warehouse still uses minio)

@jurajmajerik
Copy link
Contributor

jurajmajerik commented Oct 23, 2024 •
edited
Loading

Team Experiments

Retro

  • 🟡 ElevenLabs - risk of churning. Scrambling to implement holdouts with Neil before tomorrow's meeting with them - will be done.

  • 🟡 Continued on HogQL for Experiments (Experiments HogQL rewrite #24914) - good progress, 90% done - backend migration complete now, just need to finish the frontend.

  • 🟡 Review statistics with a contractor

    • going great, we have a shared Jupyter notebook where we're writing the new methodology. Making sure to understand everything to fully revamp docs once this is done.
    • focusing on 3 main metric types: funnel, count, numerical field value (e.g. revenue)

  • 🟢 Support hero for the Feature Success queue - workload very manageable

Sprint goals

  • $customer is the current priority
    • based on the outcome of tomorrow's meeting, we'll see what else needs to be done right now
    • reusable metrics they've been requesting are on my list already - this is the next step after HogQL migration
  • Continue HogQL rewrite
    • migrate UI behind a feature flag
  • Review the methodology with a statistician
    • discuss possibly measuring difference between averages (currently not working correctly), comparison between test variants

@Twixes
Copy link
Member

Twixes commented Oct 23, 2024 •
edited
Loading

Team "Do Androids Dream of Electric Hedgehogs?"

Retro

  • ✅ Router between AI agent's skills (trends, funnels, SQL, etc.) @skoob13

  • 🔴 Support for insight types @skoob13 @Twixes Rolling over due to support, deprioritized in favor of quality

  • 🔴 Basic SQL support @Twixes Rolling over due to support, deprioritized in favor of quality

  • ✅ Answer feedback buttons @Twixes

  • ✅ Extra from user feedback: Query definition preview @Twixes

  • 🟠 Environments out as a feature preview @Twixes Rolling over due to support

Objective

LLM-based product manager as a service

High priority

  • Funnels support @skoob13
  • Tune agent/prompt for more relevant results (primary: excluding most $-prefixed events/properties) @skoob13 @Twixes
  • Stream feedback on the agent's current task in conversation @Twixes
  • PostHog dashboard for AI product manager use @Twixes
  • Generalize Session Replay's OpenAI data processing opt-in (to be determined with @fraserhopper) @Twixes

Low priority / side quests

  • Results evaluation framework - a benchmark @skoob13
  • Environments out as a feature preview @Twixes

@aspicer
Copy link
Contributor

aspicer commented Oct 23, 2024 •
edited
Loading

Team Product Analytics

Support hero: @aspicer and @anirudhpillai 

Retro

Anirudh

  • ✅ Create snoozing mechanic for firing alerts
  • ✅ Launch relative alerts
  • 🟡 Roll out to more users (talk to comms about finding beta test customers)

Sandy

  • ✅ UDF rollout for steps + moving funnel trends to UDF
  • 🟢 Get a subset of cohorts calculating on HogQL

Next Sprint

Sandy

  • Support (7 days)
  • 24.8 query porting
  • Continue porting cohorts 

Thomas (Returns on Nov 4th!)

  • Resume filter to query work?

Anirudh (OOO through Nov 6th)

  • Support (3 days)

@robbie-c
Copy link
Member

robbie-c commented Oct 23, 2024 •
edited
Loading

Team web analytics

Support hero: @robbie-c

Retro

Made some progress on cookieless tracking, but was out sick for part of the sprint

Tasks

Cookieless prototype

  • 🟢 front end
  • 🟠 back end

🟢 Fixed a long term issue (Dec 2021!) around incorrectly setting initial campaign params on later visits

OKR

  • Continue to improve performance
  • Build a small amount of more advanced marketing features, to measure interest
  • Cookieless tracking
  • Improve the NextJS experience
  • More page-level insights
  • Improve the documentation, and link to it more from the app

High priority

  • Finish cookieless prototype
  • Onboard Mike / have a successful offsite
  • Finish up the PR to reduce writes to v1 sessions table by filtering team_id

@dmarticus
Copy link
Contributor

dmarticus commented Oct 23, 2024 •
edited
Loading

Team Flags

Support hero: mostly @jurajmajerik (old feature success team is sharing the same support queue until our newly split teams scale up)

Retro

(I had a limited sprint because I to go to a family funeral at the end of last week)

  • Didn't get much work done on OKR 1, mostly spent time on OKR 2 (maintaining old decide endpoint)
  • spent most of the sprint fixing issues, doing calls with customers, and then fixing more issues.
  • Finally paid down the outstanding support volume and have fixed some of the bugs that users were complaining about, so this sprint I'm hoping to double down on OKR 1 work

Things shipped

Things carrying over

  • Finish static and dynamic cohort matching for new feature flag service
    • support full subset of cohort match operations (not_in, etc) at the service/DB level

OKRs

  1. Ship new feature flags in production and accomplish the 10x scale + 2x speed boost performance targets (ideally decreases infra spend by N% as well, will try to figure out a more specific target going forward)
  2. Maintain current /decide service and make optimizations.

Sprint

High priority

  • Finish static and dynamic cohort matching for new feature flag service
    • support full subset of cohort match operations (not_in, etc) at the service/DB level
  • Prepare for Haven's onboarding in Seattle

Low Priority/Stretch Goal

  • Port over existing feature flag integration tests from the django to rust repo (lots of valuable alpha in our existing /decide tests, but this doesn't need to happen this sprint)

@marandaneto marandaneto unpinned this issue Nov 11, 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