Iteration/sprint modeling is the focused design and modeling work that happens at the beginning of each iteration. It’s where the team takes the stories planned for the sprint and thinks through how they’ll implement them.
This is different from Requirements Envisioning (which looks at the whole project) and Look-Ahead Modeling (which scouts future iterations). Sprint modeling is about this sprint’s work.
What happens:
- The team reviews each story planned for the iteration
- They sketch out the design: data model changes, API interfaces, UI wireframes, component interactions
- They identify dependencies between stories and decide on implementation order
- They surface risks and unknowns (“we’ve never integrated with that API before — let’s spike that first”)
- They break stories into technical tasks
How long: a couple of hours at most. This shouldn’t consume the first day of the sprint. It’s a focused burst of collaborative design.
The format:
- Usually a whiteboard session with the whole team
- Light, fast, conversational
- Models are disposable — they’re thinking tools, not documentation
- Take a photo if you need to reference it later
Why it works: when everyone has a shared mental model of what they’re building before they start coding, there’s less rework, fewer misunderstandings, and better design decisions. The 2 hours of modeling saves 20 hours of “wait, I thought we were doing it this way.”
Related: Architectural Envisioning, Requirements Envisioning, Agile Modeling Session