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 DetailsThis 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 © agil8 2014
About the Sprint ReviewTo 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 © agil8 2014
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 © agil8 2014
Sprint Review Team name: Date of review: Time: Venue: Product Owner: ScrumMaster: Sprint Goal: Stakeholders present: Team members present: © agil8 2014
Product Backlog Item ApprovalRef Product Backlog Item Name and Type (e.g. Functional/NFR/New Feature/Maintenance/Spike/Dev Environment) No of ‘Points’ Done? Y/N? 1 2 3 4 5 6 7 8 9 10 11 © agil8 2014
Development Team View Velocity this Sprint: Typical historical velocity: What went well during the Sprint? Problems encountered? How solved? © agil8 2014
Product Backlog Items to be Demo’dRef Product Backlog Item Name Comments/Questions 1 2 3 4 5 6 7 8 9 10 11 © agil8 2014
Changes to Product Backlog In this SprintChanges 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: 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: © agil8 2014
Product Backlog ReviewLikely completion dates based on progress so far: Full planned scope: dd/mm/yy Minimum scope: dd/mm/yy Agreed adjustments to overall Product Backlog: © agil8 2014
Probable Product Backlog Items for Next SprintRef Product Backlog Item Name Comments 1 2 3 4 5 6 7 8 9 10 11 © agil8 2014
Scrum. An evolutionary/iterative/incremental/agile software process The main roles in Scrum are: – Scrum team: Team of software developers – Scrum master.
ITEC 370 Lecture 24 Lifecycles. Review Questions? –Grades for Requirements/Design Doc F give prototype demonstration –Testing plan for your software Maintenance.
Scrum in 10 slides.
Copyright © by Mark J. Sebern Software Engineering Process I SE 2800.
Scrum in 10 slides by Pierre Mengal – Scrum In Ten Slides v1.1 is licensed under a Creative Commons Attribution-NoDerivs 3.0 Unported.
10/8/2008Clarity PLC Fall WebConference This slide copyright Jeffrey A. Bloom Tips and Techniques Leveraging Clarity’s Notes Facility & SCRUM in.
What is Agile? Agile is a software methodology based on iterative and incremental development, where requirements and solutions evolve through collaboration.
Software Engineering- Scrum 徐 瑋 Alen 林芳瑜 Flora 1.
Introduction to Agile. Introduction Who is this guy?
1 - Agile in a nutshell. 2 - Basic principles ●Relies on an iterative, incremental development mechanism with continuous adaptation to customer requirements.
Dr. Nguyen Hai Quan. Why SCRUM? What is SCRUM? Some terms SCRUM Meetings Sprint Estimation Product backlog Sprint backlog Whiteboard.
Copyright © 2012 by Mark J. Sebern Scrum Overview (from
Using Scrum to Improve Teamwork, Communication, Quality and Speed
The Business Analyst Role in Agile Projects
Iterative Development: Done Simply Emily Lynema NCSU Libraries Code4Lib 2010.
Managing Agile Software Development Teams Using Scrum AKA: Wrangling Developers for Fun and Profit!
Informed Traveler Program and Applications Agile / Scrum Overview Jerry Inberg.
SCRUM introduction 6 April Scrum Team are known as pigs because they’re committed to delivering Sprint Goal People who are involved but not dedicated.
Managing a Project Using an Agile Approach and the PMBOK® Guide
End of Sprint Meetings (Ceremonies)
Introduction to Scrum.
Using Scrum to Improve Teamwork, Communication, Quality and Speed.
Rules of the Game Loosely based upon the TV show, “Who wants to be a millionaire.®” Once the question is read, you will have 30 seconds to discuss.
The Scrum Framework Presented by Somnath Ghosh Scrum Practitioner 24 hours weeks.
User assignments (product owner) ‘circle’ 1 st sprint: ◦ Scrum Boards (informative workspace) Product -, release -, sprint -, defect backlog
1 Agile Methodology & Programming Ric Holt July 2009.
#msdevcon Community Track IMPLEMENTATION OF SCRUM Bernardin Katić Insa Investment Software AG.
THE AGILE MENTALITY CHAPTER Topics Why Use Agile and Scrum? Agile Development –Manifesto for Agile Software Development Scrum Methodology.
Barnes & Noble Alonda Morgan. Agile UX Agile.
Agile CRM Applying the Scrum Methodology for Deployment Neil Benson.
Agile Methodology. -Dhanashree Kumkar -Plus91 Technologies.
Scrum CS These slides were created by Kevin Schenk, BS in Computer Science, Purdue University, 2012.
> Sprint Planning Presentation API Release: Date: Presented by:
OFFICE OF INFORMATION AND TECHNOLOGY Mobile Applications Scrum Framework November 21, :00 am (EST) Seal of the U.S. Department of Veterans Affairs.
What is Scrum Process? Where is it used? How is it better?
Mobile Apps: Review and Retrospectives Refresher Agile Transformation Team 1.
Process is continuously improving Have Definition of Done (DoD) DoD achievable within each iteration Team respects DoD The bottom line Delivering working,
Release and Iteration Planning September 13, 2008.
Sprint Plans and Burndown Charts David Millard | davidmillard.org.
© Timothy Korson Page 1 Scrum by Dr. Korson For CPTR 209 Software Engineering Version
Scrum Task Board Template Company name Stories To Do In Progress TestingDone This is a sample text. Replace it with your own text. This is a sample text.
Agile-SCRUM. Introduction to SCRUM Sanil Xavier What is Scrum?
Agenda −Scrum with TFS 2010 using MSF for Agile 5.0 −Planning the Project −How do you plan the project? −Project planning in TFS 2010 −Planning a Sprint.
Agile Information Management Development. Agile Project Management Characteristics Acceptance and even welcome of changing requirements Incremental.
Business Intelligence in Classroom WHY:. Purpose – knowledge to make an informed career decision Process – Use Scrum method of project management.
Team Development with Microsoft Scrum 1.0 Doncho Angelov Developer Evangelist Microsoft Bulgaria.
If you want to survive in marketing, it’s time to know agile. Dan Naden VersionOne Community Manager.
Agile Design and SCRUM Brent M. Dingle, Ph.D. “For the last few centuries, … science has been attempting to break matter down into ever smaller bits, in.
© 2017 SlidePlayer.com Inc. All rights reserved.