The goal of this page is to document, share and iterate on the Jobs to be Done (JTBD) and their corresponding job statements for the Pipeline Execution group. Using JTBD framework we intend to arrive at the more specific problems to be solved in relation to Continuous Integration workflows.
Utilize JTBD and job statements to:
When making a code change, I want to integrate it to the target branch quickly and safely, so I can save time and focus on developing.
|When integrating code changes, I want to automatically run relevant checks on it, so I can avoid worrying about unexpected conflicts while merging.||Researched||Issue|
|When running automated checks on code changes, I want to see the specific reason a check failed, so I can resolve it and move to another task.||Researched||Issue|
When integrating changes to a target branch, I want to be alerted about unforeseen issues, so I can avoid upsetting our users with downtime.
|When integrating changes to a target branch, I want the deployed changes to be automatically monitored, so I can focus on developing.||Researched||Issue|
When working in a large team, I want the changes to be merged without hassle or delay, so I can ensure my performance is unaffected.
When running, reviewing and interacting with automated checks, I want the platform to respond without delay or failure, so I can timely deliver on my tasks.