Package Stage - The most important use cases for our customers

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 Package stage. 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

• Most customers do not purchase GitLab solely for the Package stage. So, there will be assumptions in the JTBD that from the buyer’s perspective, the motivations for ‘buying’ Package are the same.

Jobs To Be Done

Reliable software dependencies

When building and deploying software, I need to reliably fetch my project’s software dependencies, so my development and product ecosystem can operate without interruption.

Micro Job	Job statement	Maturity	Confidence	Source
	When building and deploying software, I want to reduce reliance on upstream dependencies that I don't control, so my product can operate without interruption.	Grade -	Researched	Issue

Manage and store dependencies

When my organization stores dependencies in a registry, I want to understand and manage what’s stored, so that I can keep organized and keep storage costs down.

Micro Job	Job statement	Maturity	Confidence	Source

Control dependency access rights and permissions

When setting up my organization, I want to manage permissions for dependencies my software relies on, so that I can comply with company security and compliance requirements.

Micro Job	Job statement	Maturity	Confidence	Source
	When I work in sectors that are subject to audit and regulation, I want to access immutable historical versions of dependencies, so that I can fulfill legal requirements.	Grade -	Researched	Issue
	When multiple teams or projects share the same dependency, I want to ensure that the dependency is accessible to all who rely on it, so my development and product ecosystem can operate without interruption.	Grade -

Security

When my code relies on dependencies, I want to ensure these dependencies don’t introduce security vulnerabilities and compliance violations to my codebase, so my development and product ecosystem can operate without interruption.

Micro Job	Job statement	Maturity	Confidence	Source

Troubleshoot dependencies

When my code won’t compile due to a problem with a dependency, I want to understand what needs to be remediated, so that I can ensure there’s no disruption for my product.

Micro Job	Job statement	Maturity	Confidence	Source