fleet/docs/Contributing/rituals/sprint-demo.md
2025-09-13 21:17:15 -05:00

1.7 KiB

Sprint Demo

Purpose: Showcase features, improvements, and bug fixes in the upcoming release to everyone at Fleet.

Cadence: On the last day of each sprint, 90 minutes.

Participants: All engineering teams and stakeholders.

Ritual DRI: Release DRI or assigned team member.

Format

  1. Each EM introduces their group's contributions.
  2. Each engineer takes less than 10 minutes to demo their work.
  3. Manage time and transitions between presenters.
  4. Record the ritual for the release article and social media.

Agenda

  • Introduction and overview of sprint accomplishments.
  • Feature demonstrations, all product groups.
  • Bug fix presentations, all product groups.
  • Closing and next release timeline.

Presentation Guidelines

  • Time limit: 3-10 minutes per contribution.
  • Format: Live demonstration preferred over slides.
  • Audience: Mixed technical and non-technical stakeholders.
  • Focus: User impact and capabilities, not implementation details.
  • Privacy: No specific customer names or confidential information.

Keep presentations accessible to all participants. Avoid overly technical details. Focus on demonstrating what users can now do rather than how it was built.

For features: Show what is now capable and demonstrate the user experience.

For bug fixes: Explain how the issue impacted existing customers.

Important: These meetings are recorded and posted publicly. Do not mention specific customer names.

Notes