61 lines
3.1 KiB
Markdown
61 lines
3.1 KiB
Markdown
|
# 20250214 Retro
|
|||
|
|
|
|||
|
|
## 🙌 What went well
|
|||
|
|
|
|||
|
|
- Pablo had a child ♥️
|
|||
|
|
- Managed to survive and still get a lot of work done without Pablo
|
|||
|
|
- Good organization and staying in touch with each other
|
|||
|
|
- Office & Fun
|
|||
|
|
- One of the best comilonas so far (upcoming vegetarian next week)
|
|||
|
|
- New office is cool and much more convenient
|
|||
|
|
- We have Cobee now!
|
|||
|
|
- Delivery
|
|||
|
|
- Solved all invoicing problems and urgent fires
|
|||
|
|
- TMT is happy with us so we can feel confident we are doing well
|
|||
|
|
- Updated all Legacy report still in use so we won’t discontinue
|
|||
|
|
- Nice analysis
|
|||
|
|
- New metrics and visualizations in Main KPIs looking great
|
|||
|
|
- A/B test had good results
|
|||
|
|
- New Dash is growing more and more
|
|||
|
|
- Company is focusing on setting a strategy and key levers
|
|||
|
|
|
|||
|
|
## 🌱 What needs improvement
|
|||
|
|
|
|||
|
|
- Pablo is not here
|
|||
|
|
- Massive context switching and pressure handling
|
|||
|
|
- Lack of Engineering capability to do engineering work + challenge architectural decisions
|
|||
|
|
- Airbyte CPU close to 100% for several weeks went unnoticed (though nothing broke)
|
|||
|
|
- Other teams asking things we can’t handle (or will take a lot of time) because we don’t have an engineer despite all of this being discussed previous to Pablo’s departure
|
|||
|
|
- RiF + additional people leaving:
|
|||
|
|
- Unclear restructure, responsibilities, points of contact. Specially on Product team
|
|||
|
|
- Unclear transition of Data team to RevOps
|
|||
|
|
- There is a lot of insecurity as to how this will all keep on working with so many people being released or quitting
|
|||
|
|
- Delivery
|
|||
|
|
- Old dash invoicing issue
|
|||
|
|
- People still asking for some adhoc request not through data captain
|
|||
|
|
- Late dbt run production failures
|
|||
|
|
- A/B test miscommunication / lack of certainty
|
|||
|
|
- Priorities in some teams don’t seem to be very aligned yet with the recently presented north star
|
|||
|
|
|
|||
|
|
## 💡 Ideas for what to do differently
|
|||
|
|
|
|||
|
|
-
|
|||
|
|
|
|||
|
|
## ✔ Action items
|
|||
|
|
|
|||
|
|
- [x] Retro with Ben C. around planning practices (centralization is not working, changing scopes too fast, etc).
|
|||
|
|
- [x] Quiet Tuesdays and Quiet Thursdays
|
|||
|
|
- [x] Move calendar recurring meetings
|
|||
|
|
- [x] Give Ben C. a heads-up
|
|||
|
|
- [ ] Read Shape-up ([https://basecamp.com/shapeup/](https://basecamp.com/shapeup/)) and discuss next retro
|
|||
|
|
- [ ] Fuse Comilona and Retro and schedule for Monday 13/01 and make retros loooonger (2H)
|
|||
|
|
- [ ] Sketch roughly formalization of Domain Analysts programme
|
|||
|
|
- [ ] Discuss and agree with Tech team on data-alerts onboarding (should they be there? who should we tag?)
|
|||
|
|
- [x] 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
|
|||
|
|
- [x] Discuss with Ben C. New Dash retrospective with PMs/Dash Squad/Data by the EOY
|