FY22-Q4 UX KR: Help drive Category Maturity forward by preparing JTBDs for Q1 planned maturity
We expect to move 9-product categories up in maturity by the end of FY22-Q1 by evaluating their maturity using Category Maturity Scorecards (CM Scorecards).
Step 0 of conducting a CM Scorecard is having defined and confident JTBDs. We will work on creating these in Q4 to properly prepare for the upcoming Q1 evaluations.
Helpful tips:
- Learn how to write JTBD
- Work with your PM to select up to 2 relevant high-priority job statements (JTBD). These should be specific to the defined criterium for moving a category maturity up (i.e., related to the newly added features or enhancements since the last evaluation).
Once you have your 1-2 job statements, add them to the JTBD SSoT (data/jobs_to_be_done.yml) and your category's (or group's) direction page. For an example, see Austin's Compliance MR. Mark your category off below and provide a link to your MR in the comments.
-
Compliance: Audit Reports ⚠ ️No longer prioritized in this quarter as maturity date has been moved out. -
Plan: Epics | gitlab-org/ux-research#1641 (closed) - !87491 (merged) -
Plan: Design Management ⚠ ️No longer prioritized in this quarter @cdybenko to update the planned maturity. -
Package: Package Registry | !95054 (merged) -
Create: Git LFS ⚠ ️No longer prioritized in this quarter as maturity date has been moved out. -
Secure: DAST | !95454 (merged) -
Secure: Dependency Scanning -
Release: Release Orchestration | !95913 (merged) -
Enablement: Geo-replication | !96366 (merged) -
🌟 BONUS🌟 Testing: Performance Testing | !95842 (merged) !96447 (merged) -
🌟 BONUS🌟 Testing: Review Apps | !96812 (merged)
If the time of the planned maturity changes for your category please add a comment to the issue indicating the updated quarter it is expected.
Edited by Rayana Verissimo