search

PostHog / posthog

🦔 PostHog provides open-source product analytics, session recording, feature flagging and A/B testing that you can self-host.
https://posthog.com
Other
20.94k stars 1.24k forks source link

Sprint Sep 19 - Sep 30 #11822

Closed timgl closed 1 year ago

timgl commented 2 years ago

Global Sprint Planning

3 things that might take us down

Last week

  1. Rate limiting API requests - @rcmarron to figure this out, just target clickhouse

Retro: Status of Outcomes from Previous Sprint

can only be an engineer.

  1. Add session recording billing @kappa90 -> working on it, scope has increased a bit, but we'll end up with a future proof system.
  2. Continue bugbashing. @mariusandra to provide a list on Friday. Timebox to this sprint https://github.com/orgs/PostHog/projects/58/ -> 8 more bugs done, 5 in progress, 2/3 finish this sprint. They're big bugs. why: Make sure we have a great experience + increase retention
  3. $create_alias deprecation @yakkomajuri -> instrumented metrics, talked to users. Lots of users using this. why: to roll out persons on events
  4. PostHog EU (ClickHouse / Zookeeper production ready, runbooks, + other services if possible) @ellie -> up and working! Small things to iron out, load testing, then get beta testers on next week! why? to increase usage from customers that need EU cloud
  5. Harry: investigate latency issues and random error rate increase @hazzadous -> Resolved.
  6. Session recording event log filtering in playlist @alexkim205 -> No progress. Will get this out next sprint. why? Make our session recording experience comprehensive/competitive
  7. Complete person on events rollout @EDsCODE. -> backfilling for person/group properties didn't work. Digging into this. why? To unlock scale & quicker queries
  8. Feature Flags: posthog-js and react-native bootstrapping, server side override, GeoIP overrides for everyone, and UX issues: audit history, feature flags on person @neilkakkar -> the whole list is sorted. Why? To make our feature flag competitive

Retro: What can we do better next sprint?

1. 2. 3. 4. 5.

Support hero this sprint

Week 1: Karl Week 2: Li

Plan: Proposed Goals for Next Sprint

Each goal should have a single owner. Owner can only be an engineer.

  1. Text tiles on Dashboards with our team and beta users @pauldambra Why? People asked for this
  2. re-re-re-naming calculated events @mariusandra why? Ongoing confusion, Annika has done good work so we can solve this
  3. Debug and re-run persons on events backfill @yakkomajuri (for now) why? To speed up queries
  4. Deprecate $create_alias @yakkomajuri why? So we can release persons on events
  5. 🇪🇺 EU plan and build out testing framework for load for new infrastructure (both ingestion and query side) @ellie why? New infra so we want to test this
  6. Continue improving visibility and making loki logging more scalable @hazzadous why? Because Loki isn't reliable, because we have problems that we can't debug.
  7. Continue supporting person on events rollout where possible @EDsCODE why? To speed up queries
  8. List of clean up tasks for team west @liyiy @neilkakkar @EDsCODE why: very little capacity based on schedules
  9. Getting new PlaylistView out for session recordings @alexkim205 why? so people can binge more recordings
  10. PoC of Billing service @kappa90 why - Getting Billing right ASAP will start unlocking revenue for SeshRec™️

Team sprint planning

For your team sprint planning copy this template into a comment below for each team.

Team ___

## Retro

<!-- Talk about what went well, what didn't go well and any actions to improve next time -->

- 

## Hang over items from previous sprint

<!-- For each item, decide to re-prioritise (and add below) or deprioritise -->

- Item 1. prioritised/deprioritise

## Planning

<!-- Each item should have a single owner. Owner can only be an engineer. -->

### High priority

-

### Bugs

-

### Low priority / side quests

-
pauldambra commented 2 years ago

Team East

Retro

Hang over items from previous sprint

Continue bugbashing. @mariusandra to provide a list on Friday. Timebox to this sprint https://github.com/orgs/PostHog/projects/58/ why: Make sure we have a great experience + increase retention

Planning

We have one week of the sprint and then offsite week in Rome

High priority

Bugs

yakkomajuri commented 2 years ago

Team Ingestion

Retro

Goal: Stay afloat + create_alias deprecation

Goals

  1. Kafka queue for jobs @yakkomajuri
  2. Debug and re-run persons on events backfill @yakkomajuri (for now)
fuziontech commented 2 years ago

Team Infrastructure

Retro

Harry - Events in EKS! 🥳 It's been a struggle trying to keep the infra from collapsing (logging). Firefighting bits and bobs. Everything is a blur. What did we even do? Yakko - Goal: stay afloat. Outcome: Still dry. Didn't have anyone to work with for spec-ing which was not idea. Person on events has a few bugs that need to be investigated. How deep into the weeds should he go into to make sure everything goes perfectly Ellie - PostHog EU IS SHIPPED!! 🚀 Logging is working as well which is amazing. Sounds like a great sprint Guido - Mainly worked on PostHog EU. Very happy with working with Ellie and Harry. Generally happy. So far support hero has been ok, but it's getting a bit busy.

Important bits

Hang over items from previous sprint

Planning

EDsCODE commented 2 years ago

Retro:

Planning: Li on support the second week Eric doing release on the second week Neil off first week + half of second week

Related work:

benjackwhite commented 2 years ago

Team ~SeshRec~ Recordings

Retro

Hang over items from previous sprint

Planning

  1. Off-board Ric successfully! @benjackwhite why - This is our last opportunity to learn from the master 😍
  2. PoC of Billing service @kappa90 why - Getting Billing right ASAP will start unlocking revenue for SeshRec™️

High priority

Bugs

Low priority / side quests

-