Sprint Review
Agile Scrum

Sprint Review

Sprint Review is a Scrum event where the increment and the progress towards the Product Goal are inspected.
Read more
Get PDF
Tags
Agile Agile Sprint Review image Infographic Picture Poster Purpose of Sprint Review Scrum Scrum Events Sprint Review Sprint Review Agenda Sprint Review Meeting
Article

Sprint Review


  • Sprint Review is a meeting where the increment and the progress towards the Product Goal are inspected.
  • The time-box for the event is 4 hours for a one-month Sprint, for shorter sprints, it is usually shorter.
  • It is attended by both the Scrum Team and the Stakeholders to gather the best possible insights.
  • Based on the increment and the changes in the environment the possible adaptations should be identified.
  • If the Product Owner decides to do so, the adaptations from the Review are reflected in the Product Backlog to meet new opportunities.
  • This event is not supposed to be only a presentation of what was done in the Sprint, it is a working session.

Sprin Review in Sprint.
Resources
scrumguides.org

Similar posters

RACI Matrix
RACI Matrix RACI Matrix/Chart is the type of responsibility assignment matrix for effective work organization, communicating the responsibilities.
CEDAR Feedback
CEDAR Feedback CEDAR is a structured feedback model providing coaching opportunities via repeated revisiting and readjusting of the feedback and the goals.
STATIK Kanban
STATIK Kanban The Systems Thinking Approach To Introducing Kanban (STATIK) is a repeatable way to start with Kanban resulting in continuous improvement.
Data Model Canvas
Data Model Canvas The Data Product Canvas is a framework for developing data products based organized into 10 blocks within 3 domain areas.
Kanban Practices
Kanban Practices Visualize Visualizing your work provides transparency, identifying the bottlenecks. Create cards for the items you work on. Think of the workflow – statuses that work items go through to make implicit policies explicit, which enable learning how the work works. Limit Work In Process Stop starting, start finishing. Limit the number of items being worked...
Theory Of Constraints
Theory Of Constraints The Theory of constraints says the throughput of any system is limited by at least one constraint slowing it down.
Classes of Service (CoS)
Classes of Service (CoS) Classes of service (CoS) provide a transparent way of categorizing the incoming work items and ensuring they are properly prioritized and governed to lead to meeting customer expectations. They enable managing risk, priorities, and cost of delay. Expedite High-priority items that should be worked on as soon as possible. Expedite class work items have critical...
Seven wastes of software development
Seven wastes of software development Similar to what TPS identified as seven categories of waste in manufacturing, also software development has its own wastes.
Core Kanban Practices
Core Kanban Practices One of the few rules or practices which are the foundation of Kanban are its 3 core practices: Visualize, Limit WIP, and Manage flow.
The prime directive of agile software development
The prime directive of agile software development Acronymat poster: The prime directive of agile software development - Never be blocked, the system must work all the time.