Retrospective: Validation for Release Orchestration Maturity

Overview

We are using this issue to capture the process for the Release Management Maturity Evaluation. We will also use this a Retrospective Thread.

JTBD: Create a Release and update it

When tracking important deliverables in my project, I want to easily create and manage release entries, so I can provide a packaged software, notes, and files for people to use.

Process Overview

Product Management and UX evaluated the "Create a Release using GitLab" using a Scorecard. This is the core JTBD for Release Orchestration.

• May 2019: Defined the JTBD and started validating it.
• Aug 2019: Closed, with recommendations.
• Nov 2019 - Feb 2020: Revisited the JTBD
• Conducted interviews with 3 participants
• Documented 20 user insights
• Additionally, Jackie interviewed 45 customers as part of Problem Validation to better understand Release Management.
• Feb - Mar 2020: To validate the viability of the major implementation for Release Orchestration, which was prioritized based on findings from our JTBD exercise, plus upcoming changes, we proactively conducted solution validation.
• Conducted interviews with 3 participants
• Documented 20 user insights
• Mar 2020: Updated the category maturity from Minimal to Viable, based on system usage and user insights.
• Mar 2020: We are tasked with the Category Maturity Scorecard for the same JTBD (Create a Release and update it).

Maturity Scorecard vs. Current Process

Retrospective Take Aways