Scrum in software development
Scrum is the most popular agile methodology with around 85% of practitioners opting to go with this approach. Like Kanban, Scrum is an iterative approach to software development which delivers continuous iterations of value to the consumer as quickly as possible.Ceremonies & Artifacts
Scrum uses Sprints (usually 2 weeks long).
At the start of the Sprint, a Sprint Planning Meeting takes place to select high priority items from the Product Backlog that the developers believe they can commit to delivering in this 2 week period.
From that meeting, a Sprint Backlog is created with the items to be delivered during that Sprint. Any new requirements or asks that crop up need to wait for the next sprint.
Daily Stand Up takes place each and every day to discuss progress and identify any blockers.
Sprint Review is where new functionality is demonstrated to stakeholders. It’s a joint opportunity to demo work and make sure everything is as intended. Feedback and dialogue are welcomed. At the end of the Sprint, items are released. Any incomplete items return to the Product Backlog.
Sprint Retrospective is where the squad reviews what went well, what needs improvement and what actions can be taken to iteratively improve the way we work for the next Sprint cycle.
The Burndown chart measures the velocity at which the squad is working through stories. Did we over/under estimate work committed this sprint? What is our work effort against each increment delivered?