Environment Stage - JTBDs
Overview
The goal of this issue will be to review existing jobs from the Release and Configure teams, and adjust them as we see fit for groupenvironments
Existing Jobs
Deliver code changes
- Job Statement: When code changes are finalized, I want to deliver them to customers, so they can benefit from these changes.
- Grade: B
- Confidence: Researched
- Source: gitlab-design#431 (closed)
Track code being delivered
- Job Statement: When delivering changes, I want to track different versions of code until they are ready for production, so I can ensure the right set of changes reach our customers.
- Grade: C
- Confidence: Researched
- Source: gitlab-design#431 (closed)
Include relevant information with the code being delivered
- Job Statement: When preparing a new version of my software for users, I want to include relevant information to supplement the code in the release, so that users can understand what is in the new release and are able to use the software successfully.
- Grade: B
- Confidence: Researched
- Source: gitlab-design#431 (closed)
Track and coordinate deployments
- Job Statement: When preparing to deliver changes, I want to keep my teams coordinated and aware of what’s being deployed, so that I can ensure the right set of changes reach our customers.
- Grade: None
- Confidence: N/A
- Source: N/A
Manage deployments in one place
- Job Statement: When managing changes to production, I want to manage and take action on deployments from a single tool, so that I can have better control of our production changes.
- Grade: None
- Confidence: Researched
- Source: &3052
Managing environments
- Job Statement: When releasing software, I want to manage application environments across multiple teams and projects, so I can lower risks and guarantee higher organizational performance.
- Grade: None
- Confidence: Researched
- Source: ux-research#1935 (closed)
Manage software releases
- Job Statement: When managing software releases, I want to optimize repeated tasks and workflows, so that I can make the business more efficient.
- Grade: None
- Confidence: Researched
- Source: https://gitlab.com/gitlab-org/ux-research/-/issues/2016
Manage release compliance
- Job Statement: When releasing code, I want to manage release artifacts, so I can deploy and audit them in a repeatable fashion.
- Grade: None
- Confidence: Researched
- Source: N/A
Communicate release changes
- Job Statement: When my product is ready to be released, I want to make the documentation about it available, so I can educate the adopters on any changes.
- Grade: None
- Confidence: Researched
- Source: N/A
Manage infrastructure as code
- Job Statement: When I need to provision or administer cloud infrastructure resources, I want to do it through code, so that I can collaborate on it with others, can run automated tests and deployments, and check out compliance requirements.
- Grade: None
- Confidence: Researched
- Source: N/A
Manage infrastructure as code
- Job Statement: When I need to provision or administer cloud infrastructure resources, I want to do it through code, so that I can collaborate on it with others, can run automated tests and deployments, and check out compliance requirements.
- Grade: None
- Confidence: Interview Based
- Source: https://dovetailapp.com/projects/22141897-42eb-4a96-8038-4c0467c7c58b/data/b/5cf7e46b-aca3-405e-ae39-8ee1304115a6
Manage access around IaC changes
- Job Statement: When I need to collaborate on cloud infrastructure, I want to control who has read and/or write level access to different parts of the infrastructure, so that I can comply with company security and compliance requirements. (leader)
- Grade: None
- Confidence: Interview Based
- Source: https://dovetailapp.com/projects/22141897-42eb-4a96-8038-4c0467c7c58b/data/b/5cf7e46b-aca3-405e-ae39-8ee1304115a6
Easy onboarding for non Ops professionals
- Job Statement: When I need to manage the infrastructure, I need an easy to use, simple workflow, so that I can focus on the task at hand.
- Grade: None
- Confidence: Interview Based
- Source: https://dovetailapp.com/projects/22141897-42eb-4a96-8038-4c0467c7c58b/data/b/5cf7e46b-aca3-405e-ae39-8ee1304115a6
Deploying in preferred way
- Job Statement: When I have a new version of my application, I want to deploy it into production following my preferred deployment strategy, so that I can reap the fruits of my work and can celebrate success.
- Grade: None
- Confidence: Interview Based
- Source: N/A
Monitoring deployment metrics
- Job Statement: When I push a new version into production, I want to monitor core metrics related to the deployment, so that I can be assured about the quality of the new release and act when necessary.
- Grade: None
- Confidence: Interview Based
- Source: N/A
Taking action on released versions
- Job Statement: When there is a problem with a just released version, I want an easy way to roll forward or backward.
- Grade: None
- Confidence: Interview Based
- Source: N/A
Setting up a cluster
- Job Statement: When I set up a new cluster, I want to make sure that application operators can easily target their developments at it, so they can start using the cluster immediately.
- Grade: None
- Confidence: Interview Based
- Source: N/A
Setting up a cluster
- Job Statement: When the engineers need a new cluster, I want to make sure that they can self-serve and the cluster will be set up following company requirements.
- Grade: None
- Confidence: Interview Based
- Source: N/A
Actions
-
Review all existing JTBDs from Release and Configure -
If required - Craft and Validate new JTBDs for groupenvironments -
If required - Remove old and outdated JTBDs from the list
Links and resources
Edited by Emily Bauman