Loading content
During the Sprint Planning meeting, the Scrum team and the Product Owner come together to define the tasks and objectives for the upcoming sprint. The team estimates the work and selects the tasks it can complete in the sprint.
Use this profile to understand the building block briefly, place it in the model, and switch to the 360° assessment when needed.
Executable approach: can be applied and produces an outcome.
What organizes, connects, or makes decisions possible.
Sprint Planning is the Scrum event where a team sets the goal and work plan for the coming Sprint.
Sprint Planning comes from Scrum, which Jeff Sutherland and Ken Schwaber described and evolved from the 1990s as an empirical framework for complex product development. The Scrum Guide defines it as the start of every Sprint.
The team answers three questions: why is the Sprint valuable, what can realistically be delivered, and how will the work be done? Product goal, capacity, and backlog become a testable Sprint Plan.
A shared purpose gives the Sprint's work a focus.
The team chooses backlog items for its capacity.
The plan is a testable expectation, not a guarantee.
Good Sprint Planning creates focus and shared expectations; it loses value when turned into a rigid command or micromanagement ritual.
Where this building block is located in the topic model.
No structure path available.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.