Validate JTBD for CMS: Optimize (DevOps Reports)
What’s this issue all about?
This issue is contributing to the "KR: Continue validating Jobs to be Done to better support Category Maturity"
The DevOps Reports category (direction) is currently at minimal maturity. Our aim in FY22 is to move this to viable maturity. The first step in the category maturity scorecard process is to define and validate our Jobs-to-be-done.
We would like to validate 1-3 of the below JTBD hypotheses.
Who is the target user of the feature?
What questions are you trying to answer?
What are the core JTBD for our target persona related to this category? Are our hypotheses valid?
What hypotheses and/or assumptions do you have?
JTBD hypotheses in no particular order...
-
Renewal: When renewing my contract with a vendor, I want to demonstrate to leadership that the tool is being adopted and providing value, so I can justify the tool's expense.
-
Upgrade: When looking to upgrade my contract with a vendor, I want to demonstrate to leadership that the higher tier will provide value, so I can justify the tool's expense
-
Migration: When consolidating my DevOps toolchain and/or migrating to a new platform, I want to track the progress of adoption across my organisation, so that we can get the most out of our new investment and remove other tools.
-
Best practice: When trying to improve organisational productivity, I want to know which tools & practices are being used in high/low-performing teams, so that we can learn from their experience.
-
DevOps maturity: When transforming my organisation, I want to know how far along our DevOps journey we are and how this has impacted performance, so that I can report on progress to leadership.