Skip to content

CMS Scorecard - Release: FY22-Q3-Q4 - Environment Management Viable

Category Maturity Scorecard Checklist

Learn more about Category Maturity Scorecards

  1. Review the Category Maturity Scorecard handbook page and follow the process as described. Reach out to the UX Researcher for your stage if you have questions.
  2. Document the research data and insights in a Dovetail project using the Category Maturity Scorecard Dovetail project template.
  3. Link the Dovetail project in this issue.
  4. Document the results of each JTBD scenario using the Dovetail template.
  5. If the participant has not granted permission to share the recording publicly, ensure the sharing settings are set to GitLab-only.
  6. If needed, create a recommendation issue for these sessions.
  7. Once the research has concluded, update the issue description Outcome section with the maturity level. The outcome can be a downgrade, remain, or increase in x-maturity. For example, The CM Scorecard research has concluded and we have increased the maturity for Dependency Scanning to Complete.

Outcome

Other notes

{{Add any additional notes that came from freeform discussion or elsewhere}}

JTBD

Source - https://about.gitlab.com/direction/release/environment_management/#jobs-to-be-done

  • When releasing software, I want to manage application environments across multiple teams and projects, so I can lower risks and guarantee higher organizational performance.

Personas

Edited by Emily Bauman