pages

notion_data_team_no_files/20241008 Retro 1190446ff9c9807982abfe76f161994f.md

@@ -0,0 +1,46 @@
+# 20241008 Retro
+
+## 🙌 What went well
+
+- **Team and Jarana**
+    - Data Comilona + Meetup = Nice combo! +1
+    - We survived the period without Ben
+- **Data Platform**
+    - No more dumps <3
+    - First usages of dbt versioning have worked nicely
+    - dbt testing is working nicely so far
+    - Performance and DevEx improvements in both production and dev environments have made things much better
+- **Delivery**
+    - Hubspot integration in progress
+    - Data requests feedback was very positive
+    - KPIs sessions with PMs were quite insightful
+    - Q3 was closed with success and everyone is happy, plans for Q4 are clear and aligned with everyone
+    - Business Overview PBI app looks very good after latest changes from Joaquin
+- **Stakeholders**
+    - New Dash/New Pricing much better communication with Product/Tech teams
+    - Very happy to see that data quality improvements are being prioritised in Guest Squad (GJ completion date)
+
+## 🌱 What needs improvement
+
+- **DE Vacancy**
+    - Data engineer vacancy
+    - Timing for Data Engineer is looking ugly
+- **New dash**
+    - Still it’s quite confusing and time consuming to work on New Dash/New Pricing
+    - New Dash/Tech/Product drama
+- **Other**
+    - Edeposit invoicing misunderstanding
+
+## 💡 Ideas for what to do differently
+
+- 
+
+## ✔ Action items
+
+- [ ]  If Data Engineer vacancy doesn’t progress by end of september, pursue sign-off on consequences
+- [ ]  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