> ## Documentation Index
> Fetch the complete documentation index at: https://www.scrums.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Outcome-Driven Sprints

> Deliver a defined outcome through a time-boxed scope with explicit inputs, deliverables, and acceptance criteria.

## Overview

An Outcome-Driven Sprint is a time-boxed execution model for a defined scope. It works best when you can describe the result, required inputs, and acceptance criteria before delivery begins.

Examples include discovery, architecture, audits, prototypes, remediation, and technical-debt reduction.

## Before the sprint

Confirm:

* The outcome and acceptance criteria
* Included and excluded work
* Required repositories, environments, and stakeholders
* Known dependencies and risks
* Deliverable format and review date
* What happens when assumptions change

## During and after delivery

Scrums.com tracks the sprint as a deployment. At the final review, you accept the deliverables, request changes within the agreed scope, or define a follow-on deployment.

An Outcome-Driven Sprint is one scope model. The broader [AI Development scopes](/docs/ai-development/scopes) register can contain other delivery shapes.