Scrum Framework — the sprint cycle explained
The Scrum framework on an interactive canvas: the product backlog, sprint planning, daily stand-ups, the sprint review and the retrospective that closes each cycle.
Scrum is a framework for delivering work in fixed-length sprints: a product owner orders a backlog, the team commits to a batch, and a short cycle of planning, daily alignment, review and retrospective turns it into a releasable increment.
Scrum Framework — the sprint cycle explained
The interactive FlowJam canvas for this explanation — every lane, row and arrow above is a real QueryChart diagram you can open and edit.
How to read this visual
- Read the four columns left to right as the sprint's arc: what exists beforehand, what planning commits, what happens during the sprint, and how it closes.
- The rows are owners: follow the boxes in the Product owner row to see what the product owner controls, and the Development team row for the work itself.
- The final box, "Next sprint begins from the updated backlog", is the loop — Scrum is a repeating cycle, not a one-shot process.
Before the sprint
"Product backlog of ordered work" is the single source of every item the team could work on, ordered by value and owned by the product owner. "Sprint planning selects work for the sprint" is the commitment moment: the team picks items from the top of the backlog and agrees a sprint goal. "Sprint backlog of committed items" is the resulting plan — the batch the team has promised to finish.
During the sprint
"Daily stand-up to align the team" is the fifteen-minute alignment ritual, and "Team develops the increment" is the actual work — building, testing and integrating toward a potentially releasable increment. Both sit in the Development team lane because Scrum is explicit that the team self-organises the work inside the sprint.
Closing the cycle
"Sprint review demos the increment" shows stakeholders what was built and lets the product owner adjust the backlog from what they see. "Sprint retrospective improves the process" is the team's own meeting in the Scrum master lane, and "Next sprint begins from the updated backlog" is the loop back to the start — the review changed the backlog, and the cycle repeats.
Key relationships and takeaways
- The backlog is the product owner's; the sprint is the team's — the framework keeps those two powers separate.
- Planning commits to a batch; the sprint goal gives the batch a purpose.
- The daily stand-up is alignment, not a status report to management.
- The review is about the product; the retrospective is about the process — two different meetings with two different outputs.
- Scrum is a loop: each sprint leaves an updated backlog for the next.
When to use this visual
- Teaching a team new to Scrum what each ceremony is for and who owns what.
- Onboarding a new product owner to the difference between ordering a backlog and running the team.
- Auditing a team's Scrum: a ceremony that does not exist on the canvas, or is owned by the wrong lane, is a practice to discuss.
How it works
Rename the roles to your team
Replace Product owner, Development team and Scrum master with your real roles, and merge or split lanes to match who actually holds the work.
Add your sprint length and cadence
Annotate the sprint boxes with your sprint length, stand-up time and review day, so the diagram is your team's schedule, not a generic one.
Draw the definition of done
Add a decision between "Team develops the increment" and the review: a definition-of-done checklist that must pass before an item counts as complete.
Extend with your refinement ritual
Insert a backlog refinement step between the backlog and sprint planning if your team holds one, connected to the ordered backlog.
Frequently asked questions
What is the Scrum framework?
Scrum is a lightweight framework for developing and delivering complex work in fixed-length iterations called sprints. It prescribes roles (product owner, development team, scrum master), events (sprint planning, daily stand-up, sprint review, sprint retrospective) and artefacts (product backlog, sprint backlog, increment), but leaves the how of the work to the team.
What are the three Scrum roles?
The product owner owns the backlog and its ordering — what gets built and in what order, and the value of the outcome. The development team self-organises to deliver the committed items — how the work is done is theirs. The scrum master serves the process — facilitating ceremonies, removing impediments and coaching the team. The visual's three lanes are exactly these three owners.
What happens at a sprint review versus a retrospective?
The sprint review is about the product: the team demonstrates the increment to stakeholders and the product owner adjusts the backlog in response. The retrospective is about the process: the team alone discusses what went well, what went badly and one improvement for the next sprint. They are separate meetings with separate outputs, which is why the visual places them in different rows — review with the team, retrospective with the scrum master.
Does Scrum require a daily stand-up?
Yes, the daily stand-up is one of Scrum's prescribed events — a short, daily alignment meeting where each team member says what they finished, what they will do next and what is blocking them. Its purpose is coordination and early surfacing of impediments, not reporting to management. The visual marks it as alignment for exactly that reason.
Edit this visual in QueryChart (FlowJam)
Open this exact Scrum canvas as your own chart, rename the roles to your team, and adapt the ceremonies to your practice.