Global Sprint Planning

• Having one or more huge headline goals per sprint to push our ambition (50:50)

Retro: Status of Outcomes from Previous Sprint

1. ✅ Quantitative Analysis (Owner: @neilkakkar) - Basic MVP behind a feature flag by the end of sprint - infront of some specific users (users from paths engagement) - design works in parallel
   • 🎯Goal: _Be able to understand the top 3 properties or events that signal failure in the activation flow of PostHog
   • through a production-ready MVP._
   • Status: It looks not great, but this capability now exists^. We'll be talking to users & gathering feedback before we iterate further on it.
2. ✅ Paths User Experience (Owner: @EDsCODE ) - Get people to use it and more feedback and iterate on it
   • 🎯Goal: Get 5 users to use new features for more than 1 day.
   • Status: Released. Sitting tight waiting for users to flow through. We released to 50% of all users and got a few dozen visits the first day. Will continue to monitor follow up users. Goal is 5. What's paid and what's not paid?
3. ✅ Ingestion Data Integrity (Owner: @yakkomajuri) - Ensuring we can easily track and recover dropped events
   • Status: We're on track to meet the goal by end of week
4. 🔁 Groups - Interview customers, verifying our assumptions/showing proof of value + understand feature flag + groups story better. Group Analytics Questions Group Analytics Questions #6189
   • Start implementing, build an MVP with 1-2 client libraries accessible for our team behind a feature flag during the sprint -
   • Status: Interviews done, MVP implementation started - too much for this sprint to finish goal
5. 🔁 Session Recording? (Owner: @rcmarron ) - Ship a complete "session recordings" page (and make it easy to find sessions) and an updated playback experience (close open issues - solve the epic)
   • ✅ 🎯Goal: Two main ingestion errors completely gone (1 & 2). Note: Consider sentry2 too.
   • 🔁 🎯Goal: 80% of the time I should be able to find the part of the session I care about within 5 seconds. Measured via internal tests.
   • Status: Ingestion bug 1 is fixed + ingestions bug 2 is on track to be fixed. We made progress toward the 5-second goal (buffering of recordings is on track), but have more work to do on the UX for ‘finding the right moment’.
6. ✅ Refactor and test insights logic? (Owner: @mariusandra) - Our additive and testless development style has resulted in various insights and dashboards behaving erratically (borked reloads, white screens, etc). It's time to clean house.
   • Status: Did two huge refactors, which cleaned house a lot and also fixed few bugs. Still the "url too long" issue to fix Thursday, with related refactors. Follow up work can be rolled into other tasks, so on track for completion this sprint.

Retro: What can we do better next sprint?

Focus on what went well and can improve for Quantitative Analysis? @neilkakkar @hazzadous @clarkus @EDsCODE @paolodamico feel free to update this comment in advance with your thoughts.

1. Doing design & MVP in parallel: We haven't yet figured out the final design, but we still have something up on Production to play around with. This was great - it allowed me to gather feedback quickly and fix data issues while the design is coming along. General learning: When you need production data to test how a feature is doing, bias towards getting a crap version ready ASAP.
2. Using the product more aggressively - everyone should do that
3. We left the usability tests towards the end - next time: schedule usability tests early on - no reason to wait

Sprint priorities
4. We did not meet all the goals we set out to do:
- Groups: Intention was to have a moonshot - as opposed to a rooftop
- Recordings: Bit off more than we could chew - we did not account for Alex being support hero - Michal was out - we weren't explicit enough within the team when we set them (more explicit about resources for the team) - We should assume ZERO product work for support hero @liyiy @timgl
- The owner should ask for more resources or share we're not on track - we should be more explicit about that

Plan: Proposed Goals for Next Sprint

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

1. Correlation Analysis (Owner: @neilkakkar) - Ship the best Quant analysis tool in the industry (50:50) (@paolodamico @neilkakkar)
   • Why? We've already made significant progress here and are close to what our competitors are offering - we should identify the gaps in our competitors offering and ship a tool without those gaps and something no-one else has
2. Data Integrity Querying (Owner: @EDsCODE) - Resolve and build robust tests for all known query inconsistency issues affecting persons modal (@marcushyett-ph @EDsCODE) (+ cohorts are accurate)
   • Why? Identified in the data integrity strategy as critical and from recent customer feedback causing users to lose trust
3. Data Integrity Ingestion (Owner: @yakkomajuri) - Nail ingestion data integrity (50:50) (@marcushyett-ph @yakkomajuri)
   • (Owner: @yakkomajuri ): "Ensuring Postgres and CH persons are fully in sync"
   • (Owner: @tiina303 ): "Allowing events to be ingested in any order"
   • Why? Following incidents with data ingestion, ingestion reliability remains a top priority for our customers
4. Recordings (Owner: @rcmarron)
   • Why? The session recording experience is unreliable and underused - and key to diagnose causes.
   • 🎯 Goal: 99% of session recordings have a full snapshot (and are therefore not missing)
   • 🎯 Goal: 80% of the time I should be able to find the part of the session I care about within 5 seconds. Measured via internal tests. (continued)
5. Groups (Owner: @macobo) - Full group analytics support enabled for 5 alpha customers (+ release plan) (@marcushyett-ph @macobo)
   • Why? We have validated this with 5+ of our customers and theres a definite need for for the capability to analyze based on groups

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

-

### Low priority / side quests

-