Guide for tech leads

Plan the sprint with the team

1. In Sprints, create the next sprint with a goal and dates.
2. Pull work in from the top of the backlog. On the Board with All sprints selected, tick the cards and use Sprint in the bar that appears, or set Sprint on each issue.
3. Check estimates. The sprint shows its total points; the Reports tab shows your average velocity to compare with.
4. Mark dependencies. On an issue, use Relations › Blocks or Blocked by so everyone can see what waits on what. Blocks between teams also appear in PI planning.

See Sprints and retrospectives.

Keep the board moving

• Group the board By epic to see each feature's progress, or By column for the usual flow.
• Filter by assignee or label to find stuck work.
• Cards show priority, type, story points, epic and labels. Bugs show a red bug icon.

Connect your repositories

Ask an admin to add each repository with Add repository in Settings › Repositories and paste the webhook details it shows into GitHub. See Pipelines and code. After that:

• Issues show their branches, pull requests and deployments.
• Pipelines shows build results and what's live in each environment.
• Delivery shows the four DORA metrics: deployment frequency, lead time for changes, change failure rate and time to restore.

See Pipelines and code.

Write it down

Use Docs for tech specs, runbooks and ADRs; there are templates for each. Link a spec to the epic it describes. See Docs.

Check the API before QA does

Save the main requests for each service in the API tab with checks, and link them to stories. Run a whole collection before handing a build to QA. See API workspace.