sprint

An innovation sprint is a 2-week structured cycle that tests key business assumptions while delivering measurable product work. It applies a sprint framework to discovery, validation, and MVP phases to define clear learning goals.

Prioritize your sprint backlog by evaluating assumption risk against delivery value to optimize learning. This ensures testable user stories with clear acceptance criteria directly validate hypotheses during the sprint cycle.

Yes, a 2-week sprint can combine learning goals and feature delivery. The framework ensures every cycle includes a learning goal tied to an assumption, testable user stories, and a definition of done for tangible outcomes.

The best way to structure an innovation sprint retrospective is to surface tested assumptions and guide next steps. The retrospective updates the innov.local.md file to capture learning outcomes and adjust future discovery cycles.

Yes, the sprint framework explicitly works for discovery, validation, and MVP phases. It defines learning goals, manages the backlog, and establishes a definition of done tailored to each phase of the innovation cycle.