sprintsthat

Sprintsthat is a term that appears in informal discussions of agile software development to describe a pattern of sprint planning that emphasizes outcome-oriented work. The core idea is to link each sprint to a specific, observable result and to assess success against measurable criteria rather than nominal completion of a set of tasks. The term is not part of a formal framework and is used variably by practitioners.

Origin and usage: The phrase appears primarily in online forums, blogs, and coaching materials from the early 2020s. It is sometimes presented as a pragmatic approach within existing methodologies such as Scrum or Kanban, rather than as a replacement for them. Because it is informal, definitions of sprintsthat can differ between teams and organizations.

Concepts and practice: In a sprintsthat workflow, teams start with a clearly defined sprint objective that articulates the user or business outcome sought. Plans are constrained by a targeted scope, and success is measured with predefined metrics or acceptance criteria. Reviews focus on learning and impact, and retrospectives emphasize adjustments to align future sprints with value delivery. Tools often used include lightweight metrics, stakeholder demos, and feedback loops from end users.

Relation and evaluation: Sprintsthat aligns with value-driven delivery and continuous improvement, similar in spirit to impact mapping and outcomes-based planning. Critics warn that without careful standardization it can become vague or drift toward vanity metrics. Related concepts include sprint planning, outcome-oriented development, and continuous delivery.