The Sprint Retrospective What: An opportunity for the Scrum Team to inspect itself and create a plan for improvements to be enacted during the next Sprint. During each Sprint Retrospective, the Scrum Team plans ways to increase product quality by improving work processes or adapting the definition of “Done”, and also ways to increase velocity by…
The Sprint Review What: Event held at the end of every Sprint to inspect the Increment and adapt the Product Backlog if needed. Who: Scrum Team, Stakeholders. When: At end of each sprint, before sprint planning. Approx. 2 hours for a 2-week sprint. Agenda Product Owner describes the goals for the sprint and associated…
The Daily Scrum The daily scrum (or stand-up) event is primarily for the development team. Others may attend but not interfere with the proceedings. This event is where the team updates themselves on progress in the last 24 hours, and then aligns on a plan for the next 24 hours that they believe keeps them…
Sprint Planning What: Confirm what can be delivered in the upcoming sprint Identify the work needed to deliver the increment Who: Entire Scrum Team: Dev-Team, Product Owner, Scrum Master When: Immediately prior to start of next sprint. Requires approx. 2 hours for a 2-week sprint. Sprint Planning is a Two-Part Event Sprint Planning Part One:…
Backlog Refinement What: Get User Stories ready: who/what/why acceptance criteria small enough to fit – split if necessary dependencies in place Sized in story points Who: Dev. Team, PO, Scrum Master When: Approx. 2 hours per 2-week sprint Agenda PO selects stories to refine PO describes story to team, takes questions, clarifies Add/discuss acceptance…
Scrum was introduced to address the unacceptably high failure rate of software projects. (The annually published CHAOS Report by the Standish Group publishes data on the success rates of IT projects. It was started in 1994 and at that time reported that a startlingly low 16.2% of IT projects are successful). Software development projects can…