3.1 KiB
3.1 KiB
20250319 Retro
🙌 What went well
- We can live without Pablo
- Welcoming back Pablo with nothing burning
- You guys have chewed through my leave wonderfully. Everyone happy and nothing has exploded. Good job!
- Company situation
- Clearer company strategy
- It seems the dust has settled after the December/Jan company changes.
- Data team has clearly been positioned as an important one in Truvi and we're on the table to decide where the company is going
- Deliveries
- Good advance with new reports (Churn Report, Resolutions)
- New Main KPIs tab with targets and performance MTD & YTD
- Excel training session
- Data-driven alert spotting and communication (HTVR)
- Work with other teams
- Good organization between us and Matt to decide work priorities
- Good collabs with Alex & Nathan
- So far good adaptation to Truvi rebranding, though there is still work to be done.
🌱 What needs improvement
- Company org and ways of working
- Lack of communication of how is the hierarchy with recent changes
- Many opened frontlines / context switching (despite it has reduced in the latest weeks)
- Company organisation after RIF is still not clear, specially on Product side
- Many fires still in Tech side
- I don't see initiatives on the table that I feel will move the needle
- Though training sessions of excel and power bi, help we need to find ways to make them more engaging for the users
- We need more engineering skills within the team (despite nothing really extremely was broken in Pablo’s absence)
💡 Ideas for what to do differently
- Folder and naming convention in DWH → we have CosmosDB + Core cases that end up in a Athena/E-Deposit/CIH/Resolution folder
- Copilot paid version
✔ Action items
- Get Copilot paid version
- Think about changing dbt model naming/structure conventions
- Should
int/crossbe split into… something?
- Should
- Request TMT clarity on org. structure again
- Read Shape-up (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?)
- 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
- Discuss with Ben C. New Dash retrospective with PMs/Dash Squad/Data by the EOY