midsprint

Midsprint is a term used in some agile software development communities to describe a checkpoint at the midpoint of a sprint. It is not part of the formal Scrum framework, and its usage, duration, and purpose can vary considerably between teams. The concept generally aims to improve adaptability by re-evaluating progress against the sprint goal before sprint planning concludes.

Typically, a midsprint checkpoint is a short, time-boxed meeting held roughly halfway through the sprint. It may involve the product owner, the Scrum master, and the development team, and sometimes stakeholders. The format can range from a quick stand-up-style update to a focused backlog-review session. The key requirement is to keep it lightweight and within the team's defined cadence.

Purpose and outputs: the team reviews progress toward the sprint goal, checks completed work against acceptance criteria, and identifies blockers. Based on this review, the team may re-prioritize backlog items, adjust scope within the sprint, or reallocate resources. Outputs typically include an updated sprint backlog, a clarified or revised sprint goal, and a risk or blocker log. Benefits can include earlier risk detection, better alignment, and reduced last-minute scope changes; drawbacks include possible disruption to planned work and the temptation to micromanage.

Adoption varies; some teams use midsprint checkpoints only for longer sprints, while others integrate it with other ceremonies. It is not a universal practice in Scrum and is more common in hybrid or lightweight agile approaches. Related concepts include mid-sprint reviews and backlog refinement sessions.