Skip to content

Optimize group — JTBD

Overview

The goal of this issue will be to create and iterate on the Jobs to be Done and their corresponding job stories for the groupoptimize. Our goal is to utilize the jobs theory to better understand our buyers' and users' needs. As part of the product development workflow, we will select prioritized job stories for problem and solution validation. We will then move the validated solutions to the build track, and launch the feature.

The following JTBD have been created for the Optimize group. These have not been validated:

  • Learn: When I am new to value stream practices; I want to learn what’s important, why it’s important and how to use it, so that I can use the tool effectively and adapt to my organisation’s needs.
  • Map: When I am establishing practices to measure my value stream, I want to define the flow of work required to ship value to my end users so that we can visualize how efficiently and reliably value is delivered.
  • Deliver: When I am moving work items through my value stream, I want to quickly identify stagnant and outlier work items in real-time, so that my team can unblock them and improve our performance.
  • Optimize: When I am optimizing my value stream and its stages, I want to understand trends and common bottlenecks, so that I can identify areas that need improvement, experiment with new practices, measure success, and learn from other successful teams.
  • Evaluate: When my organization is adopting new DevOps practices, I want to track the impact of changes, so that I can understand return on investment(ROI) and report to leadership on the value of our DevOps transformation.

Goals

Continually validate and iterate on JTBD for the Optimize group.

Utilize JTBD and job stories to:

  • Understand our users' motivations
  • Validate identified use cases and solutions
  • Continuously test and iterate features to ensure we are meeting our customers' and users' needs.
  • Create a transparent view for our stakeholders into the current and future state of the product.

Challenges

  • There isn't a large amount of existing research in this area.
  • There are many job stories that need to be validated. We will need a good way of deciding which to bring into the validation track.

Expected Outcome

Here are the revised JTBD:

Learn: When I am new to value stream practices; I want to learn what’s important, why it’s important, and how to use it, so that I can use the tool effectively and adapt to my organization’s needs.

Map: When I am establishing practices to measure my value stream, I want to define the flow of work required to ship value to my end users so that we can visualize how efficiently and reliably value is delivered.

Deliver: When I track my value stream I want to quickly understand the software delivery status so we can improve our performance in near real-time and enforce DevOps best practices and governance.

Optimize: When I am optimizing my value stream, I want to identify opportunities for improvement, or detect risks in the delivery of value to customers.

Evaluate: When evaluating my value stream, I want to link software delivery metrics to value metrics so that I can understand the value of the software workstream.

The two main jobs to be validated

  • Optimize
  • Map

Links and resources

Handbook

Existing issues/comments

The following comments, epics and issues contain useful context and inspiration.

Existing research

Edited by Dan MH