all the other things we've done in
our life.
You know that later someone balls is
out for Finally,
we did something right.
This is good.
Hey, friends,
welcome back to the channel.
If you new
here, my name is Vibhor. I am an Executive
Agile and Leadership Coach based in
Toronto, Canada.
and in this video we will talk about some
of the key questions that we all have
regarding the new Scrum Guide
2020. Clips in this video are taken from
the two hour long official Scrum guide
2020 video from Scrum Inc.
The link of which is in the description in
case you want to check it out.
Also as always,
everything I mention is going to
be linked as time stamps
in the video description on YouTube and
in the pinned comments.
So feel free to skip around the video.
If you feel like it.
Let's start with question number one.
Why are we changing Scrum Guide?
I've We've been talking about changing
the scrum guide,
so it's suitable for every domain and
every department in every company.
Indeed, Scrum revolutionized software development,
and although we kind of sort of been
using it In industries other than software
such as hardware,
healthcare,
construction, HR,
and Artificial Intelligence, Scrum
Guide 2020 has been adjusted to officially support
these domains.
This is our best guide so far.
When we did the very,
very first guide back in 2000,
right after the Agile manifesto,
it was 160 pages and it had seven phases.
This is an improvement.
Yeah, we're down to 13 pages.
I mean, I think this is just as good for
a sales team now,
as it is for a software development. Question.
Number two,
what does the main highlight of Scrum
Guide 2020. So we made scrum guides less
prescriptive as we proceeded.
We would get questions.
How do you do this?
How do you do that?
How does that happen?
And it would bother us,
so we would try to put something that
would guide or instruct or or give people
information about how to do it.
And I think I started it by by the three
questions you ask during the daily scrum.
And then we also had how you do
refinement.
So we put in things that we thought would
help you through,
so scrum itself is much,
much less prescriptive.
So although Scrum Guide is less prescriptive
now, It is still a lot prescriptive for
being an Agile framework,
and this makes us wonder,
"When does it make more sense to follow
Scrum Guide word by word and when it
doesn't. And in my opinion,
it depends a lot upon the level of
Agile maturity you are in.
So if yours is a new Agile team or
in other words,
you are at SHU stage,
then you should follow Scrum Guide line
by line. If you are in the HA stage or
have been doing Scrum for some time,
then you should start questioning the
practices prescribed in the Scrum Guide.
Once you reach the Ri level or a
mature stage,
then you should replace the prescribed practices
with the ones that most suit your situation.
You can check out this post in LinkedIn.
where I've described it in a little more
detail. Link of which is in the description.
Question number three.
What's new in Scrum Guide 2020. One of
the things we did with the guide was
simplify the sprint planning topics and
also bring in a focus on Why are we
doing what we're doing and the introduction
of the Product Goal.
Remember Ken, I mentioned to you about
a year or so ago that some of our trainers
were saying the product owners are not
focused on the overall goal?
They don't have a vision of where they're
going, So the team is supposed to know
long term,
where are they going as well as for each
sprint, what is the goal of that specific sprint?
So now we have this new term called Product
Goal, which can be equated to the overall
Product Vision,
the elevator pitch to the popular question,
"What the scrum team is working on?"
The Guide does not provide any prescription
on how to write a product goal and as
such scrum
teams are free to define a goal in a way.
that is right for their context.
Question number four. What about the artifacts?
Each of the three artifacts has certain
commitments,
So for the product backlog,
the product goal is the commitment for
the Sprint backlog.
The Sprint goal is the commitment. The
increment has a definition of done.
Uh, they all exist to bring transparency and
focus towards the progress of each artifact.
Question number five.
What about the role of the product owner?
When we said that there was one team
a problem that we had heard arguments after
arguments after arguments about is
the product owner is one team,
but then the developers are separate development
team and the scrum master kind of floats
out there.
And where you get with that is,
is you wind up with what I see in Sprint
reviews where the product owner is
pounding on the table,
saying, "You promised me you would do
this for the sprint,
why didn't you do it". If that person is
part of the team,
they are part of the committing to
what they thought they could do.
That's right.
And I think to some level we all can
relate to it that sometimes product owners
put themselves apart from the scrum team.
This is most apparent during the Sprint
planning meeting,
where the development team somehow appears
to be a separate team altogether,
with product owners acting as external stakeholders
demanding features. Well,
this is all taken care of by Scrum Guide 2020
where the emphasis is on WE instead of
THEY or THEM. Product owner is now officially
part of the single scrum team consisting of
the development team and the Scrum Master.
Question number six.
What is the intent behind removing the
term Servant Leadership?
The intent is the same as the past,
but as we were beginning to put this
Guide together,
Ken said to me,
I think the biggest problem in Scrum
it is the word servant leadership.
And I said Why?
He said, because many people have been
interpreted that as they don't need
to enable the team to improve and they're
not responsible for that improvement.
And we have many management teams saying,
you know,
we're paying the Scrum Masters a
lot of money,
but they're just secretaries.
Why should we pay them?
And so we said we got to do something about
that because the Scrum Master's livelihood
depends on them being,
you know,
really valuable contributors to the
to the community.
So initially,
Ken says,
let's just take servant leadership out
of the guide and so then we thought about
it. We said Okay,
you know,
really, the problem is that the scrum
master is not doing the leadership part
of servant leadership,
so so let's just reverse the words.
It's still the same thing,
but the leadership is front and center.
Not that you're going to tell people what
to do, but you're going to talk to
the people and explain the importance of
what we're doing.
Create inspiration for the people,
and then you're going to get out there
and take blows for your team.
That's what a great team captain does.
So scrum masters are still servant leaders,
but the misunderstanding that was created
by the term servant is now removed.
Scrum masters now officially have the
power to be assertive,
which we already were,
but now it is official. Question number
seven. Why did we remove the three standard
questions?
Well, in 2017,
we made the questions optional,
and the reason for that.
We saw teams using other techniques that
were quite effective,
and we also saw a lot of misuse of
the questions.
Some teams.
It was just a status report,
you know,
I worked on this yesterday.
I'll be working on this today.
I have no impediments and there's no
cross collaboration.
One of the best daily meetings I've seen
we published in a paper called Shock Therapy
Scott downy, he was a great coach.
He decided that it's only gonna be one
question of the daily meeting is. that
was, why isn't the first story done?
And how do we get the maximum number of
people on this team getting that one
story done now?
So Scrum Guide 2020 focuses more on the
WHY instead of HOW. But again, I will urge
you to be a little bit cautious.
Do not treat scrum guide as a silver bullet
to all your problems.
Remember,
scrum is only a framework to help you
to be more Agile with your approach.
If you're unable to find your answers in
Scrum,
don't forget to fall back on your friendly
neighbourhood AGILITY.
I hope you like this video and if you
did, then do not forget to give it
a thumbs up.
And also do not forget to provide your
valuable feedback in the comments.
I'll see you in the next video.
Should they be wearing scrum hats?
Scrum Hats!
Yeah, you could you buy little scrum hats
back when you when you started to remember
we had the all black shirts that said Scrum
They they don't sell them anymore.
Is that right?
Yeah. And strangely enough they are
too small for me now.
I don't understand how that could be.
I think I still have one in my closet somewhere.
Maybe I should have pulled it out with
this meeting,
huh? That would be a good one.