Release Process

Sprint Planning

• Planning Sessions: Regular sessions to define sprint goals, review tasks, assign owners, and ensure alignment with business objectives.

  • Use JIRA

  • Start product feature documentation for release notes.

  • Identify the scope of feature testing for UAT

  • Review Figma Designs

    • leverage comments section still for questions to P3 team

Post-Release Reviews

• After each release, hold a brief retrospective to identify successes, pain points, and areas for improvement. Capture insights to inform future releases.

  • Use JIRA/Confluence

Continuous Release Cadence

• Release on Completion: Aim to release each feature as it’s ready rather than bundling multiple features. This ensures quicker feedback and reduces the risk of large-scale issues.

• Feature Toggles: Use feature flags to control the visibility of unfinished or experimental features in production, allowing for gradual rollouts and safer deployments.

  • can be controlled via environment variable

Testing

• User Acceptance Testing (UAT): Vicki and Mark perform UAT in the Release QA environment to ensure features meet the acceptance criteria and are ready for production.

Documentation

• Release Notes: Provide short, user-focused release notes that highlight key new features, improvements, and bug fixes. These should be shared internally and externally to ensure transparency and understanding

  • Keep Mark’s documentation

  • Vicki (product) to add feature-user focus notes

Dependencies

Ownership & Timelines: Track all cross-team or external dependencies, ensuring clear ownership and timelines. Regularly review these to avoid bottlenecks or delays in releases.