Sprint Planning is the event that starts a Sprint. The whole Scrum Team agrees why the Sprint is valuable, what can be finished in it, and how the chosen work will get done. It ends with a Sprint Backlog: a goal, the items chosen to serve it, and a plan the Developers can follow.
A project manager is accountable for delivering a project to plan: scope, schedule, budget and risk. A Scrum Master is accountable for the team using Scrum well, and for removing what holds it back. The first manages the work. The second serves the team that manages itself. They overlap less than their job titles suggest.
The Definition of Done is the team's shared description of what a finished piece of work looks like. Work that meets it becomes part of an Increment, and work that doesn't goes back to the backlog. This post covers how to write one, what a good one contains, and what changes when some of the code is generated by AI.
Scrum is a lightweight framework for solving complex problems in small steps. One small team works in fixed-length Sprints of a month or less, shows something usable at the end of each one, and uses what it learns to plan the next. This guide explains how that works, and where Scrum deliberately stops.
We use analytics cookies to see which pages help and which don't. Scrumagic works the same whichever you choose, and you can change your mind any time from "Cookie settings" in the footer. Privacy Policy.
