Define and add JTBD for Source Code Management
High level plan
-
Review existing research around JTBD statements for Source Code Management (Due 2 Dec) -
Torsten -
Michael
-
-
Come up with JTBD statements for Source Code Management (Due 9 Dec) - Unvalidated at this stage is ok
-
Add to Handbook (Due 16 Dec) - JTBD statements will go in the
data/jobs_to_be_done.yml
file - Will appear in Handbook https://about.gitlab.com/direction/create/#jobs-to-be-done
- JTBD statements will go in the
-
Create research issues to validate JTBD statements (Due end of January 2023)
Existing research
From ux-research#2184 (comment 1184926701)
there is some previous work for identifying JTBD for SCM:
- https://app.mural.co/t/gitlab2474/m/gitlab2474/1589390696686/5a2d728f9555be9f5972504f422d6b53ab29017c
- https://www.youtube.com/watch?v=u5mlErGAWgY
This work was done before SCM and Code Review were split. However, I think this post-it sticker is at the heart of it. Although, I agree with Pedro's comment that "setup" is not purposeful enough. When I did a quick exercise in my head before looking at this mural, I came up with the following (totally unvalidated) jobs for SCM:
- Protect IP
- Enable/motivate collaboration
- Ensure quality/compliance (through process)
Also, I have made my own attempts to explain what the goals are in SCM in the four bullets under the overview section of the direction page.
Edited by Michael Le