Design flow of work and traceability
Overview
This module turns a feature request into a connected evidence trail: work item → branch → pull request → build → artifact → deployment → operational feedback. The aim is not to create bureaucracy; it is to make delivery state reliable and discoverable.
Concepts introduced
Hands-on (required embedded lab)
Create a training issue/work item and a branch that references its ID. Open a pull request that links the work, run a pipeline that publishes a versioned artifact, and record the deployment environment in the PR or release note. Verify that someone else can trace from the work item to the pipeline run without asking you. Break the chain by removing one link, explain what evidence is lost, restore it, then delete the training project/repository if disposable.
Exam focus
- GitHub Flow is a short-branch, PR, validate, merge, deploy workflow—not merely “use GitHub.”
- Traceability connects source, bug, quality, deployment, and feedback evidence.