Project Management

Please login or join to subscribe to this thread

The new Scrum

linkedin twitter facebook   Agile   Scrum  
avatar
David Portas London, United Kingdom
Any thoughts on the newest version of the Scrum Guide? Key points:

- No estimates
- No roles or development team
- Self-managing rather than self-organising
- New product goal
- No more “three questions”
- The guide is shorter and less prescriptive

https://www.scrumguides.org/scrum-guide.html
Sort By:
avatar
Miguel Rodriguez Manager| Telefonica Global Solutions Torrelodones, Madrid, Spain
Would be great if we could extract the exact differences from 2017 guide.
avatar
Kiron Bondale Retired | Mentor| Retired Welland, Ontario, Canada
David -

In some ways it is more prescriptive (e.g. commitments tied to each artifact) and in others less so (e.g. no more three questions).

I wouldn't say that it addresses any of the inherent gaps or weaknesses in the framework so it will still only fit specific team contexts.

Kiron
avatar
Thomas Walenta Global Project Economy Expert Hackenheim, Germany
Miguel,
see here
https://amazing-outcomes.de/en/resources/d...crum-guide-2017
avatar
Sergio Luis Conte Helping to create solutions for everyone| Worldwide based Organizations Buenos Aires, Argentina
With all my due respect, most of the affirmations you post above are not inside the Scrum Guide. Where you can find a explicit mention about "no estimate"? The same from others items on the list. When you read: "Through discussion with the Product Owner, the Developers select items from the Product Backlog to include in the current Sprint." what do people think is this?. But I know, people read things based on the perception and perception is created by knowledge and previous experience. Just my point of view I can sustain.
...
1 reply by David Portas
Nov 29, 2020 5:13 PM
David Portas
...
Hi Sergio. Perhaps my summary could have had a few more words of explanation, sorry. My point about estimates is that the *previous* version of the guide said that backlog items should be estimated - the new version does not. In line with the practices of many teams, formal estimates are no longer considered essential to Scrum. Teams can plan sprints without recording any estimates for backlog items. I didn't mean to imply that Scrum forbids estimates!

Similarly, the word "roles", the three question format for standups and the term "development team" have been deleted. I think those are welcome changes to the Guide for several reasons. Of course Scrum will still be used by development teams.
avatar
David Portas London, United Kingdom
Nov 29, 2020 2:55 PM
Replying to Sergio Luis Conte
...
With all my due respect, most of the affirmations you post above are not inside the Scrum Guide. Where you can find a explicit mention about "no estimate"? The same from others items on the list. When you read: "Through discussion with the Product Owner, the Developers select items from the Product Backlog to include in the current Sprint." what do people think is this?. But I know, people read things based on the perception and perception is created by knowledge and previous experience. Just my point of view I can sustain.
Hi Sergio. Perhaps my summary could have had a few more words of explanation, sorry. My point about estimates is that the *previous* version of the guide said that backlog items should be estimated - the new version does not. In line with the practices of many teams, formal estimates are no longer considered essential to Scrum. Teams can plan sprints without recording any estimates for backlog items. I didn't mean to imply that Scrum forbids estimates!

Similarly, the word "roles", the three question format for standups and the term "development team" have been deleted. I think those are welcome changes to the Guide for several reasons. Of course Scrum will still be used by development teams.

Please login or join to reply

Content ID:
ADVERTISEMENTS

No matter how much cats fight, there always seem to be plenty of kittens.

- Abraham Lincoln

ADVERTISEMENT

Sponsors







Vendor Events

See all Vendor Events

Newsletters

Jun 3: The Career Problem Facing New PMs
May 20: Your PM Career as a Project Life Cycle
May 13: The Big Lie After Layoffs

See all newsletters