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.
Utilize JTBD and job statements to:
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.
|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.||Researched||Issue|
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.
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.
|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.||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.||Issue|
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.
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.