Runner Group - JTBD
Overview
The goal of this page is to create, share and iterate on the Jobs to be Done (JTBD) and their corresponding job statements for the Runner group. Our goal is to utilize the JTBD framework to better understand our buyers’ and users’ needs.
Goals
Utilize JTBD and job statements 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
- DevOps teams may be managing hundreds of Runners, which may also mean offering different virtual machine configurations and sizes, which adds operational complexity. JTBDs will help us hone in the complex tasks these users need to successfully use our tools.
- Runner’s strategy must consider and balance the needs of both self-managed and GitLab.com product offerings.
- Configuring and managining runners are crucial steps in the continuous integration path, but today first-class enterprise management of runners experience is not easily accessible to users. Bringing this capability to a higher level can increase our reach and growth.
JTBD
Getting started with GitLab Runner
When using a CI/CD tool for the first time, I need to understand what software I need to install and configure to execute the pipeline jobs.
| Micro Job | Job statement | Maturity | Confidence | Source |
|---|---|---|---|---|
| When I have to address a specific CI build use case or CI platform administrative requirement, I want to configure the CI build software application to ensure that the CI/CD pipeline jobs can run successfully for the specified project types. | Grade D | Researched | Issue | |
| When migrating from Jenkins, I want to understand how the new CI build software architecture is different from Jenkins agents, so that I can set up my infrastructure in the most optimal way. | Grade - | |||
| When inspecting an existing job, I want to easily understand the role of an agent, so I can make decisions on its configuration. | Grade - |
Runner Fleet Management
| Micro Job | Job statement | Maturity | Confidence | Source |
|---|---|---|---|---|
| When I am managing the execution of many CI jobs, I want an overall understanding of the job execution agents connected to my organization, so I can make effective decisions. | Grade C | Researched | Issue | |
| When I am troubleshooting CI jobs, I want to quickly know if the problem connects with the job execution agent, so I can resolve the problem and continue working. | Grade - | Researched | Issue | |
| When I am managing continuous integration of code at scale, I want to understand the pipeline health, so I can successfully resolve and prevent issues from occurring. | Grade - | Researched | Issue |
Last modified December 15, 2023: Migrate Engineering ruby code to the new handbook (
c8544f4a)
