PostHog / posthog

πŸ¦” PostHog provides open-source web & product analytics, session recording, feature flagging and A/B testing that you can self-host. Get started - free.
https://posthog.com
Other
22.32k stars 1.35k forks source link

Sprint - Aug 19 to Aug 30 #24364

Closed marandaneto closed 2 months ago

marandaneto commented 3 months ago

Global Sprint Planning

3 things that might take us down

  1. infra inconsistencies EU/US - next sprint to upgrade dev in US to 23.12.something

Team name game score

7 out of 9 are doing great. Noice.

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

-
marandaneto commented 3 months ago

Team ~Replay~ Full team!

Support hero: @marandaneto

Retro

High priority

βœ… done 🟒 in progress, on track 🟑 in progress, off track πŸ”΄ missed

Low priority / side quests

OKR

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

High priority

Error tracking

Low priority / side quests

benjackwhite commented 3 months ago

Team Continuously Deploying Patches

Support: @benjackwhite

Retro

High priority

OKR

(to be refactored)

High priority

benjackwhite commented 3 months ago

Team Infrared

Retro / hangover

OKR

  1. 🦹 Zero-trust security 🟒
  2. πŸ€“ 10x Developer Experience 🟑
  3. πŸ’ͺ Every service lives and dies alone 🟒
  4. πŸ’° Save big on cost 🟑

High priority

Phanatic commented 3 months ago

Team Feature Success

Support hero: @jurajmajerik

Retro

βŒ› No-code experiments : @Phanatic βœ… Customer Support, build some metrics @Phanatic βœ… Fixing request parser errors: @dmarticus βœ… Define mid-term success for feature flags rewrite: @dmarticus βœ… Experiment confidence intervals @jurajmajerik βŒ› Release the winning variant

Side Quests


OKRs

  1. Make sure feature flags can handle 10x current scale
  2. No-code experiments ~3. Split out experiments into its own product~

High priority

fuziontech commented 3 months ago

Team Click Haus, Haus of the Hogs

OKR Q2 2024

Objective

James as a Service -> Clickhouse as a Service

Board

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

Retro

@Daesgar - OOO this sprint

@fuziontech - Really great sprint - with @Daesgar focusing on the green field projects I've been able to dive deep into a few things that have needed attention for some time. A lot of progress on deletes (teams and person deletes are working mostly) and incidents have gone relatively fast. Performance work is especially exciting.

Board Snapshot

image
EDsCODE commented 3 months ago

Team Data <->

OKR Q2 2024

Objective

Query 3000

Data Modeling MVP

Retro

High Priority

Eric off first week

raquelmsmith commented 3 months ago

Team Growth

Retro

Retro items - @raquelmsmith - [x] Support this week, Out next week - [x] Launch / announce personless - [x] Fix shenanigans with session replay pricing update - [x] Fix monthly enterprise customers revenue issue - https://posthog.slack.com/archives/C043VJ93L3B/p1721940308706669 - [ ] Set up billing alerts - [ ] Add LLM usage to usage reports for Lior - @zlwaterfield - [x] sentry profile / perf clean up - [x] subscription cancellation reasoning dropdown - [x] ICP score research - how is it calculated, where is it stored, when is it accessible, does it align with current views of ICP? - [ ] billing limit to numbers - [ ] teams annual plans - [ ] SAML tests - [ ] startup plan credits linked to infra cost - bonus - [x] org user syncing to billing

Q3 Goals

βœ…=finished 🟑=in progress πŸ”΄=won't finish βšͺ=not started

  1. 🟑 Make onboarding awesome for Product analytics and Data warehouse (Raquel)
  2. 🟑 Support self-serve annual commitments (Zach)
  3. 🟑 Dive into the data to understand our billing metrics and customers better (Zach)
  4. βœ… Launch pricing for data warehouse (Raquel)
  5. 🟑 Hire 2 people (one for billing, one for auth/permissions focus)

This sprint

Time off: Raquel out 1 day

(This is probably too much for this sprint.. listed in roughly priority order)

Twixes commented 3 months ago

Team Analytics of the Product

Support hero: Georgiy + Thomas + probably Anirudh Off: Michael second week, Thomas second week and beyond, Anna 1 day. Also Julian's off for parental leave beyond this sprint.

Retro

We had an offsite, hacked some things together. Retro issue on this pending.

OKR

  1. Rock-solid analytics (@thmsobrmlr + @webjunkie + @aspicer + @anirudhpillai)
    1. 🟒 Legacy Minus – removing legacy insights code so that we can move fast
    2. 🟠 Tests Plus – shipping fewer bugs in the first place.
    3. 🟠 Metrics Plus – catching issues before before users report
    4. 🟑 Performance Plus - eliminating UX pain via maximum query performance/reliability, based on Metrics Plus data
    5. 🟒 Support Plus – sparking joy for users when they’re led to report a bug
  2. Answering more product questions, deeper (@thmsobrmlr + @webjunkie + @aspicer + @anirudhpillai)
    1. πŸ”΄ Growth Plus - increasing ease of onboarding, and subsequent retention
    2. 🟑 Analysis Plus - answering more product questions, more deeply
  3. 🟑 ArtificialHog (@Twixes + @skoob13) – an LLM-based chat-like interface for answering product questions.

High priority

Low priority / side quests

robbie-c commented 3 months ago

Team Analytics of the Web

Support hero: @robbie-c

Retro

Sessions v2 table is backfilled up to last weekend on US, but not ingesting new events: just need some help from team-clickhouse to get the MV back (it was deleted as part of an incident (it didn't cause the incident)).

I started thinking about the saving of filters / web analytics state and realised that I probably want to do conversion events first, plus I've had quite a few customers asking for this recently (and it was already on my roadmap). So I've been doing this first.

Planned Tasks

🟒 Figure out what's going on with cross domain tracking problems - it was user error! Added a way of debugging customer's implementations on their site, even when installed via npm πŸ”΄ Come up with a solution for a few linked issues: people want a default set of filters, and people want it to be easier to separate their sites. Postponed behind conversions 🟑 Conversion events tile and page-level filters 🟑 Finish backfill on US and switch over to sessions v2 for everyone.

Bonus stuff

🟒 Session replay tile in web analytics (and error tracking) 🟒 "Time on page" in posthog-js 🟒 Better bot filtering 🟒 Improve the deprecation modal, use deprecation info that already have in posthog-js repo, add it to web analytics

OKR

  1. Make querying fast enough for large customers
  2. Heavily requested features
  3. Work better with other products
  4. Product and growth

High priority

Stretch goals