Validated GitLab JTBD Canvases and Opportunity Scores

This page contains links to the JTBD canvases that have gone the GitLab JTBD Playbook process and the top outcome statements and opportunity scores from those canvases.

This page acts as the single source of truth for the record of Jobs to be Done canvases that have completed the GitLab Playbook process.

For each canvas / job performer we list each outcome statment that received a score of 10 or higher. As a reminder, we perceive opportunity score as having a severity as explained at the end of the determine opportunity scores section of the playbook.

Code Author

Top Opportunities

Outcome Statement Opportunity Score
Maximize my confidence when checking that new code is working as expected in production. 11.76
Minimize the time it takes to reproduce a bug/problem. 11.70
Minimize the time it takes to identify errors and bugs in my code. 11.00
Decrease the time it takes to run test cases. 11.00
Maximize my confidence that CI/CD pipelines are running smoothly. 10.85
Decrease the time it takes to fix errors and bugs in my code. 10.81
Increase the chance that documentation is kept up to date. 10.76
Minimize the errors when integrating new code into the existing system. 10.69
Increase the chance that the pipeline passes. 10.17
Minimize the effort it takes to review my own code for security and performance. 10.04

Code Reviewer

Top Opportunities

Outcome Statement Opportunity Score
Minimize the time it takes me to understand the context of a merge request (as a reviewer). 11.09
Increase my ability to assess the larger infrastructure impact of the proposed changes (during a code review). 10.06
Increase the efficiency with which I can examine proposed code changes. 10.02

Repository Manager

Top Opportunities

Outcome Statement Opportunity Score
Minimize the effort when searching for a specific change in the code base. 11.28