Skip to main content

Sprint cadence and Jira

Our sprint rhythm creates shared context, exposes blockers early, and protects time for focused delivery. Teams may adapt the cadence when the work requires it, but they must preserve clear commitments and visible progress.

Current cadence​

  • Daily standup: share completed work, today's focus, and blockers. See Standup.
  • Weekly refinement: clarify upcoming work, examine edge cases, and estimate effort only after the problem is understood.
  • Weekly planning: select refined work, agree priorities, and make realistic commitments for the next sprint. See Planning.

Planning distinguishes exploration targets, operating targets, and external commitments. The distinction must be visible in Jira whenever another team or customer may plan around the date.

Jira working agreement​

The person doing the work keeps its tasks, estimates, status, dependencies, and material decisions current. Update the record before a status discussion so the meeting can focus on decisions and help rather than reconstructing history.

When work is blocked or confidence changes, record the observation, consequence, owner, and next test or decision. Surface bad news early; delay does not make it more accurate or easier to resolve.

A plan is a high-integrity agreement based on current knowledge, not a promise to ignore new evidence. When confidence changes, communicate early and propose the clearest path to the objective.

Guidance type: Working agreement
Owner: Product and Engineering leadership