Scrum Guide 2020 - Product Goal in, Estimates Out
8,676
2020-11-19に共有
= = = = = = = = = = = =
New for 2024: my best-ever training:
"How Your Agile Teams Can Achieve Predictability and Productivity WITHOUT Burnout"
→ www.developmentthatpays.com/webinars/p-and-p?ref=y…
= = = = = = = = = = = =
0:00 Start
1:29 The big ADDITION
3:25 The big REMOVAL
4:34 What do YOU think?
-------------------
147. Scrum Guide 2020 - Product Goal in, Estimates Out
#scrum #DevelopmentThatPays
The Scrum Guide is 25 years old and to mark this occasion, it's had something of a makeover, a fairly radical makeover. But did they make things better Or did they just break it Welcome to Development That Pays. My name is Gary Straughan and a wise man once said, "Perfection is achieved not when there's nothing more to add but when there's nothing more to take away." And I have a feeling that Jeff Sutherland and Ken Schwaber, the originators of Scrum, would agree with that sentiment. Certainly it is reflected in this version of the Scrum Guide, Scrum Guide 2020 is down now to 13 pages. I think that's three fewer than the previous version. But this is more than just a stiff edit. There's been a whole raft of changes, many of which I'm still getting my head around. To give you an idea, here are the notes I took during yesterday's Scrum Guide 2020 launch event. So loads of things I could talk about. What I've decided to do for this video is to cut things down to just two. One major addition and one, for me anyway, major removal. So something that's been taken away from the Scrum Guide that most people are not talking about but I think is a huge deal. But let's start with the headline addition and this, of course, is what everyone's talking about and I probably put it in the title of this video. So you already know that I'm gonna be talking about the Product Goal. What exactly is the Product Goal Well, let's have a look at the brand new shiny edition of Scrum Guide 2020 to find out. The Product Goal describes the future state of the product, which can serve as a target for the Scrum Team to plan against. The Product Goal is in the Product Backlog. The rest of the Product Backlog emerges to define what will fulfill the Product Goal. And there's some clarification about exactly is a product in the context of Scrum. A product is a vehicle to deliver value. It has a clear boundary, known stakeholders, well-defined users or customers. A product could be a service, a physical product, or something more abstract. The Product Goal is the long-term objects for the Scrum Team. They must fulfill, or abandon, one objective before taking on the next. The Product Goal then is intended to make sure that we keep our eyes on the prize. In previous versions of the Scrum Guide, the word used was vision. The Product Goal kind of replaces vision and at the same time, strengthens it by making it a commitment. And actually, by making it a commitment, they've pulled off a pretty clever trick I think of making the Product Goal look like it should have been in the Scrum Guide all along. And here's what I mean by that. The Scrum artifacts, as I'm sure you know are the Product Backlog, the Sprint Backlog and the Increment. The Increment has its own commitment. That's the Definition of Done. The Sprint Backlog has its own commitment. That is the Sprint Goal. And now the Product Backlog joins the club with its very own commitment. You're right, the Product Goal. Let's move on now and talk about something that has been completely removed from the latest version of the Scrum Guide and I have to say, this one really caught me by surprise. You see, Scrum and I have been going through something of a rough patch, partly my fault. I've been dabbling with other frameworks, a little bit of Kanban here, a little bit of Scrumban there, but there is blame on both sides and over time, there was something in Scrum that I could just, well, I could really no longer live with it, and that thing was estimates. I really hate estimates. So I couldn't be more pleased that the words estimates, estimating anything like that, no longer appear in the Scrum Guide. Ken and Jeff, very, very impressed that you took that step. I for one did not see that coming. Product Goal in, estimates out. Those are the two things that caught my attention but now I'd like to hear from you. What's the one thing that caught your eye in the new version of the Scrum Guide Let me know in the comments below. Cheers for now.
• Scrum Guide 2020 - Product Goal in, E...
コメント (21)
-
What struck YOU the most about the brand new Scrum Guide ?
-
Such a great channel. Really nice insights on the changes, loved the estimates drama! Lol
-
Thanks for this video. I was staying away from Scrum, only, because of estimating. I am really glad that they have finally get it out from the guide.
-
thanks Gary....very interesting changes.
-
Excellent video, Gary! I hadn't even noticed that the estimates had been removed! Also, loved your description of your "rocky relationship" with Scrum. Golden :)
-
Thank you, Gary! As sharp on details as always!
-
Estimations out!!! That’s a shock! Got to go through the Scrum Guide today.
-
Good job,Gary!
-
I just read it, and I have to say that I like they considered some experiences I have lived. I loved they focused on data in order to forecast and they clarify that a scrum team doesn't need to wait until sprint review to release an increment
-
Thanks for the video, Gary. I really like your dark humour way to describe things. Based on the slide that you presented where sprint backlog has sprint goal and now product backlog has now product goal, can we assume that this product goal is changing also as output of sprint reviews? If yes, all the scrum team now has real time access to the product goal and give inputs to update it accordingly? In other words, how and who is going to manage the product goal? Do they are going to bring it in all sprint reviews and also get inputs from stakeholders? I would be curious to know how the product goal is created in the first place and for whom? If the product goal doesnt change along the way, it seems to me kind of the "waterfall" style to have the scope agreed and "written in stones" in the first place.😉
-
Nice analysis. For me, the thing that caught my eye was 2 parts, the removal of structure for the Daily Scrum, which I agree with, but I think that teams new to Scrum need a starting point. The 2nd thing that caught my eye was the redefinition of what a team is.
-
You have also highlighted something else here. The definition of Done (DoD) is the artifact for the 'Increment' not the Sprint and as we don't need to wait to the end of the sprint for the increment to be complete we have a clearer/different view on release management.
-
They should have launch earlier this year or late last year. launch at year end??
-
I like the Why very much and if we defocus estimates (btw the results of this was often a clarification of the what) the focus on the why is very strong because it leads toward the value and :) :) :) for this
-
Good video, thanks! Question regarding 2020 absence of “estimate” in the Guide: isn’t it basically replaced by “size”? If not, what is “size” referring to in the 2020 version (pages 10-11)? Cheers!
-
Liked that now there is only a Team, not Scrum Team and Devlopment Team. One thing that makes me a bit confused is the PO delegating the backlog management.
-
Hi Gary , it seems that the new scrum guide us borrowing a page of our book ?(is it going to the dark side to Scrumbhan side ?loll)..I love the fact that estimates are removed ,seems that scrum is becoming more lean and thus it should be ,after all it is lean that provided the genesis of scrum .Odly enough most of the things said in the new version made perfect sense to me .There is however one ☝️ thing that caught my eye and I wanted to get your input on it ,is the notion of self-managed teams replacing self organizing teams ,I’m still trying to scratch my head around that ..What is your opinion on it ,what exemple best illustrates that difference ..Richard Hickman’s famous definition of self managing team vs self governing teams convey that the former has a definition quite correlated to self organizing teams ,I really don’t see why there was a need to replace the term..
-
Also what does True leader mean...I believe this gives the Project Managers an opportunity to get back into the old ways in the guise of a True Leader
-
So what are we supposed to now do in Daily scrum...How to we discuss updates...The 3 questions were never forced upon everybody but always made sense to use as people could give updates quickly and then conclude the call in 15 minutes...
-
I have no idea how you should run scrum without estimates, looks like I'll be reading the updated version of scrum over the weekend then.
