Update Create Stage JTBD
What’s this issue all about?
There is a need to update the JTBD statements for Create that live within the data/jobs_to_be_done.yml file. See this issue and this comment for background and context.
No user-facing research is required, but some desk-research to ensure the relevancy and clarity of the statements will be done. We will use the Create Stage Benchmarking data, recent CMS studies, and other source material to justify the updates to the JTBD.
From @sarahwaldner:
Purpose
Develop a concise list of JTBD to help the Create stage to...
- Coordinate collaboration between groups when making improvements to certain JTBD that multiple groups are responsible for
- Clearly communicate to other stages in GitLab what the charter of the Create stage is
- Help the stage focus on solving problems for the jobs users utilize GitLab to complete
Scope
Develop JTBD statements (a reasonable amount that applies to jobs majority of our personas hold) and document them in the yaml file. This will entail review of existing studies and no extra research.
I think that we should correlate the JTBD to the categories that we have so that we can see what JTBD are relevant to which group.
I think there should be 5-8 JTBD.
Impact
- Streamlined collaboration
- Focus on enabling jobs and fixing problems to avoid being a feature factory
- Support creating a vision
Current JTBD
| Slug | JTBD | Group | Status/Confidence | Source |
|---|---|---|---|---|
| code_review_1 | When product improvements are identified, I want to propose changes that address them, so that I can help build a better product. | Code Review | Not validated | Issue |
| code_review_2 | When my teammates propose changes, I want to review them before they are accepted, so that I can help increase the quality of changes, minimize the risk of defects, minimize the risk of out-of-scope changes, and grow the team’s expertise. | Code Review | Not validated | Issue |
| code_review_3 | When my teammates propose changes, I want to ensure they are reviewed and accepted according to internal guidelines, so that we can increase the quality of changes, minimize the risk of defects, and maximize the reliability of product data. | Code Review | Not validated | Issue |
| source_code_protect_IP | When the source code contains restricted information or is part of a critical system, I want to control the access to the source code, so that I can protect the investments in intellectual property and to reduce the risk of source code exploitation. | Source Code | Not Validated | Issue |
| source_code_track_changes | When reviewing past code changes, I want to track changes and manage different iterations of the source code, so that I can identify which changes were made and when, and to reference an earlier iteration if necessary. | Source Code | Not Validated | Issue |
| source_code_enable_motivate_collaboration | When developing source code with multiple people, I want to set the rules for the collaboration, so that collaborators can explore changes and contribute efficiently. | Source Code | Not Validated | Issue |
| source_code_ensure_quality_compliance | When changing source code, I want to set conditions for applying these changes, so that code quality and compliance is maintained. | Source Code | Not Validated | Issue |
| source_code_large_binary_files | When working with large binary files, I want to version control these files with the source code, so that I can track and manage changes to the files over time. | Source Code | Not Validated | Issue |
| pages_1 | When I am deploying a static site I want to use kubernetes for my cloud native installation so I can leverage auto-devops and other benefits of K8. | Editor (Pages) | Not validated | |
| pages_2 | When I am setting up a static site for A/B testing I want to have multiple versions for the same site live so I can run tests on different cohorts of users in the same timeframe. | Editor (Pages) | Not validated | |
| pages_3 | When I have a custom domain or multiple domains I want to be able to redirect the other domains to my custom/main domain so I can optimize SEO rankings and ensure traffic from like domains are tracked. | Editor (Pages) | Not validated | |
| pages_4 | When I am setting up a static site I want to be able to set up the site with a wildcard DNS so I can avoid setting up a custom domain. | Editor (Pages) | Not validated | |
| When I'm making changes, I want to deliver secure and performant code, so I can ensure the integrity of my organization's software is not compromised. | Sasha (motivations) | Validated | Issue | |
| When collaborating with a large number of developers, I want to see a record of everyone’s changes, so we can pinpoint and unwind mistakes. | Sasha (motivations) | ? | ? | |
| When I need to review a merge request, I don’t want to lose context in my editor, so that familiar tools and views are available to remain efficient. | Editor (extension) | Validated (CMS) | Issue | |
| When I have supplemental scripts, I want to document them, so I can reuse them and become more efficient. | Snippets | Not validated | Issue | |
| When I have a piece of code that could benefit others, I want to be able to share it, so we can collaborate. | Snippets | Not validated | Issue |
Edited by Ben Leduc-Mills