We think you have liked this presentation. If you wish to download it, please recommend it to your friends in any social system. Share buttons are a little bit lower. Thank you!
Presentation is loading. Please wait.
Published byMarie Bragdon
Modified over 2 years ago
Sprint Review Results Example Template
License and Contact Details This work is licensed under the Creative Commons Attribution-ShareAlike 4.0 International License. To view a copy of this license, visit To see the blog post about this template and download the PowerPoint version please visit: agil8 © agil
About the Sprint Review To download the PowerPoint version of this template please visit A Sprint Review is held at the end of each Sprint to inspect the Product Increment and, if required, adapt the Product Backlog. The Sprint Review meeting is timeboxed to 1 hour for each week of the Sprint. The Scrum Team and stakeholders collaborate to understand what happened in the Sprint, what changes occurred and what might be done next. The Sprint Review is an informal meeting, the intention of which is to create transparency, feedback and collaboration. Within the Sprint Review meeting: The Product Owner identifies what has been Done and what has not been Done The Development Team describes how the Sprint went: what went well, what problems it had, and how it addressed them (they will hold a Sprint Retrospective following this meeting) The Product Increment is demonstrated, questions about it are fielded by the Scrum Team and any potential new Product Backlog Items are identified The Product Owner leads a review of the Product Backlog, drawing attention to any changes since the last Sprint Review The Product Owner presents projected completion dates based on progress to date and everyone in the meeting collaborates to determine if the Product Backlog should be changed and what to do next © agil
About this Template People and interactions should be valued over processes and tools … but it is still a good idea to capture the results of key meetings so that decisions and the rationale behind them are not lost and can be communicated to those not present This template should be adapted for your own context It is presented in PowerPoint for the sake of convenience and because many teams use it Any suitable tool can be used instead: from a white board or flip charts with a digital camera to record them, to direct entry into a backlog management and collaboration software tool © agil
Sprint Review Team name: Date of review: Time: Venue: Product Owner: ScrumMaster: Sprint Goal: Stakeholders present: Team members present: © agil
Product Backlog Item Approval RefProduct Backlog Item Name and Type (e.g. Functional/NFR/New Feature/Maintenance/Spike/Dev Environment) No of Points Done? Y/N? © agil
Development Team View Problems encountered? How solved? © agil What went well during the Sprint? Velocity this Sprint:Typical historical velocity:
Product Backlog Items to be Demod RefProduct Backlog Item NameComments/Questions © agil
Changes to Product Backlog In this Sprint Changes to Full Planned Scope Points estimated in Full Planned Scope at start of Sprint: Points estimated in Full Planned Scope at end of Sprint: Reason/s for Change: © agil Changes to Minimum Scope Points estimated in Minimum Scope at start of Sprint: Points estimated in Minimum Scope at end of Sprint: Reason/s for Change:
Product Backlog Review Likely completion dates based on progress so far: Full planned scope: dd/mm/yy Minimum scope: dd/mm/yy © agil Agreed adjustments to overall Product Backlog:
Probable Product Backlog Items for Next Sprint RefProduct Backlog Item NameComments © agil
Scrum in 10 slides. Responsible for the product backlog and maximizing the product ROI. Represents the users Clearly expresses backlog items Orders.
What is Scrum? This Stack is based upon the Redistributable Scrum Introduction Stack from the Scrum Alliance This work is licensed under the Creative Commons.
Iterative Development: Done Simply Emily Lynema NCSU Libraries Code4Lib 2010.
Software Development QA Best Practices May 20, 2010 Suzette Hackl, CSM Senior Project Manager Skyline Technologies, Inc.
Applying evo to a project An Agile and EVO Workshop Based on the article Measuring Agile Value in Overload 89, by Ryan Shriver, and used with his permission.
Testing Relational Database. Overview Once the design of a database system has been completed, the developers are ready to move into the implementation.
Armstrong Process Group, Inc. Copyright © , Armstrong Process Group, Inc., and others All rights reserved Armstrong Process.
Mountain Goat Software, LLC An Introduction to Scrum.
The Enterprise Skills Story Demonstrating the enterprise skills.
JASS 2006Agile Project Management - Scrum1 Introduction Classical methods of software development have many disadvantages: -huge effort during the planning.
Chapter - 5 Understanding Requirements Unit II. Introduction Definition : “The broad spectrum of tasks and techniques that lead to an understanding of.
Every Job Has A Customer while everyone is logging on, please ensure your phone is muted and your chat window is open Customer Service.
SIVA 1 Construction Management-Lec3 Planning and Scheduling-II Dr. Attaullah Shah.
The Charter Partners ® Guide Effective Meeting Management Good meetings are managed events... they just dont happen! © Charter Partners USA, Inc. January.
Group Projects Making working software as a team Bruce Scharlau, University of Aberdeen, 2011.
An HML white paper: Agile IT A value-driven approach to IT delivery.
Prince2 – The useful bits…. Objective… Quick intro to Prince2 and how key elements were adopted at Salford Present a simple structured approach to organising.
A method for addressing any large problem. Carefully consider the problem. Define the problem. Ask yourself the following questions: What is it that I.
© Connextra 2003 John Nolan & Rachel Davies Connextra.
Working in a Business Enterprise: An Introduction Access 2.
Chapter:4 Principles That Guide Practice Unit II.
Neil B. Harrison Utah Valley University. Who Who And a bit of history What we are doing What we are doing Creating a pattern language of Scrum A few words.
They tell me that I'm a BIM Coordinator. How did that happen and what does it mean? Brett C. Gatti Design Technology Leader.
Tactical Product Ownership day 1: product scope and planning Jeff Patton AgileProductDesign.com
The Masterclass Strategy ◦ What is it? ◦ Influencing ◦ AHP strategy standard Clinical Governance ◦ Elements of CG ◦ Risk management ◦ Evaluation and.
The Project Cycle Management Course presented by Simon Pluess World Alliance of YMCAs.
University of Leeds Project Management Stuart Roberts School of Computing.
A Guide-How to make a 15-minute presentation template. Use this as a guide when creating your business presentation for early-stage investors. Each slide.
Introduction to Scrum for Software Project Management Kevin Thompson, Ph.D. Project Management Professional Certified Scrum Practitioner Certified Scrum.
Lecture 6 Conceptual Design Brainstorming Card sort Semantic networks Personas Scenarios, flowcharts and cognitive walkthroughs Both of these are excellent.
© 2016 SlidePlayer.com Inc. All rights reserved.