- Let's summarize lesson 5.
We discussed Agile frameworks,
team composition, organizational structure,
and covered destination and planning.
We also reviewed Scrum Cadence
as the most frequent Agile methodology.
Now, as we do at the end of each lesson,
I'm offering you a five question quiz.
I will show and read the question.
Please pause the video after you see the question
and write down your answer and then restart the video
and then I will reveal the answer for you.
Here are questions 1 through 5.
Question 1, which is not a standard Scrum role?
Please write down the letter
that corresponds to your answer.
And now let me reveal the correct answer.
The answer is B, there is no tech lead.
It could be tech leads in an Agile organization,
but it is not a standard Scrum role.
Question 2, which type of organizational structure
has been adopted by Spotify?
Write the answer.
And the correct answer is flexible.
It's not traditional, hierarchical, or matrix.
It's completely flexible
with four different team structures.
Now, question 3,
what is the optimal size for a Scrum team?
Please write down your answer.
And the correct answer is B, 5 to 9 people.
We're saying it's an optimal team size.
However, it is not a restrictive framework
so it could be any team size
that works for the organization,
but more than 15 becomes really problematic
to be flexible and move fast.
Now, question 4.
What is the purpose of Kanban?
Please write your answer.
And the correct answer is A,
to remove bottlenecks every step of the way,
visualizing any bottlenecks in the flow.
The flow is the keyword.
Now let's go to question 5.
What happens if a team has a velocity of 16,
then plan the Sprint up to 15 points already,
and the next item on their backlog
is estimated at three story points?
Please pause your video,
review all the answers,
and write the letter that corresponds to the correct one.
The correct answer is B,
the team takes the next item in the backlog
that is estimated at one story point
because they can only go to 16 story points.
And for that, they may skip a few items
until they get to a one pointer and that's perfectly fine.
Sometimes product backlog owner or the product owner
will disagree with that
and then they do decomposition.
But the rule is that the team should skip anything
until they find the backlog item
that is estimated as one story point.
That's why it's so important to have small stories.
Remember invest mnemonic.
S stands for small.
The smaller the user story is,
the easier estimation becomes
and more accurate it becomes for the team.
With that, I hope you got all the five questions right
and did a great job on this
and I'll see you in lesson 6.