pages

notion_data_team_no_files/20240819 Retro 88ed749ed43b4eb7a2d277ddd2b03747.md

@@ -0,0 +1,61 @@
+# 20240819 Retro
+
+## 🙌 What went well
+
+- **Holidays reliability**
+    - Surviving even without the whole team
+    - Survived holidays without issues
+- **Methodology**
+    - We keep on having a lot of freedom and we are using it nicely
+    - Quality and methodology stays high
+    - Capacity to investigate new tools/methodologies (CosmosDB integration, Metric Flow)
+    - More contact with development team
+    - Keeping up with our documentations and pressing other teams to do the same
+    - We are pushing the documentation culture and leading with example
+- **Stakeholders**
+    - Product initiatives should be now estimated and prioritised based on Revenue with the help of the Data team
+    - Increased access to Business Overview for PMs
+    - Our customers are very happy with us and our work is appreciated
+    - Company is starting to appreciate that data is not the owner of invoicing
+
+## 🌱 What needs improvement
+
+- **Dev env, data infra**
+    - Capacity to run models in local and not running out of memory
+    - Lack of automation around tests, CI, manual stuff
+    - Local development keeps on being a bit of a pain in the ass
+    - Data platform is growing a lot of mushroom components
+- **Priorities/Backlog**
+    - We're going to have a lot of shadow work this quarter with New Dashboard and APIs: we should make it more visible towards TMT
+- **People doing crappy stuff**
+    - Still some shitty initiatives are happening on top of supposedly “well built projects” (Grand Welcome Invoicing, MVP launch with bugs and without documentation, issues with check-in hero, etc.)
+    - We are pushing the documentation culture and leading with example
+    - Lack of technical documentation from development team, specially impacting on holidays period
+    - Product/Engineering has made failures and used bad methodologies in different ways that will cost us expensive
+    - Incidents go unnoticed generally on backend side
+- Reduce bus factor on key projects (for instance, invoicing)
+- Lack of synchrony with some initiatives: New Dash MVP misunderstanding on deliverables, Revenue figures mismatch took quite a bit of time to align with Finance
+
+## 💡 Ideas for what to do differently
+
+- ~~Having access to all documentation from development team (confluence)~~
+- Treat Backlog/Todos columns in board with a bit more respect (bi-weekly grooming?)
+- Ensure that there’s minimum description and DOD on tickets
+
+## ✔ Action items
+
+- [x]  Run invoicing for september all together holding hands
+    - [x]  Invite sent
+- [x]  Run MainKPIs training sessions for PMs/Other audiences
+- [x]  Set bi-weekly grooming session
+- [x]  Plan Data <> Tech team council of wise men on a quarterly basis
+- [x]  Document progress towards quarterly goals (emphasis on unplanned work)
+- [x]  Fix dbt alerts
+- [ ]  Agree with Ben R. on a different way to manage permissions PBI
+- [x]  Explore **local** environment postgres improvements
+- [x]  Create Ticket to document KPIs dbt area
+- [x]  Checklists for dbt repo
+    - [x]  and pbi repo
+- [ ]  Potentially, also include CI checks in dbt repo
+- [ ]  Make a cleaning day for Data Catalogue docs
+- [x]  90 minutes retros