scaledagileframework.com Open in urlscan Pro
146.148.108.109  Public Scan

Form analysis
1 forms found in the DOM

GET https://scaledagileframework.com

<form class="container search-new" style="display:none" method="get" id="searchform" action="https://scaledagileframework.com">
  <input type="text" data-swplive="true" name="s" class="form-control" placeholder="Type &amp; Hit Enter..">
</form>

Text Content

FirstName LastNameuser occupation

Home

Learn
Scaled Agile Framework

My Learning

My Classes

Resources & Media Library

Customer Stories

Glossary

Implement
Implementation Roadmap

Lean Portfolio Management

Organize Around Value

Value Stream Mapping

Practice
SAFe ART & Team Events

My SAFe Events (Collaborate)

My SAFe Assessments

SAFe Toolkits

Connect
Community Forums

Summit & Events

Skip to content
REGISTER NOW




 * Search
   

Framework
 * Framework
 * About
   * About SAFe
   * SAFe Contributors
   * What’s new in SAFe 6.0?
   * Presentations and Videos
   * Posters and Graphics
   * Contact Us
 * Blog
 * Read More
   * Extended SAFe Guidance
   * Community Contributions
   * SAFe Beyond IT
 * SAFe Training

> Few are those who see with their own eyes and feel with their own hearts.
> 
> —Albert Einstein


ITERATION REVIEW

--------------------------------------------------------------------------------

Note: For more on SAFe Scrum, please read the additional Framework articles in
the Scrum series, including SAFe Scrum, Scrum Master/Team Coach, Iterations,
Iteration Planning, Iteration Goals, and Iteration Retrospective

--------------------------------------------------------------------------------

The Iteration Review is a regular SAFe Scrum event where the team inspects the
iteration increment, assesses progress, and adjusts the team backlog.


DETAILS

The iteration review is the second to last event of the iteration. It provides a
way to regularly gather immediate, contextual feedback from the team and its
stakeholders. The iteration review offers several benefits:

 * It brings closure to the iteration timebox
 * It allows team members to demonstrate their contributions and to take some
   satisfaction and pride in their work
 * It provides an opportunity for the team to receive feedback to improve the
   solution under development
 * It shows the results of the latest system increment to help determine future
   work

An iteration review is where the team demos a working, tested increment. No
slides are needed. Instead, the focus is on the solution instead of a
presentation. The team and stakeholders review the accomplishments in the
iteration—based on this information, attendees collaborate on what to do next.
The Team Backlog may also be adjusted to meet new opportunities.


INPUTS AND OUTPUTS OF THE ITERATION REVIEW

Inputs to the iteration review include:

 * Iteration goals and PI Objectives
 * The team’s increment deployed to a staging environment (or production
   environment where appropriate)
 * A brief list of work to be demoed to prepare people for what they are about
   to see

A successful iteration review event delivers the following outputs:

 * Feedback on the increment and progress toward the iteration goals and broader
   PI Objectives
 * Adjusted Team Backlog based on feedback
 * Identification of risks and impediments


PREPARATION

The preparation for the iteration review begins during Iteration Planning, where
teams start thinking about how they will demo the committed Stories. ‘Beginning
with the end in mind’ facilitates iteration planning and alignment, fostering a
more thorough understanding of the functionality needed ahead of iteration
execution.


PROCESS

The PO starts the iteration review by discussing the iteration goals and their
status. It proceeds with a walk-through of all the committed stories. Teams
demonstrate the significant new behavior and knowledge gained from the
iteration’s completed stories, Spikes, Refactors, and Nonfunctional Requirements
(NFRs). The demos should be part of a working, tested system—preferably in a
staging environment closely resembling production. Spikes and NFRs can be
demonstrated via a presentation of findings if the functionality lacks a user
interface. Stakeholders provide feedback on the stories that the team demoed,
which is the primary goal of the review.

The team reflects on stories not completed after the demo and why they could not
finish them. This discussion usually results in discovering impediments or
risks, false assumptions, changing priorities, estimating inaccuracies,
over-commitment, or other problems with Team Flow. These findings often lead to
further study in the Iteration Retrospective and may result in improvements to
support better planning and execution going forward. Figure 1 shows an iteration
review in action.

Figure 1. An Agile team demoing a working, tested increment

The team reflects on how well it did within the iteration and determines its
progress toward its Team PI objectives. It finishes the event by refining
the Team Backlog, based on the feedback received, before the next iteration
planning event.


ATTENDEES

Attendees at the iteration review include:

 * The Product Owner (PO)
 * Scrum Master/Team Coach
 * All team members and other stakeholders or subject matter experts
 * Stakeholders, which may also include other teams or trains.

Although Agile Release Train (ART) stakeholders may attend, their interests and
the level of detail they require are usually better aligned with the System
Demo.


AGENDA

The timebox for the event is a maximum of 90 minutes for a two-week iteration.
Figure 2 shows an example agenda and a description of each item.

Figure 2. An example iteration review agenda

The Scrum Master/Team Coach or PO typically facilitates the iteration review for
the team, ensuring they stay within the agreed event agenda and timebox.
Following are descriptions of the example agenda:

 1. Review iteration goals – Discuss the status of each iteration goal. Teams
    may also review PI objectives for a broader context.
 2. Demonstrate completed stories – The iteration review proceeds with a
    walk-through and demonstration of each completed story (spikes, NFRs, and
    any other work finished by the team). Demos should show progress towards
    iteration goals, PI objectives, solution changes, test scenarios, or a
    prototype representing the user’s environment. Spikes can be demoed as a
    presentation of findings or learning. The team and stakeholders should ask
    questions and provide constructive feedback.
 3. Reflect on any incomplete stories – Next, the team should reflect on missed
    iteration goals and stories they did not complete to identify opportunities
    for future improvement. This discussion usually results in discovering
    impediments or risks, false assumptions, changing priorities, estimating
    inaccuracies, or over-commitment.
 4. Identify risks and impediments – After the demo and reflecting on any
    incomplete stories, the team identifies new risks or dependencies that might
    impact achieving the PI objectives. Teams often use the ROAM (Resolved,
    Owned, Accepted, Mitigated) process to address the risks as needed.
 5. Refine the Team Backlog – Based on stakeholder feedback, the team can refine
    their backlog to reflect any adjustments before the next Iteration Planning
    event.


GUIDELINES

Below are some tips for running a successful iteration review event:

 * Limit preparation to less than two hours
 * Timebox the event to about 90 minutes
 * Minimize the use of slides; the iteration review is intended to garner
   feedback on working, tested system components
 * Verify that completed stories meet the definition of done (DoD)
 * Demonstrate incomplete stories if enough functionality is available to get
   feedback
 * Encourage providing constructive feedback and celebration of the team’s
   accomplishments
 * If a significant stakeholder cannot attend, the PO should follow up to report
   progress and get feedback

Note: Teams applying Continuous Delivery  will generally review completed
Stories or Features as soon as they are available rather than waiting until the
end of the iteration.

--------------------------------------------------------------------------------


LEARN MORE

[1] Leffingwell, Dean. Agile Software Requirements: Lean Requirements Practices
for Teams, Programs, and the Enterprise. Addison-Wesley, 2011.



[2] Leffingwell, Dean. Scaling Software Agility: Best Practices for Large
Enterprises. Addison-Wesley, 2007.



 

Last update: 23 November 2022

The information on this page is © 2010-2024 Scaled Agile, Inc. and is protected
by US and International copyright laws. Neither images nor text can be copied
from this site without the express written permission of the copyright holder.
Scaled Agile Framework and SAFe are registered trademarks of Scaled Agile, Inc.
Please visit Permissions FAQs and contact us for permissions.


FRAMEWORK

 * Download SAFe Posters & Graphics
 * Watch and download SAFe videos and presentations
 * Blog


TRAINING

 * Course Calendar
 * About Certification
 * Become a Trainer


CONTENT & TRADEMARKS

 * FAQs on how to use SAFe content and trademarks
 * Permissions Form
 * Usage and Permissions


SCALED AGILE, INC


CONTACT US

5400 Airport Blvd., Suite 300
Boulder, CO 80301 USA


BUSINESS HOURS

Weekdays: 9am to 5pm
Weekends: CLOSED

© 2024 Scaled Agile, Inc.
 * Get News
 * Privacy Policy
 * Code of Conduct
 * Remote Training Policy

 * DAEA2F06-E0FD-4DBA-8560-2D61F70C362E
 * 
 * 4F60BB82-0505-4C99-AE8E-416215FB7376
 * 41FDBA7F-305F-4E28-88A8-78941B743DBE

We use cookies to analyze website performance and visitor data, deliver
personalized content, and enhance your experience on the site. Cookie Policy. By
clicking Accept you consent to the use of all cookies. Otherwise click Adjust
Cookie Settings.
Adjust Cookie Settings Accept
Manage consent
Close

PRIVACY OVERVIEW

This website uses cookies to improve your experience while you navigate through
the website. Out of these cookies, the cookies that are categorized as necessary
are stored on your browser as they are essential for the working of basic
functionalities...
Necessary
Necessary
Always Enabled
Necessary cookies are absolutely essential for the website to function properly.
These cookies ensure basic functionalities and security features of the website,
anonymously.

CookieDurationDescriptioncookielawinfo-checbox-analytics11 monthsThis cookie is
set by GDPR Cookie Consent plugin. The cookie is used to store the user consent
for the cookies in the category "Analytics".cookielawinfo-checbox-functional11
monthsThe cookie is set by GDPR cookie consent to record the user consent for
the cookies in the category "Functional".cookielawinfo-checbox-others11
monthsThis cookie is set by GDPR Cookie Consent plugin. The cookie is used to
store the user consent for the cookies in the category
"Other.cookielawinfo-checkbox-necessary11 monthsThis cookie is set by GDPR
Cookie Consent plugin. The cookies is used to store the user consent for the
cookies in the category "Necessary".cookielawinfo-checkbox-performance11
monthsThis cookie is set by GDPR Cookie Consent plugin. The cookie is used to
store the user consent for the cookies in the category
"Performance".viewed_cookie_policy11 monthsThe cookie is set by the GDPR Cookie
Consent plugin and is used to store whether or not user has consented to the use
of cookies. It does not store any personal data.

Functional
functional
Functional cookies help to perform certain functionalities like sharing the
content of the website on social media platforms, collect feedbacks, and other
third-party features.
Performance
performance
Performance cookies are used to understand and analyze the key performance
indexes of the website which helps in delivering a better user experience for
the visitors.
Analytics
analytics
Analytical cookies are used to understand how visitors interact with the
website. These cookies help provide information on metrics the number of
visitors, bounce rate, traffic source, etc.
Advertisement
advertisement
Advertisement cookies are used to provide visitors with relevant ads and
marketing campaigns. These cookies track visitors across websites and collect
information to provide customized ads.
Others
others
Other uncategorized cookies are those that are being analyzed and have not been
classified into a category as yet.
Save & Accept



Notifications