57 lines
3.1 KiB
Markdown
57 lines
3.1 KiB
Markdown
|
# 20240913 Retro
|
|||
|
|
|
|||
|
|
## 🙌 What went well
|
|||
|
|
|
|||
|
|
- **dbt**
|
|||
|
|
- Improvement of performance on dbt project, had less incidents when running models.
|
|||
|
|
- dbt tests are working great
|
|||
|
|
- DBT automatic testing to detect shitty stuff going on
|
|||
|
|
- **Collaboration with teams**
|
|||
|
|
- Quarterly session with Tech team was a great thing to do
|
|||
|
|
- Nice discussions / alignments with TMT/Tech leads
|
|||
|
|
- Very nice internal Data Team collaboration!!!!
|
|||
|
|
- Nice advancements on aligning with Guest Squad (tracking, A/B testing, etc)
|
|||
|
|
- Data Comilonas <3
|
|||
|
|
- **Delivery**
|
|||
|
|
- We’re doing great in making the most out of our infra
|
|||
|
|
- Very glad to have Cosmos DB integrated into DWH and the following refactors to centralise efforts
|
|||
|
|
- Unleashing analytical capabilities with KPIs by Categories
|
|||
|
|
- Documentation keeps on being great, we’re being recognized as exemplary on it
|
|||
|
|
- Probation periods successfully passed!
|
|||
|
|
- Truvi logo is now readable (and cool)
|
|||
|
|
|
|||
|
|
## 🌱 What needs improvement
|
|||
|
|
|
|||
|
|
- **PBI Awareness/know how**
|
|||
|
|
- Lack of knowledge of “this data is available in this report”
|
|||
|
|
- Spread more knowledge on (1) what PBIs we have + (2) best ways to use them
|
|||
|
|
- I suspect a lot of reports are being super-underused, but we can’t monitor that easily
|
|||
|
|
- PBI users need to have more knowledge as to where and how they can get the data they need
|
|||
|
|
- **Data Contracts/Issues with Tech**
|
|||
|
|
- Docs and comms with Tech team are not on their best spot + we might need to raise this more loudly and frequently + no clear visibility on every time tech is impacting data
|
|||
|
|
- Shitty stuff happens on Tech deployments:
|
|||
|
|
- 27th August Check-out Bookings and Cancelled Bookings fake increase because of PMS issues. The later, the issue still persists
|
|||
|
|
- New Dash MVP migration on 10th of September broke the report despite anticipating the changes needed from dev team
|
|||
|
|
- Remind development to not change tables or adding test data without our knowledge
|
|||
|
|
- A bit stressed of not knowing when/if we’ll have a Data Engineer position opening soon
|
|||
|
|
|
|||
|
|
## 💡 Ideas for what to do differently
|
|||
|
|
|
|||
|
|
- Incentivise people to use the Data Request for ad-hoc requests and asking for permissions
|
|||
|
|
- Explore the possibility to have a “report” to check PBI report usage
|
|||
|
|
- Have a PBI 101 class for users
|
|||
|
|
- Since we rarely have incidents, we might need to cause them to grease the groove
|
|||
|
|
- Open Data Comilonas with different stakeholders and colleagues from time to time (it was nice with Joan!)
|
|||
|
|
|
|||
|
|
## ✔ Action items
|
|||
|
|
|
|||
|
|
- [x] Programar Data Comilona
|
|||
|
|
- [x] Pablo schedules his Chaos Monkey role
|
|||
|
|
- [x] Research if there is any better way to monitor PBI report usage
|
|||
|
|
- [ ] Schedule harsh therapy session with Lou
|
|||
|
|
- [ ] 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
|