16 June 2021

The Scrum framework (13) : Sprint Review

The Scrum Framework :

  • The Scrum Framework consists of Scrum Teams and their associated events, artifacts, and roles as defined in the Scrum Guide.
  • According to the Scrum Guide, mandatory rules and principles of Scrum are Scrum Roles, Scrum Events, Sprint Goal, Product Backlog, Sprint Backlog, Increment, Definition of Done, and Monitoring progress in Sprint and Project levels. Other things are practices that can be employed in the Scrum framework and are up to the team and project and are not mandatory.

The Scrum roles :

  • Product Owner
  • Development Team (Developers)
  • Scrum Master

The Scrum artifacts :

  • Artifacts represent work or value to provide transparency and opportunities for inspection and adaption.
  • Artifacts are defined by Scrum and designed to maximize transparency of key information so that everybody has the same understanding.
  • Product Backlog
  • Sprint backlog
  • Increment

The Scrum events :

  • Sprint Planning
  • Daily Scrum
  • Sprint Review
  • Sprint Retrospective
  • The Sprint is the container for all events

Rules :

  • According to the Scrum Guide, mandatory rules and principles of Scrum are Scrum Roles, Scrum Events, Sprint Goal, Product Backlog, Sprint Backlog, Increment, Definition of Done, and Monitoring progress in Sprint and Project levels. Other things are practices that could employ in the Scrum framework and are up to the team and project and are not mandatory.

Events :

  • Events present an opportunity in the Sprint for something to be inspected or adopted.
  • Events are designed to enable transparency and inspection
  • There are totally 5 events in the Scrum framework as Sprint, Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective.
  • Four Events of Inspection & Adaption
    1. Sprint Planning
    2. Daily Scrum
    3. Sprint Review
    4. Sprint Retrospective
  • The Sprint is a container for other events.
  • All four Scrum events are a type of feedback loop or inspect and adapt opportunities include Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective. Although Sprint is an event its role is being a container for other events. Product Backlog refinement is a continuous activity and is not a feedback loop.

Sprint Review :

  • Sprint Review is a mandatory event of Scrum and is about the Product.
  • Sprint Review is held at the end of the Sprint to inspect the Increment and adapt the Product Backlog if needed.
  • The Scrum Team and Stakeholders collaborate about what was done in the Sprint. Based on what was done in a sprint and any changes to the Product Backlog during the Sprint, attendees of this meeting collaborate on the next things items to do for optimized value.
  • The Sprint Review is at most a four-hour meeting for one-month Sprints, or shorter for shorter Sprint.
  • Sprint Review is a time-boxed event of 4 hours, or less, to conclude the development work of a Sprint.
  • Sprint Review is a mandatory event of Scrum and is a feedback loop that team members demonstrate the Increment to the stakeholders and elicit feedback from them in order to determine likely PBIs for the next Sprint. Also, the last forecasted project end date, budget, market status, new capabilities, and insights about the project could be discussed. It should be conducted at the end of each Sprint before the Sprint Retrospective.

Sprint Review purpose :

  • Sprint Review serves the Scrum Team and the Stakeholder to inspect the Increment of the Product resulting from the Sprint, asses the impact of the work on the progress, and update the Product Backlog to maximize value for the next period.
  • Eliciting feedback from the stakeholders and customers is the main purpose of the Sprint Review.
  • Fundamentally the Sprint Review is an inspect and adapt loop, not just a demo meeting. The most important topics in this event are: -Inspect the Increment through showing it by the Development Team and try it by stakeholders and customers in order to elicit feedback -Check how the current Sprint went and if the Sprint Goal was achieved or not -Adapt Product Backlog through the Team and stakeholders’ collaboration to nominate things that can be done during the next Sprint -The Product Owner explains the project status and last forecast of the project completion date -Stakeholders collaborate with the Team to adjust the budget, inspect market status and every project level interested things -Is an informal meeting and there is not any hand-off / sign-off in it.

Sprint Review participants :

  • Participants of the Sprint Review are all Scrum Team members plus key stakeholders invited by the Product Owner :
    1. Development Team
    2. Key Stakeholders
    3. Product Owner
    4. Scrum Master
  • Stakeholders are actively engaged with the Scrum Team at the Sprint Review meeting.
  • The Key Stakeholders are allowed to participate only in the Sprint Review meeting. However, any member of the Scrum Team can interact with them any time.

Sprint Review results :

  • Fundamentally the Sprint Review is an inspect and adapt loop, not just a demo meeting.
  • The result of the Sprint Review is that the Product Backlog is revised to defines the probable Product backlog Items (PBIs) for the next Sprint.

Sprint Review practice :

  • Sprint Review is an informal meeting and there is not any hand-off / sign-off in it.
  • The Product Owner explains the project status and last forecast of the project completion date.
  • Key Stakeholders collaborate with the Team to adjust the budget, inspect market status and every project level interested things
  • Is an informal meeting and there is not any hand-off / sign-off in it.
  • During this meeting attendees take into account what was done during the Sprint, and any changes to the Product Backlog, in order to collaborate what items to do next for optimized value.
  • Sprint Review is an informal meeting, not a status meeting.
  • Sprint Review is a meeting for presenting the increment for feedback and collaboration.
  • The Sprint Review is at most 4 hour(s) for a monthly Sprint and can be shorter for shorters Sprints.
  • In the Sprint Review Product Owner (PO) explains what Product Backlog items have been “done” or not “done.”
  • In the Sprint Review the Development Team demonstrates the work that is has “done” and answers questions about the increment.
  • In the Sprint Review PO discusses the Product Backlog as it stands.
  • In the Sprint Review Development Team discusses what went well during the Sprint, any problems had, and how they were solved.
  • In the Sprint Review PO projects the likely target and delivery dates for the Product Backlog as it stands.
  • In the Sprint Review everyone collaborates on what to do next, in order to provide valuable input to the subsequent Sprint Planning meeting.
  • In this meeting event the marketplace/potential use of the product is reviewed in order to asses what is the most the most valuable thing to do next.
  • In this meeting the timeline, budget, potential capabilities, and market place for the next anticipated releases of functionality/capability are reviewed.
  • Product Owner (PO) tracks total work remaining in at least every Sprint Review.
  • The amount of work remaining is compared by the Product Owner with the previous reviews to asses progress.
  • In the Sprint Review, the Team and stakeholders collaborate on adapting the Product Backlog to nominate things that can be done during the next Sprint.
  • The most important topics in the Sprint Review are:
    – Inspect the Increment through showing it by the Development Team and try it by stakeholders and customers in order to elicit feedback
    – Check how the current Sprint went and if the Sprint Goal was achieved or not
    – Adapt Product Backlog through the Team and stakeholders’ collaboration to nominate things that can be done during the next Sprint

More informations for the Scrum PSD certification here.

Leave a Reply

Your email address will not be published. Required fields are marked *