Sprint Review

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 »

Sprint Planning

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.

planningtime

Read More »

What is Scrum?

Scrum is an Agile framework for developing innovative products and services, for organizing and managing work. Scrum begins when some stakeholders need a product. The Scrum framework is based on a set of values, principles, and practices that provide the foundation to which your organization will add its unique implementation of relevant engineering practices and your specific approaches for realizing the Scrum practices. The result will be a version of Scrum that is uniquely yours. Scrum is a refreshingly simple, people-centric framework based on the values of honesty, openness, courage, respect, focus, trust, empowerment, and collaboration. The Scrum practices themselves are embodied in specific roles, activities, artifacts, and their associated rules. Read More »