At the end of each Sprint, the Scrum Team meets for the Sprint Retrospective. The purpose is to review how things went with respect to the process, the relationships among people, and the tools. The team identifies what went well and not so well, and identifies potential improvements.
The Sprint Retrospective is one of the most important and least appreciated practices in the Scrum framework. It is important because it gives teams the chance to customize Scrum to their unique circumstances. It is under-appreciated because some people have a misguided view that it takes time away from doing “real” design, build, and test work.
The Sprint Retrospective is a crucial contributor to the continuous improvement that Scrum offers. Scrum teams hold Retrospectives each and every sprint, allowing teams to take advantage of insights and data before they are lost. Because a Scrum Team meets at the end of each Sprint to inspect and adapt its Scrum process, it can apply early and incremental learning throughout the development process and thereby significantly affect the outcome of the project.
Read More »
Near the end of the Sprint, the team conducts two important inspect-and-adapt activities: the Sprint Review and the Sprint Retrospective. The Sprint Review focuses on the product itself. The Sprint Retrospective, on the other hand, looks at the process the team is using to build the product.
During Sprint Planning we plan the work. During Sprint Execution we do the work. During Sprint Review we inspect (and adapt) the result of the work – the Potentially
Shippable Product Increment. The Sprint Review occurs near the end of each Sprint cycle, just after Sprint Execution and just before – or occasionally after – the Sprint Retrospective.
The Sprint Review gives everyone with input to the product development effort an opportunity to inspect and adapt what has been built so far. The Sprint Review provides a transparent look at the current state of the product, including any inconvenient truths. It is the time to ask questions, make observations or suggestions, and have discussions about how to best move forward given current realities.
Demonstrates what was achieved in the Sprint and collect feedback
Whole team participates
Invite anyone and everyone
Read More »
The Daily Scrum is a critical, daily inspect-and-adapt activity to help the team achieve faster, more flexible flow towards the solution. All Scrum meetings are time boxed. The Daily Scrum is a fifteen minutes activity that takes place once every 24 hours. The Daily Scrum serves as an inspection, synchronization, and daily adaptive planning activity that helps a self-organizing team do its job better. The Daily Scrum is a core Scrum practice. If you don’t do it, you aren’t doing Scrum.
The goal of the Daily Scrum is for people who are focused on meeting the Sprint Goal to get together and share the big picture of what is happening so that they can collectively understand how much to work on, which items to start working on, and how to best organize the work among the team members. The Daily Scrum also helps avoid waiting. If there is an issue that is blocking flow, the team would never have to wait more than a day to discuss it. Imagine if the team members got together only once a week—they would deny themselves the benefits of fast feedback.
Read More »
Each Sprint begins with a time boxed meeting called Sprint Planning. In this meeting the Scrum Team collaborates to select and understand the work to be done in the upcoming Sprint.
The entire team attends the Sprint Planning meeting. Working from the ordered Product Backlog, The Product Owner and the Development Team members discuss each item and come to a shared understanding of that item and what is required to complete it consistent with the current Definition of Done.
In Scrum, the Sprint Planning meeting is described as having two parts.
Choose Goal: the Team and the Product Owner collaborate to decide how much of the prioritized backlog can be turned into potentially shippable functionality.
Create Sprint Backlog: the Team defines the tasks required to build that functionality during the next Sprint, including estimates to achieve the Definition of Done.
Read More »