sh-notion/notion_data_team_no_files/20240709 Retro 6c815a39840f408fbd935c4b3e937be3.md

20240709 Retro

🙌 What went well

• Delivery
  • Huge advancements on reporting capabilities (KPIs, Xero, Check in Hero, currency conversion)
  • Important/critical data captain subjects moving forward
• Stakeholders
  • Good organization and advancing with tasks, good feedback from outside
  • Priorities setting and alignment with stakeholders is now much leaner and efficient
  • Awareness campaign with engineers around breaking stuff in Core
• Internal
  • Data Engineering super fast survival training program
  • High quality approaches to tough bones: incidents, refactors, etc.

🌱 What needs improvement

• Platform
  • Data drift is happening and we have no scheduled full-refreshes
  • Dbt run in production not displaying alerts
  • PBI Licenses/Group permissions are a (invisible) ball of hair
  • Full-refreshing in local reaches the error “could not resize shared memory segment "/PostgreSQL.4065550950" to 907743232 bytes: No space left on device”
• Documentation
  • Documentation on business KPIs, both technical (for Data) and broadly for consumers
  • We’re dropping balls with some conventions (exposures documentation, keeping data catalogue up to date, etc)
• Exploration of tables to check which ones have incomplete, outdated or wrong data
• Not all stakeholders use the data request form still

💡 Ideas for what to do differently

• Hands-on knowledge sharing by diversifying working scopes (I feel we have clear ownerships of X products)
• Capacity to focus without interruptions
• Possibility of managing power bi active directories ourselves

✔ Action items

• Comilona soon™️
• Fix dbt alerts
• Agree with Ben R. on a different way to manage permissions
• Explore local environment postgres improvements
• Create Ticket to document KPIs dbt area
• Checklists for dbt repo
• and PBI repo
• Potentially, also include CI checks in dbt repo
• Make a cleaning day for Data Catalogue docs
• 90 minutes retros