sh-notion/notion_data_team_no_files/20241210 Retro 1580446ff9c9803ea397d22f31bade85.md
Pablo Martin a256b48b01 pages
2025-07-11 16:15:17 +02:00

3.5 KiB
Raw Permalink Blame History

20241210 Retro

🙌 What went well

  • Delivery
    • Good advance with KPIs reporting
    • A/A test showed there were some improvements needed in the tracking and Guest Squad quickly fixed it
    • Check-in hero & S&P integrations to DWH went smoothly
    • Migration of Athena CosmosDB container went smoothly
    • You guys (J&U) have been rocking it
  • Methodology
    • Quiet days are being helpful. More?
    • Documentation keeps helping us a lot
    • dbt docs working perfectly
    • Anaxi and Infra documentation is absolutely perfect for dumb analysts like Uri to handle actual DE work effectively
    • Tagging unplanned work in a dedicated epic to wrap up EOQ
    • Very good collaboration with APIs and Guest Squads
  • Fun
    • Cube and rollup workshop in love
    • EOY social activities (Quiz, Escape Room, Dinner)
    • Glad to see some upcoming python usage
    • And notebooks are very cool (used properly)
  • Domain analysts program +1

🌱 What needs improvement

  • Methodology
    • Huge amounts of unplanned work - not being able to fully reach Q4 objectives
    • Very reactive quarter: spinning from one fire to the next
  • Keeping things tidy
    • Going crazy with PBI permissions: invisible tangle of who has access where
    • Having a better way to follow up on the usage of reports to see which ones are relevant
    • We are not doing great with cleaning up old stuff, tends to stick around permanently
  • Tech change management from MS Server changes side
  • New Dash reporting is still facing data quality issues from the source and its not prioritised
  • Cachondeito
    • Moar comilonas.
    • Kind of miss the office (an office and the bars, not Norssken specially)

💡 Ideas for what to do differently

  • Change planning and organization to be a tad less reactive, have more time to tidy things up? Shape up? Change Data Captain role?
  • Kill SH legacy reporting to avoid confusion on KPIs
  • More syncs with RevOps (we do tons with Product, a bit with Finance, RevOps is the long forgotten son)
  • Put some order in our Notion
  • Make retros 2h

✔ Action items

  • If Data Engineer vacancy doesnt progress by end of september, pursue sign-off on consequences
    • Reassess DE plans
  • Retro with Ben C. around planning practices (centralization is not working, changing scopes too fast, etc).
    • Quiet Tuesdays and Quiet Thursdays
      • Move calendar recurring meetings
      • Give Ben C. a heads-up
  • 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