pages

notion_data_team_no_files/20241112 Retro 13c0446ff9c980b0a942d10a7c68583c.md

@@ -0,0 +1,60 @@
+# 20241112 Retro
+
+## 🙌 What went well
+
+- **Incident Mgmt**
+    - Outlier tests in Main KPIs work surprisingly well
+    - Problem detection and resolutions
+    - We keep on spearheading incident management and doing things right
+    - Incidents are finally hurting enough for TMT to pay (some) attention
+- **Deliveries**
+    - KPIs refactor, including daily modelisation +1
+    - Integration of Hubspot into DWH
+    - Account Managers report (prev. Top Losers) being extremely useful and used by RevOps teams
+    - Churn rate metrics computation
+    - Starting Guest KPIs in new KPI modelisation
+    - GUEST TAXES CROSSCHECK FINISHED (AT LAST)
+- Last Comilona was AMAZING
+- Domain Analysts advancing well +1
+- GJ A/B test alignment sessions
+- Guest squad is doing the Lord’s work
+- Not impacted by layoffs
+
+## 🌱 What needs improvement
+
+- **Incidents**
+    - Persistent bugs in BookingToProductBundle
+    - Old invoicing incident
+        - + generally a lot of incidents all over the place
+- **People**
+    - Layoffs communication sourness
+    - Lou D. leaving us
+- **Priorities and planning**
+    - Tons of unplanned work - delaying other deliverables for Q4 +2
+    - Q1 company priorities still mostly focus on deliver new stuff rather than fixing core business
+        - + general misalignment between TMT and boots on the ground
+- Data Engineer vacancy not filled by now clearly impacting Q1 +2
+- Some Data Requests do not reach the channel, needs investigation
+- General doomloop sourness around New Dash, with no light at end of tunnel
+
+## 💡 Ideas for what to do differently
+
+- New Dash retrospective with PMs/Dash Squad/Data by the EOY
+- CI/CD checks on DWH complete PR button to ensure branch is up-to-date with master branch
+- Modify data captain distribution
+- Include Tech Team in data alerts channel and tag them
+- Propose and discuss how to align with Tech team to avoid context switching and optimise time and effort
+
+## ✔ Action items
+
+- [ ]  If Data Engineer vacancy doesn’t progress by end of september, pursue sign-off on consequences
+    - [ ]  Reassess DE plans
+- [ ]  Discuss and agree with Tech team on data-alerts onboarding (should they be there? who should we tag?)
+- [ ]  Think about how to make some kind of “PBI Homepage” where Superhog personnel can find all the PBIs that are available easily
+- [ ]  Document all the config references (URLs, DB connection strings, credentials, etc)
+- [ ]  Agree with Ben R. on a different way to manage permissions PBI
+- [ ]  Potentially, also include CI checks in dbt repo
+- [ ]  Make a cleaning day for Data Catalogue docs
+- [ ]  Document existing invoicing processes, not just new ones
+- [ ]  Azure DevOps checks on DWH complete PR button to ensure branch is up-to-date with master branch
+- [ ]  Discuss with Ben C. New Dash retrospective with PMs/Dash Squad/Data by the EOY