1
00:00:00,293 --> 00:00:03,126
(classical music)

2
00:00:05,960 --> 00:00:08,470
The Iteration review is
a cadence-based event

3
00:00:08,470 --> 00:00:10,450
in which each team inspects the increment

4
00:00:10,450 --> 00:00:13,080
at the end of every
iteration to assess progress

5
00:00:13,080 --> 00:00:15,643
and then adjust its backlog
for the next Iteration.

6
00:00:17,010 --> 00:00:19,360
During the Iteration
review, each Agile team

7
00:00:19,360 --> 00:00:21,720
measures and then
demonstrates its progress

8
00:00:21,720 --> 00:00:23,930
by showing working stories
to the product owner

9
00:00:23,930 --> 00:00:26,310
and other stakeholders for their feedback.

10
00:00:26,310 --> 00:00:29,460
Teams demo new stories, spikes, refactors

11
00:00:29,460 --> 00:00:31,780
and nonfunctional requirements.

12
00:00:31,780 --> 00:00:32,900
In this short video,

13
00:00:32,900 --> 00:00:35,100
we'll walk you through
how you can achieve this

14
00:00:35,100 --> 00:00:37,886
and share tips from
enterprises around the globe.

15
00:00:37,886 --> 00:00:40,719
(classical music)

16
00:00:42,950 --> 00:00:44,740
The preparation for the Iteration review

17
00:00:44,740 --> 00:00:46,800
begins during Iteration planning

18
00:00:46,800 --> 00:00:49,310
where teams start thinking
about how they will demo stories

19
00:00:49,310 --> 00:00:50,980
to which they have committed.

20
00:00:50,980 --> 00:00:52,570
Beginning with the end in mind

21
00:00:52,570 --> 00:00:54,900
facilitates Iteration
planning and alignment,

22
00:00:54,900 --> 00:00:56,730
fostering a more thorough understanding

23
00:00:56,730 --> 00:01:00,960
of the functionality needed
before Iteration execution.

24
00:01:00,960 --> 00:01:02,270
Ahead of the Iteration review,

25
00:01:02,270 --> 00:01:06,200
the team should update the
status of its Iteration goals.

26
00:01:06,200 --> 00:01:07,200
Agree on the presenter

27
00:01:07,200 --> 00:01:09,800
and order of the stories
to be demonstrated.

28
00:01:09,800 --> 00:01:11,430
Prepare any findings and results

29
00:01:11,430 --> 00:01:13,720
required to demonstrate stories.

30
00:01:13,720 --> 00:01:15,180
Make sure the time and location

31
00:01:15,180 --> 00:01:17,480
of the Iteration review is known.

32
00:01:17,480 --> 00:01:19,010
Invite any other stakeholders

33
00:01:19,010 --> 00:01:20,860
who will want to see the team's progress

34
00:01:20,860 --> 00:01:22,910
which may include members of other teams.

35
00:01:23,760 --> 00:01:26,330
Note that although Agile
Release Train stakeholders

36
00:01:26,330 --> 00:01:28,900
may attend, their interest
and level of detail

37
00:01:28,900 --> 00:01:31,373
are usually better served
by the System Demo.

38
00:01:32,604 --> 00:01:35,437
(classical music)

39
00:01:36,670 --> 00:01:38,940
The Iteration review
is typically timeboxed

40
00:01:38,940 --> 00:01:40,720
to one to two hours max.

41
00:01:40,720 --> 00:01:42,690
The Iteration review starts by going over

42
00:01:42,690 --> 00:01:45,770
the Iteration goals and discussing status.

43
00:01:45,770 --> 00:01:47,320
It then proceeds with a walk-through

44
00:01:47,320 --> 00:01:49,370
of all the committed stories.

45
00:01:49,370 --> 00:01:53,000
Each completed story is demoed
in a working tested system,

46
00:01:53,000 --> 00:01:54,640
preferably in a staging environment

47
00:01:54,640 --> 00:01:57,220
that closely resembles the
production environment.

48
00:01:57,220 --> 00:02:00,570
Spikes are demonstrated via
a presentation of findings.

49
00:02:00,570 --> 00:02:03,690
Note that many to most stories
will have been achieved

50
00:02:03,690 --> 00:02:05,230
during the course of the Iteration

51
00:02:05,230 --> 00:02:06,880
and may already have been demoed,

52
00:02:06,880 --> 00:02:10,030
in which case a quick update
may be more appropriate.

53
00:02:10,030 --> 00:02:11,610
Stakeholders provide feedback

54
00:02:11,610 --> 00:02:13,120
on the stories that are demoed

55
00:02:13,120 --> 00:02:15,713
which is the primary goal
of the review process.

56
00:02:16,570 --> 00:02:18,370
After the demo, the team reflects

57
00:02:18,370 --> 00:02:20,760
on which stories were
not completed, if any,

58
00:02:20,760 --> 00:02:23,340
and why the team was
unable to finish them.

59
00:02:23,340 --> 00:02:26,260
This discussion usually
reveals impediments or risks,

60
00:02:26,260 --> 00:02:28,970
false assumptions, changing priorities,

61
00:02:28,970 --> 00:02:32,000
estimating inaccuracies or overcommitment.

62
00:02:32,000 --> 00:02:33,810
These findings may lead to further study

63
00:02:33,810 --> 00:02:35,270
in the Iteration retrospective

64
00:02:35,270 --> 00:02:36,720
about how the next Iterations

65
00:02:36,720 --> 00:02:39,070
can be better planned and executed.

66
00:02:39,070 --> 00:02:42,090
As Scrum Master, your job
is to keep this process

67
00:02:42,090 --> 00:02:44,638
on track and ensure
that the goals are met.

68
00:02:44,638 --> 00:02:47,471
(classical music)

69
00:02:50,150 --> 00:02:51,860
Here are some tips to help you deliver

70
00:02:51,860 --> 00:02:53,713
a successful Iteration review.

71
00:02:54,670 --> 00:02:58,010
Limit demo preparation by team
members to one to two hours.

72
00:02:58,010 --> 00:03:00,200
Too much demo overhead slows down the team

73
00:03:00,200 --> 00:03:02,590
and jeopardizes the value of the demo.

74
00:03:02,590 --> 00:03:04,650
Minimize the use of slides.

75
00:03:04,650 --> 00:03:06,690
After all, the purpose
of the Iteration review

76
00:03:06,690 --> 00:03:09,660
is to get feedback on working
software functionality,

77
00:03:09,660 --> 00:03:12,240
hardware components, and other concerns.

78
00:03:12,240 --> 00:03:15,430
Verify that completed stories
meet the definition of done

79
00:03:15,430 --> 00:03:18,030
and have been accepted
by the Product Owner.

80
00:03:18,030 --> 00:03:19,910
Demo incomplete stories too

81
00:03:19,910 --> 00:03:23,090
if enough functionality is
available to get feedback.

82
00:03:23,090 --> 00:03:25,270
Encourage providing constructive feedback

83
00:03:25,270 --> 00:03:27,630
and celebrating the accomplishments.

84
00:03:27,630 --> 00:03:29,940
If a significant
stakeholder cannot attend,

85
00:03:29,940 --> 00:03:32,190
the Product Owner should
follow up with that person

86
00:03:32,190 --> 00:03:34,563
to report progress and
to get their feedback.

87
00:03:35,530 --> 00:03:36,920
Note that teams that are in flow

88
00:03:36,920 --> 00:03:39,560
with Continuous Delivery
and Continuous Deployment

89
00:03:39,560 --> 00:03:42,150
will likely have reviewed
and accepted many stories

90
00:03:42,150 --> 00:03:43,980
during the course of the Iteration.

91
00:03:43,980 --> 00:03:46,240
In this case, the review
is more like a status

92
00:03:46,240 --> 00:03:50,091
and feedback session than a
detailed story by story review.

93
00:03:50,091 --> 00:03:52,924
(classical music)

94
00:03:54,000 --> 00:03:56,290
To recap, remember the Iteration review

95
00:03:56,290 --> 00:03:59,030
serves three important functions.

96
00:03:59,030 --> 00:04:01,460
First, it brings closure
to the Iteration timebox

97
00:04:01,460 --> 00:04:03,440
that many individuals have contributed to

98
00:04:03,440 --> 00:04:06,460
in order to provide new
value to the business.

99
00:04:06,460 --> 00:04:08,560
Second, it gives teams an opportunity

100
00:04:08,560 --> 00:04:11,060
to show the contributions
they've made to the business

101
00:04:11,060 --> 00:04:13,130
and to take some satisfaction and pride

102
00:04:13,130 --> 00:04:15,390
in their work and progress.

103
00:04:15,390 --> 00:04:18,430
And third, it allows stakeholders
to see working stories

104
00:04:18,430 --> 00:04:21,350
and provide feedback
to improve the product.

105
00:04:21,350 --> 00:04:23,770
For more information, videos, and toolkits

106
00:04:23,770 --> 00:04:25,710
on the role of Scrum Master and SAFe®,

107
00:04:25,710 --> 00:04:28,580
please consult the SAFe®
Community Platform and participate

108
00:04:28,580 --> 00:04:31,330
in the SAFe Scrum Master
community of practice.

109
00:04:31,330 --> 00:04:33,760
Additional reading on the
SAFe Scrum Master role

110
00:04:33,760 --> 00:04:35,380
and Iteration planning can be found

111
00:04:35,380 --> 00:04:38,213
in the articles on the Scaled
Agile Framework® website.

112
00:04:39,660 --> 00:04:41,550
- [Narrator] This video
depicts the Iteration review

113
00:04:41,550 --> 00:04:44,370
taking place in person
which isn't always possible.

114
00:04:44,370 --> 00:04:46,440
For enterprises practicing
SAFe with remote

115
00:04:46,440 --> 00:04:49,740
and distributed teams, here
are our top recommendations

116
00:04:49,740 --> 00:04:51,973
for a successful remote iteration review.

117
00:04:52,850 --> 00:04:55,710
Update the status of the iteration goals.

118
00:04:55,710 --> 00:04:56,880
Agree on the presenter

119
00:04:56,880 --> 00:04:59,083
and order of the stories
to be demonstrated.

120
00:04:59,950 --> 00:05:01,270
Update the team backlog

121
00:05:01,270 --> 00:05:04,210
based on the feedback
on the stories demoed.

122
00:05:04,210 --> 00:05:05,780
For more remote support,

123
00:05:05,780 --> 00:05:09,110
please use the Remote Iteration
Review Facilitator Checklist

124
00:05:09,110 --> 00:05:11,270
in the Remote ARTs toolkit.

125
00:05:11,270 --> 00:05:14,187
(classical music)