1

00:00:00,150 --> 00:00:08,070

And finally, because we are continuously improving, we need to do a sprint
retrospective, which is

2
00:00:08,070 --> 00:00:13,230
kind of like a lessons learned meeting where we look back on what worked well and
what didn't so that

3
00:00:13,230 --> 00:00:21,990
we can improve the work plan in the teamwork and anything else so that the team on
the products keeps

4
00:00:21,990 --> 00:00:22,680
improving.

5
00:00:22,680 --> 00:00:28,530
From Sprint to Sprint, the scrum master will facilitate this meeting after the
Sprint review.

6
00:00:28,530 --> 00:00:35,520
But before the next sprint planning session, the scrum master must also make sure
that it's a positive

7
00:00:35,520 --> 00:00:36,750
and productive meeting.

8
00:00:37,200 --> 00:00:38,840
You're not looking for blame here.

9
00:00:39,000 --> 00:00:46,320
You you're looking for finding solutions to problems and everybody's feedback
should be respected,

10
00:00:46,320 --> 00:00:48,530
listened to and understood.

11
00:00:49,530 --> 00:00:56,490
The Sprint retrospective is to inspect how the last sprint went with regards to
people, relationships,

12
00:00:56,490 --> 00:01:04,470
processes and tools, identify and order the majority items that went well and
potential improvements,

13
00:01:04,920 --> 00:01:10,470
and to create a plan for implementing improvements to the way the Scrum team does
its work.

14
00:01:10,740 --> 00:01:16,080
The whole team will take this feedback on board and the scrum master particularly
will try and develop

15
00:01:16,080 --> 00:01:21,440
new processes and practices to make it more effective and enjoyable for the next
sprint.

16
00:01:21,720 --> 00:01:26,400
And that concludes the sprint ceremonies or sprint events.

17
00:01:26,580 --> 00:01:32,670
Not too complicated, not too many of them, but a really powerful way to make sure
that the team is

18
00:01:32,670 --> 00:01:40,340
effective, efficient and work gets done on the right work gets done to deliver
value to the customer.

19
00:01:41,400 --> 00:01:47,250
These ceremonies are really important to the whole scrum framework and the product
owner, so I am going

20
00:01:47,250 --> 00:01:50,570
to revisit some of the concepts of these throughout the course.

21
00:01:50,790 --> 00:01:55,710
It might be worth coming back to these lectures once you've got further through the
course, because

22
00:01:55,710 --> 00:01:57,830
things are going to make a lot more sense.