Wow, 6 pages shorter than the 2017 version. Will be interesting to see what is removed, or maybe it’s just a smaller font size đ
Hm… I have interpreted the guide will be 13 pages longer than 2017 version, isn’t it?
I interpret “13 pages long” as just that, not “13 pages longer”. “lean and focused” also indicates a slimmed guide, but we’ll just have to wait and see.
Thank you, Fredrik. I’m on the way with my english đ
Looking forward!
Wow, that much shorter than before! Most curious how you achieved that! Probably not less elements in Scrum but just shorter descriptions?
Ken,
When would we able to review a draft to comment on?
Thx
Srikanth
Love to review the draft
Not a draft. Final product.
Curious and looking forward to the new version of Scrum Guide.
When is it going to be published. And Are we looking at suggestions on how Scrum need change when working Remotely.
Scrum works fine remotely now. I have been using Scrum for many years in a distributed environment. Nothing in Scrum says anything about co-location.
hi
Looking forward to discover the outcome of 3 almost 3 years of inspect and adapt
Wow! excited, curious .. looking forward
Will the changes cause any changes in the PSM training classes and/or certifications?
Thank you, Ken and team! Looking forward to it! Congratulations for the initiative!
Wow, have been waiting eagerly for an update.
What?!?! Can’t wait for it to be available. Highlighter and pen ready to go…
Will you reach out to the translator communities to release in multiple languages or first EN and then adding localisations incrementally?
Translators will be contacted over the coming weeks ahead of time.
I would love to be involved as a Brazilian Portuguese translator. The current translation could do with some work.
Many translations first, release, then we will go after the more obscure translations (Intuit…)
Will there be a webinar to explain the changes as happened with the 2017 update?
Yes, and documents..
Looking forward to the latest revison of Scrum Guide. Considering, Scrum Framework is globally adopted agile framework, hope there isn’t drastic changes to core of Scrum Framework. Excited about Scrum Guide becoming Lean and Focused. Thank you Ken and Jeff for the Scrum Framework. Can’t wait more.. Scrum ON!
As Scrum is breaking into new industries and not just IT, the vocabulary of the Scrum Guide also needs to adapt to its audience. I’m assuming the Scrum Guide is adapting so it is easier to apply towards products not relating to IT. I’m really excited to see it, absorb it, and get my Scrum on! I also may be completely wrong and it is much different than what I am anticipating đ
I’ve heard Jeff say that he was keen to change some of the terminology to emphasize the application of Scrum outside of the domain of software. I’ll be curious to see if this is one of the changes Ken and Jeff have made for the 2020 Scrum Guide update.
More focused, clear, and easy to understand – while still being hard to use.
You said it. I’m still learning and practising.
Looking forward to the new Scrum Guide. Do you have an exact date as of yet?
Before the end of the year. Scrum.org, ScrumInc, and Scrum Alliance srill have to update their materials.
Do you have a release date in mind? I’m keen to review the changes for my blog!
Early December
Christmas gift đ
For the Daily Scrum section: Remove the suggested 3 questions. This is a major reason why so many teams turn the Daily Scrum into a status meeting. Instead change to “Today I will (fill in the blank) to help the team accomplish the sprint goal. I need help with (fill in the blank)”. We need more focus on the sprint goal, not reporting status of what the individual team members did yesterday, today, I have no blockers”
Let me see… I believe in 2017 we fixed exactly that.
The Scrum Guide 2017
“The Development Team uses the Daily Scrum to inspect progress toward the Sprint Goal and to inspect how progress is trending toward completing the work in the Sprint Backlog. The DailyScrum optimizes the probability that the Development Team will meet the Sprint Goal.”
“What did I do yesterday that helped the Development Team meet the Sprint Goal? What will I do today to help the Development Team meet the Sprint Goal? Do I see any impediment that prevents me or the Development Team from meeting the Sprint Goal? ”
Sprint Goal everywhere
I don’t see that many Development Teams reading the SG anyhow. Scrum Master should help the team to understand Scrum. Pointing the team to the SG might be not a very good tactic.
All due respect, the 3 questions pointing to the sprint goal donât help. Itâs still a status driven format and throwing in âsprint goalâ doesnât magically make it impervious to becoming a status meeting.
Scrum Guide 2020 fixes that.
Is the Scrum Master title remaining? The word âMasterâ is deemed non-inclusive by many.
I believe the term “master” refers to more something like (from marriam webster dictionary)
“a worker or artisan qualified to teach apprentices”
and not the alternative meaning
“one having authority over another”
I have no doubt that youâre right about that. There are many people that donât know and may assume otherwise, though. IMHO itâs not obvious to those uninformed. If we know that something can be misinterpreted as something that is offensive, shouldnât we strive to provide clarity? It reminds me of when Grooming was changed to Refinement, not because it was the wrong name but because the word Grooming has an alternative, unsavoury definition.
What if someone feels bad about the word scrum or bed – shall we also stop using these words? I’m not trying to be mean here but the word Master in Scrum Master is as far from any negative conotation as it can be. Also these “many people that donât know and may assume otherwise” and “those uninformed” should perpaps read about what Scrum Master is before passing judgement.
@Ken Schwaber, Whether the Professional Scrum Certification exam’s questions are going to change based on the Scrum Guide?
Same. The answers are clearer.
“The answers are clearer” means, the answers to the PSM questions are clearer than before?
Please tell us the exact dates for release of this guide, eagerly waiting for the same.
Um… You’re asking for an “exact date of release” of the SCRUM Guide…. you see the irony in that right?
The framework and how it works, understanding the interplay of the parts, it clearer. The assessment ties directly to the Guide and is equally clear in the 2020 Guide.
Looking forward to train the new Daily Scrum section. Thanks
Interesting it would be! In 19 pages also, I have seen people becoming advocate to their own assumption(ex: Artifacts definition, team size etc.) so on) even though it is “guide” and not “law”. I am really curious to know as what points were considered when this was revised.
Only a few weeks left. Food for thought about the changes.
The Scrum Guide explains the Scrum framework. Am element of framework is that it doesn’t prescribe the “how”.
Some elements I think could be removed or altered are (without examining the current Scrum Guide):
– all examples how something can be done (like three questions)
– removing the part about “what to do with a PBI if Sprint is cancelled”
– more emphasis on the entrepreneurial mindset of the PO
– more emphasis on what Facilitate of SM means
– either remove the DoD or upgrade it to an artifact
– more emphasis on having a Sprint Goal for Sprint and business goal for Product Backlog
– remove recommended dev team size
– remove all recommended. Either make it mandatory or remove it đ
– describe the link of each event more clearly to the Scrum Values and TIA
Something like this makes sense?
Back to closer where we were in 2009.
2009. When there was no Scrum Guide and anyone could call any approach âScrum.â As i remember, when I left
Scrum Alliance and founded Scrum.org then i could develop and distribute the first definitive Scrum Guide. Life is good.
Scrum Guide too Agile and based on empiricism and inspect & adapt. I hope it will be backward compatible. What about the certifications? Do we have to do it again? Is there any changes to PSM certifications too apart from the Scrum Guide changes?
No you wonât have to redo certifications. The exams will absolutely change to be compatible with the updated Scrum Guide but it wonât be immediate.
We will find out soon. But, YES
Hi @Ken,
The new Nexus Guide 2021 talks about the integrated increment as singular âThe Scrum Teams in a Nexus produce a single Integrated Increment.â while it was mentioned in the new Scrum Guide 2020 and Kanban for Scrum Teams the need of clarification of multiple teams.
Scrum Guide 2020: âMultiple Increments may be created within a Sprint.â
Kanban guide for Scrum Teams 2021: âItâs a common misconception that teams can only deliver value once per Sprint.â
As a scale practitioner I would create and deliver many integrated increments if needed, but I think this is not clear in the new Nexus Guide and will cause more misconceptions.
Can you clarify if a Nexus can create and deliver many integrated increments per Sprint?
Thanks,
Ignacio
What I like before I’ve been reading on word of it is that it is shorter. Stronger focus and eliminated waste. That is real agile and lean spirit. Great and Thank you. I’am very curious.
Hi @kenschwaber, I really like the update to the guide. However, the new scrum definition says: “Scrum is a lightweight framework that helps people, teams and organizations generate value through adaptive solutions for complex problems.” That is the only reference to the word “solutions”, while the rest of the guide just refers to the “Product”. Should the definition just say “adaptive product” instead?
Thank you,
Ignacio
Hi Ken,
Are you going to release a new Nexus Guide? If so, when? The latest version is from 2018 and refers to terms that were changed in the new Scrum Guide 2020 such as “Development Team” and “Roles”.
Thanks
An update to the Nexus Guide will be coming in January.
Hi Ken,
Although I like 2020, I am having a trouble to understand these sentences.
“The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide. They do this by helping everyone understand…” Who are they? The Scrum Master is singular. Do you imply they are the Scrum Master and the rest of the Scrum team? This is simple grammar but has too much implication.
The Scrum Master
Hi @Ken,
The new Nexus Guide 2021 talks about the integrated increment as singular “The Scrum Teams in a Nexus produce a single Integrated Increment.” while it was mentioned in the new Scrum Guide 2020 and Kanban for Scrum Teams the need of clarification of multiple teams.
Scrum Guide 2020: “Multiple Increments may be created within a Sprint.”
Kanban guide for Scrum Teams 2021: “Itâs a common misconception that teams can only deliver value once per Sprint.”
As a scale practitioner I would create and deliver many integrated increments if needed, but I think this is not clear in the new Nexus Guide and will cause more misconceptions.
Can you clarify if a Nexus can create and deliver many integrated increments per Sprint?
Hi Ken,
I’m reading in the nexus guide 2021 that a scrum master that the Scrum Master in the Nexus Integration Team can be a scrum master for one or more teams.
my question, in nexus I understood that there is only one scrum master, one product owner and one integration team. but the above sentence tells that in nexus there can be more that one scrum master. is that correct?
Muhammad, there is only 1 Product Owner per product, but a Scrum Master can be on one or more Scrum Teams depending on many factors. This is true in Scrum and Nexus.
Ken Schwaber's Blog: Telling It Like It Is 
Wow, 6 pages shorter than the 2017 version. Will be interesting to see what is removed, or maybe it’s just a smaller font size đ
Hm… I have interpreted the guide will be 13 pages longer than 2017 version, isn’t it?
I interpret “13 pages long” as just that, not “13 pages longer”. “lean and focused” also indicates a slimmed guide, but we’ll just have to wait and see.
Thank you, Fredrik. I’m on the way with my english đ
Looking forward!
Wow, that much shorter than before! Most curious how you achieved that! Probably not less elements in Scrum but just shorter descriptions?
Ken,
When would we able to review a draft to comment on?
Thx
Srikanth
Love to review the draft
Not a draft. Final product.
Curious and looking forward to the new version of Scrum Guide.
When is it going to be published. And Are we looking at suggestions on how Scrum need change when working Remotely.
Scrum works fine remotely now. I have been using Scrum for many years in a distributed environment. Nothing in Scrum says anything about co-location.
hi
Looking forward to discover the outcome of 3 almost 3 years of inspect and adapt
Wow! excited, curious .. looking forward
Will the changes cause any changes in the PSM training classes and/or certifications?
Thank you, Ken! Looking forward to it!
Is Jeff Sutherland co-creator of the version?
Yes
Pingback: New Scrum Guide – so what? – Scrum for leaders
“Lean and focused” I love that.
Looking forward!
âLean and focusedâ I love that.
Looking forward!
Gd nws! Wh nds vwls nywy?
Wooow, this is a surprise!!!
Precision without prescription. Should be awesome! đ
Pingback: Scrum Guide 2020 – jesfer
Excited , Curious and looking forward..
Pingback: Nuevos cambios en la metodologĂa scrum - Agile Hispano
Looking forward to it!
Thank you, Ken and team! Looking forward to it! Congratulations for the initiative!
Wow, have been waiting eagerly for an update.
What?!?! Can’t wait for it to be available. Highlighter and pen ready to go…
Will you reach out to the translator communities to release in multiple languages or first EN and then adding localisations incrementally?
Translators will be contacted over the coming weeks ahead of time.
I would love to be involved as a Brazilian Portuguese translator. The current translation could do with some work.
Many translations first, release, then we will go after the more obscure translations (Intuit…)
Will there be a webinar to explain the changes as happened with the 2017 update?
Yes, and documents..
Looking forward to the latest revison of Scrum Guide. Considering, Scrum Framework is globally adopted agile framework, hope there isn’t drastic changes to core of Scrum Framework. Excited about Scrum Guide becoming Lean and Focused. Thank you Ken and Jeff for the Scrum Framework. Can’t wait more.. Scrum ON!
As Scrum is breaking into new industries and not just IT, the vocabulary of the Scrum Guide also needs to adapt to its audience. I’m assuming the Scrum Guide is adapting so it is easier to apply towards products not relating to IT. I’m really excited to see it, absorb it, and get my Scrum on! I also may be completely wrong and it is much different than what I am anticipating đ
I’ve heard Jeff say that he was keen to change some of the terminology to emphasize the application of Scrum outside of the domain of software. I’ll be curious to see if this is one of the changes Ken and Jeff have made for the 2020 Scrum Guide update.
More focused, clear, and easy to understand – while still being hard to use.
You said it. I’m still learning and practising.
Looking forward to the new Scrum Guide. Do you have an exact date as of yet?
Before the end of the year. Scrum.org, ScrumInc, and Scrum Alliance srill have to update their materials.
Pingback: S1E6 – Los cambios que se vienen para Scrum – Do Agile Be Agile Podcast
Do you have a release date in mind? I’m keen to review the changes for my blog!
Early December
Christmas gift đ
For the Daily Scrum section: Remove the suggested 3 questions. This is a major reason why so many teams turn the Daily Scrum into a status meeting. Instead change to “Today I will (fill in the blank) to help the team accomplish the sprint goal. I need help with (fill in the blank)”. We need more focus on the sprint goal, not reporting status of what the individual team members did yesterday, today, I have no blockers”
Let me see… I believe in 2017 we fixed exactly that.
The Scrum Guide 2017
“The Development Team uses the Daily Scrum to inspect progress toward the Sprint Goal and to inspect how progress is trending toward completing the work in the Sprint Backlog. The DailyScrum optimizes the probability that the Development Team will meet the Sprint Goal.”
“What did I do yesterday that helped the Development Team meet the Sprint Goal? What will I do today to help the Development Team meet the Sprint Goal? Do I see any impediment that prevents me or the Development Team from meeting the Sprint Goal? ”
Sprint Goal everywhere
I don’t see that many Development Teams reading the SG anyhow. Scrum Master should help the team to understand Scrum. Pointing the team to the SG might be not a very good tactic.
All due respect, the 3 questions pointing to the sprint goal donât help. Itâs still a status driven format and throwing in âsprint goalâ doesnât magically make it impervious to becoming a status meeting.
Scrum Guide 2020 fixes that.
Is the Scrum Master title remaining? The word âMasterâ is deemed non-inclusive by many.
I believe the term “master” refers to more something like (from marriam webster dictionary)
“a worker or artisan qualified to teach apprentices”
and not the alternative meaning
“one having authority over another”
I have no doubt that youâre right about that. There are many people that donât know and may assume otherwise, though. IMHO itâs not obvious to those uninformed. If we know that something can be misinterpreted as something that is offensive, shouldnât we strive to provide clarity? It reminds me of when Grooming was changed to Refinement, not because it was the wrong name but because the word Grooming has an alternative, unsavoury definition.
What if someone feels bad about the word scrum or bed – shall we also stop using these words? I’m not trying to be mean here but the word Master in Scrum Master is as far from any negative conotation as it can be. Also these “many people that donât know and may assume otherwise” and “those uninformed” should perpaps read about what Scrum Master is before passing judgement.
Yes …. they are master of the process.
My wishlist, audio is in Spanish but subtitles are in English. Hope you like it! https://www.youtube.com/watch?v=X-rvlL68jFE
I am looking forward to the guide
Aren’t we all!
Pingback: Neuer Scrum Guide angekĂźndigt – SCRUMschau
@Ken Schwaber, Whether the Professional Scrum Certification exam’s questions are going to change based on the Scrum Guide?
Same. The answers are clearer.
“The answers are clearer” means, the answers to the PSM questions are clearer than before?
Please tell us the exact dates for release of this guide, eagerly waiting for the same.
Um… You’re asking for an “exact date of release” of the SCRUM Guide…. you see the irony in that right?
The framework and how it works, understanding the interplay of the parts, it clearer. The assessment ties directly to the Guide and is equally clear in the 2020 Guide.
Looking forward to train the new Daily Scrum section. Thanks
Interesting it would be! In 19 pages also, I have seen people becoming advocate to their own assumption(ex: Artifacts definition, team size etc.) so on) even though it is “guide” and not “law”. I am really curious to know as what points were considered when this was revised.
Only a few weeks left. Food for thought about the changes.
The Scrum Guide explains the Scrum framework. Am element of framework is that it doesn’t prescribe the “how”.
Some elements I think could be removed or altered are (without examining the current Scrum Guide):
– all examples how something can be done (like three questions)
– removing the part about “what to do with a PBI if Sprint is cancelled”
– more emphasis on the entrepreneurial mindset of the PO
– more emphasis on what Facilitate of SM means
– either remove the DoD or upgrade it to an artifact
– more emphasis on having a Sprint Goal for Sprint and business goal for Product Backlog
– remove recommended dev team size
– remove all recommended. Either make it mandatory or remove it đ
– describe the link of each event more clearly to the Scrum Values and TIA
Something like this makes sense?
Back to closer where we were in 2009.
2009. When there was no Scrum Guide and anyone could call any approach âScrum.â As i remember, when I left
Scrum Alliance and founded Scrum.org then i could develop and distribute the first definitive Scrum Guide. Life is good.
Any plans for updating the Nexus Guide as well?
Pingback: GUIA SCRUM 2020 - Confira todas as novidades
Scrum Guide too Agile and based on empiricism and inspect & adapt. I hope it will be backward compatible. What about the certifications? Do we have to do it again? Is there any changes to PSM certifications too apart from the Scrum Guide changes?
No you wonât have to redo certifications. The exams will absolutely change to be compatible with the updated Scrum Guide but it wonât be immediate.
We will find out soon. But, YES
Hi @Ken,
The new Nexus Guide 2021 talks about the integrated increment as singular âThe Scrum Teams in a Nexus produce a single Integrated Increment.â while it was mentioned in the new Scrum Guide 2020 and Kanban for Scrum Teams the need of clarification of multiple teams.
Scrum Guide 2020: âMultiple Increments may be created within a Sprint.â
Kanban guide for Scrum Teams 2021: âItâs a common misconception that teams can only deliver value once per Sprint.â
As a scale practitioner I would create and deliver many integrated increments if needed, but I think this is not clear in the new Nexus Guide and will cause more misconceptions.
Can you clarify if a Nexus can create and deliver many integrated increments per Sprint?
Thanks,
Ignacio
What I like before I’ve been reading on word of it is that it is shorter. Stronger focus and eliminated waste. That is real agile and lean spirit. Great and Thank you. I’am very curious.
Hi @kenschwaber, I really like the update to the guide. However, the new scrum definition says: “Scrum is a lightweight framework that helps people, teams and organizations generate value through adaptive solutions for complex problems.” That is the only reference to the word “solutions”, while the rest of the guide just refers to the “Product”. Should the definition just say “adaptive product” instead?
Thank you,
Ignacio
Pingback: Podcast Ep. 106: What's New With Scrum? | AgileThought
So many possibilities.
Hi Ken,
Are you going to release a new Nexus Guide? If so, when? The latest version is from 2018 and refers to terms that were changed in the new Scrum Guide 2020 such as “Development Team” and “Roles”.
Thanks
An update to the Nexus Guide will be coming in January.
Hi Ken,
Although I like 2020, I am having a trouble to understand these sentences.
“The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide. They do this by helping everyone understand…” Who are they? The Scrum Master is singular. Do you imply they are the Scrum Master and the rest of the Scrum team? This is simple grammar but has too much implication.
The Scrum Master
Hi @Ken,
The new Nexus Guide 2021 talks about the integrated increment as singular “The Scrum Teams in a Nexus produce a single Integrated Increment.” while it was mentioned in the new Scrum Guide 2020 and Kanban for Scrum Teams the need of clarification of multiple teams.
Scrum Guide 2020: “Multiple Increments may be created within a Sprint.”
Kanban guide for Scrum Teams 2021: “Itâs a common misconception that teams can only deliver value once per Sprint.”
As a scale practitioner I would create and deliver many integrated increments if needed, but I think this is not clear in the new Nexus Guide and will cause more misconceptions.
Can you clarify if a Nexus can create and deliver many integrated increments per Sprint?
Thanks,
Ignacio
Pingback: GUIA SCRUM 2020 – Confira todas as novidades – Canal Valor | Universidade Digital
Hi Ken,
I’m reading in the nexus guide 2021 that a scrum master that the Scrum Master in the Nexus Integration Team can be a scrum master for one or more teams.
my question, in nexus I understood that there is only one scrum master, one product owner and one integration team. but the above sentence tells that in nexus there can be more that one scrum master. is that correct?
Muhammad, there is only 1 Product Owner per product, but a Scrum Master can be on one or more Scrum Teams depending on many factors. This is true in Scrum and Nexus.
Hit it right on the head, Eric