KR: Continue validating Jobs to be Done to better support Category Maturity => 9/13, 69%
We expect to move 9 product categories up in maturity by the end of Q3. We evaluate 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 Q2 to properly prepare for the Q3 evaluations.
- Learn how to write JTBD
- Work with your PM to select up to 2 relevant high-priority (job statements) JTBDs to focus on. (These should be specific to the defined criterium for moving a category maturity up--i.e. related to 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 example, see Austin's Compliance MR. Add a link to your MR in the table below when they're ready.
|Audit Reports||First submission !66569 (merged)
Revision !77099 (merged)
Moved pages !79347 (merged)
|DevOps Reports||!85810 (merged)|
|Performance Testing||Planned maturity moved to Q4|
|Dependency Proxy||Planned maturity is moving out of Q3|
|Auto DevOps||Planned maturity is moving out of Q3|
|Cluster Cost Management||Planned maturity is moving out of Q3 by 12 months|
|Cloud Native Installation||!85896 (merged)|
||First submission !83290 (merged)
Second submission !78306 (merged)
Maturity update !84401 (merged)
||JTBD update !80956 (merged)|
||JTBD confidence update !80208 (merged)|