Scrum Framework: an editable mindmap
Explore Scrum Framework as an editable mindmap. Follow color-coded branches for Product backlog, Sprint planning, Daily delivery, Review, Reflect & repeat, with supporting ideas and curved connections.
A mindmap of Scrum Framework, with the main ideas arranged around a central topic and connections that show how they relate.
Scrum Framework: an editable mindmap
The interactive MindMap canvas for this explanation — every lane, row and arrow above is a real QueryChart diagram you can open and edit.
How to read this mindmap
- Begin at “Scrum Framework” in the centre, then explore any branch that answers your question. The branch colors keep each group of ideas together.
- Curved lines show relationships; arrowheads appear only where one idea leads to another. Select any idea in the editor to change its text, position, or connections.
Product backlog
This branch brings together “The product owner owns and orders the backlog — every piece of work lives here until a sprint claims it.”.
Sprint planning
This branch brings together “Planning picks items from the top of the backlog and agrees a sprint goal. The team, not the product owner, decides how much it can commit to.”, “Sprint backlog of committed items”.
Daily delivery
This branch brings together “Fifteen minutes, three questions: what did I finish, what am I doing next, what is blocking me. It is an alignment ritual, not a status report to management.”, “Team develops the increment”.
Review
This branch brings together “The team shows stakeholders what it built. The product owner adjusts the backlog based on what they see — the review is about the product, not a post-mortem.”.
Reflect & repeat
This branch brings together “The retro is the team's own meeting: what went well, what went badly, and one improvement to try next sprint.”, “Next sprint begins from the updated backlog”.
Connections across the map
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.
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
Start at the central topic
Rename “Scrum Framework” if you want to adapt this map to a specific project or lesson.
Develop the branches
Edit the supporting ideas, then add examples and notes where a branch needs more detail.
Connect related ideas
Draw curved connections across branches; use an arrow only when the relationship has a direction.
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 mindmap in QueryChart
Open this mindmap as your own editable free canvas. Move ideas, add branches, and draw new connections.