🧘 Retrospective – Advanced Analytics

Purpose

To provide the team an opportunity to be introspective about processes and actions that worked, need improvement, and didn’t work.

Participants

All Advanced Analytics team members

Cadence

Bi-weekly Tuesday (Last day of Sprint)

Format

• Review Data Analytics KPI Dashboard for any expected costs inccurred by the team.
• Review DAL Usage Power BI for output usage.
• Review Story Points vs Actual Points DevOps Stats.
• Review if Sprint goals were completed.
• Complete Azure DevOPs Retrospective board for sprint.
  • What went well?
  • What didn’t go well?
• Assign any action items that surfaced.

Guiding Principles

• Use Data Wisely
  Metrics (compute, product, velocity) should guide conversations, not dominate them.
• Celebrate Success
  Recognize wins: deployments, efficiency gains, and great teamwork.
• Focus on Systems
  Discuss processes, not people. Aim to improve how we work.
• Prioritize Team Health
  Review sprint pace, workload balance, and signs of burnout.
• Foster Psychological Safety
  Everyone should feel safe and encouraged to speak up.
• Think Iteratively
  Retros are for continuous improvement, not post-mortems.

Expected Outcome

A Retrospective board with relevant feedback. If applicable, any tickets created for action items should be added to the team’s backlog.