20240611 Retro

🙌 What went well

Priorities and capacity
- Data team has increased in capacity
- TMT has a lot more visibility and alignment with us
- We’ve done a good job at structuring demand and ****keeping pushy stakeholders at bay
- Adhoc/Data Captain deliveries have been flowing orders of magnitude better than in the Pablo-era
Team organization is working well
- Internal collaboration is quite smooth so far (we’re good people 🙂)
- VERY GOOD documentation in Notion, repositories, etc. on the Data stack
- The way we are organizing the team and distributing the responsibilities, I really appreciate the tools we are using like the board that makes very easy to keep track of everyone's assignments.
- I think the dailies are also very helpful to stay in contact and updated to what everyone is doing in their day to day work
I feel very comfortable with the team and the disposition of everyone to be very helpful inside and outside the office.

Development workflow in dbt / PBI could be more agile and frictionless
Stakeholder visibility/relationship with other teams
- Clear lack of data exposed / reported to business and product teams
- Backlog of engineering dependencies/topics is messy and we drop balls
- Data priorities and tempos visibility to the rest of the business
Data modelisation problems from the source (ex: guest journey end date needs tons of logic because it was not properly implemented, expected revenue figures, sources of Hosts, etc)
To have a documentation of all the data we can work with, maybe of the source tables.

Tooling
- More hands-on development onboarding for Data
- A bit complicated to review PBI reports - ensure these are exposed in our workspace for Data team reviews?
More connection with the engineering team
Start running dbt tests in production
Reduce bus factor for Data Engineering

543057