Lesson 12: Events overview
In this, and the following lessons, we will talk about the events in Scrum. Let’s start with a quick overview.
2020 update notes
A few things have changed in the latest version of the Scrum Guide (2020), and the ASF exam is updated based on those changes. However, our videos are not updated yet; so, please note the following changes:
- There’s no “development team” anymore, but only Developers.
- The recommended team size is now “10 people or less” for the whole Scrum Team.
- It’s now called “self-managing” instead of “self-organizing” (same concept, different name).
- There’s a Product Goal now, which is part of the Product Backlog, and sets the overall direction for the product.
- The Sprint Goal is now considered as part of the Sprint Backlog.
- The concept of commitments is introduced for the artifacts:
- Product Goal is the commitment for the Product Backlog.
- Sprint Goal is the commitment for the Sprint Backlog.
- Definition of Done is the commitment for the Increment.
- The Definition of Done is created by the whole Scrum Team now, and not only by the Developers.
- Now, any time you finish an item (based on the Definition of Done), a new Increment is formed. It’s not about having just one Increment at the end of the Sprint.
- The guide doesn’t suggest 10% as the ceiling for the amount of time Developers spend on Product Backlog refinement.
- Sprint Planning has three topics now:
- Why? -> Sprint Goal
- What? -> Items from the Product Backlog
- How? -> Tasks created by decomposing the items
- “Estimating” is now called “sizing”. So, it’s the responsibility of the Developers to size the Product Backlog items.
- “Value” is no longer one of the mandatory attributes of the Product Backlog items. The mandatory attributes are description, size, and order.
- Instead of calling the Increments “potentially releasable”, the new guide calls them “usable” (more or less the same concept).
- 00:04 – Welcome back.
- 00:07 – In the previous lessons, we talked about roles in Scrum, the three roles that we have, and a few things that we should remember.
- 00:14 – For example, we shouldn’t have extra titles.
- 00:17 – We don’t have testers, we have developers who are ex– who are expert in testing.
- 00:22 – And, for example, the fact that we shouldn’t have extra roles in Scrum.
- 00:27 – Now, in future lessons, we’re going to talk about the events.
- 00:31 – And these are the events that we have. You already have an idea of what they are about.
- 00:36 – Now, we will have a quick review again, once more, before I go through each of them in one of the future lessons.
- 00:44 – People involved in those events is important.
- 00:51 – For the Sprint Planning, we have the project team members, which are the three roles - the Product Owner, the Scrum Master, and the Developers.
- 00:59 – For the Sprint Retrospective, the same. We have all those three roles.
- 01:06 – The Sprint Review is different. As you can imagine, we also have the customer.
- 01:10 – It’s not only the team, it’s also the customer.
- 01:14 – And the Daily Scrum is very special.
- 01:17 – Daily Scrum, that’s something I just realized that I forgot to mention in the review, in the first review.
- 01:23 – Besides all those meetings, we also have daily meetings, 15-minute meetings where people get together and talk about the things that they have done and they’re going to do.
- 01:32 – That’s called Daily Scrum, and the important thing is that it’s only for the Development Team, not the other people.
- 01:40 – What it means is not that other people are not allowed to come to the meeting.
- 01:46 – Everyone can come to any of our meetings, as long as they don’t speak.
- 01:52 – They just attend, they don’t participate.
- 01:55 – Only the developers are supposed to be active in this meeting.
- 01:59 – Okay. For the durations.
- 02:02 – The Sprint Planning event is 8 hours if the whole Sprint is 1 month long, and if you have shorter Sprints, then it would be shorter proportionally.
- 02:17 – For example, if you have 2-week Sprints, then your Sprint Planning would be 4 hours, and all of these are timeboxed. Do you remember?
- 02:25 – You don’t expand them. So, if your Sprint Planning is timeboxed for 4 hours, it will always be maximum 4 hours, not even 1 minute longer, so to speak. Okay?
- 02:39 – So, that was the Sprint Planning, 8 hours in a 1-month Sprint.
- 02:43 – The Daily Scrum is always 15 minutes.
- 02:47 – It’s not that important to make it proportional, and then the Sprint Review is 4 hours in a 1-month Sprint and shorter proportionally; for example, 2 hours in a 2-week Sprint, and the Sprint Retrospective is 3 hours.
- 03:04 – It’s not so complicated, but you will still have some questions about it in your exam.
- 03:10 – As you remember, all of these are timeboxed, okay?
- 03:14 – That’s important. That’s why I’m repeating that, but there are two types of timeboxes here.
- 03:19 – One is the Sprint itself. It’s a fixed-duration timebox.
- 03:24 – So, for example, if we say that our Sprints are going to be 2 weeks long, then they will be always 2 weeks, not longer and not shorter, but for the other events that we have, the type of timebox, there is a maximum duration. It can be done faster.
- 03:49 – If you’re done with planning your Sprint, for example, instead of 8 hours, you’re done in 6 hours, that’s fine.
- 03:55 – You can finish your event. Okay? That’s one difference here.
- 04:00 – So, that was it about all events, and in the next lesson, I will start telling you about the Sprint itself.
- 04:09 – That’s also some type of event, almost, and then we will go through Sprint Planning, Daily Scrum, and so on.
- 04:16 – So, about the Sprint itself.
Next, we will talk about Sprints.
Here you can submit your questions related to the content of the course. (For other questions, use the support system). The trainer's reply will be email to you in 48 hours.
This lesson is part of the first 30% of the course, which is available for free, even without registration.
You can purchase the course to access all lessons, additional material, and coaching:
More info and purchase options