The Sprint and the events inside it, one post each: Planning, the Daily Scrum, the Review and the Retrospective, in plain language.
A Sprint is a fixed-length event of one month or less, and every other Scrum event happens inside it. It gives a team a regular rhythm of planning, building, inspecting and adapting. Its length is the team's first big planning decision, and the main rule is that the Sprint Goal is not endangered once it starts.
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.
The Daily Scrum is a 15-minute event for the Developers to inspect progress towards the Sprint Goal and adjust the plan for the next day. It turns into a status report when it is aimed at a manager instead of at the work. This post shows what the Scrum Guide actually requires and how to keep the event useful.
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.
