Community Blog

What's up awesome people? I hope you are enjoying your weekend. As some of you already know, in Scrum Guide 2020, one of the accountabilities in the Scrum Team is Developer.

TheScrumMaster.co.uk has created The Simple Guide To Scrum – 1 Pager. A condensed and visual representation of Scrum on 1 page.

In this blog post, Joshua Partogi talks about the meaning of true leadership of the Scrum Master.

November 2020 was the launch of the Scrum Guide update. It seems like only yesterday but was over 3 months ago...

There is a new a new Scrum Guide out - version 2020. What has changed for Scrum teams practicing Kanban?

Four PST's (Andy Hiles, Steve Trapps, Sjoerd Kranendonk and Jasper Alblas) discuss the changes in the 2020 version of the Scrum Guide. You can watch the video above.

The following are the changes that struck me the most in the 2020 Scrum Guide...

Scrum Framework poster (2020 update) by Scrum Facilitators #ScrumGuide2020 #Scrum

The new version of the Scrum Guide has just been released. It is exciting! Scrum walks the talk by inspecting and adapting itself. So should you as a Scrum Master.

In the 2020 Version of the Scrum Guide, the commitments were introduced for each artifact. These then became an element of Scrum; in that they need to be used to gain the maximum value that the Scrum Framework offers. They were always part of a Professional Scrum approach, now there is a clear connection of these commitments to the artifacts. They increase transparency, and the focussed delivery of Value. Each of the commitments now clearly support and sustain an artifact.

Scrum Guide 2020 Poster After yesterday's Scrum Guide 2020 launch event by Ken and Jeff, I am excited to announce the release of the new Scrum 2020 poster.

Scrum is described as a framework, not a methodology. The Scrum Guide provides just enough prescription to allow Scrum to work and encourages its ‘users’ to be smart, adding practices and other things specific to them on top of the framework as needed to form their process.

With the 2020 release of the Scrum Guide, the term role was replaced with accountabilities. The purpose of this change was to place special emphasis that this is not a job description, but the bare minimum set of accountabilities necessary to execute Scrum. The blog describes how these accountabilities are split into 3 groups.

One interesting change to the Scrum Guide for the 2020 release was the change of the term Self-Organizing to Self-Managing. This blog discusses the change.

With the 2020 release of the Scrum Guide, Commitments were added for each artifact. The commitments provide a nice, structural way to describe some of the key characteristics of each artifact. The intent of this change was to provide clarity and make the Scrum Guide simpler to read and use.

With the 2020 update to the Scrum Guide, three commitments were added to the artifacts. The idea of a commitment is to provide additional quality to the artifact to improve transparency. In the case of Product Backlog, the commitment is to the Product Goal. 

At Scrum.org we have used this update of the Scrum Guide as an opportunity to have some interesting discussions and our CEO Dave West has documented some of them for your review and attention. 

Today, the 18th of November 2020 Ken Schwaber and Jeff Sutherland released an update to the Scrum Guide. If you are interested in an overview of what has changed, read about the seven main changes described with some context.

The more Scrum Teams are empowered to make and own decisions about their work, the more benefits they will realize.

If you prefer watching a video to understand the updates in Scrum Guide 2020, which are also my favourite updates, enjoy watching this video I've made.

Professional Scrum Trainer, Sahin Guvenilir, discusses measuring value, improving outcomes, and using the best available evidence to decide the next steps against a Strategic Goal.

Pour le 25ème anniversaire de Scrum, ses co-créateurs, Jeff Sutherland et Ken Schwaber nous livrent le millésime 2020 du Guide Scrum.

Let's explore how the "soft" Scrum Values directly translate into "hard" business value. Cha-Ching!

Scrum requires a self-organized team to deliver "done" increments at the end of each Sprint.

Scrum cumplió 21 años en 2016. Ya tiene edad legal para comprar alcohol en la mayoría de estados americanos. Y durante este tiempo ha crecido mucho. Con muchos cambios.

A Sprint Goal is an objective set for the Sprint that can be met through the implementation of Product Backlog (cit. Scrum Guide). Have you clearly defined a Sprint Goal at the end of your Sprint Planning? Is this Sprint Goal understandable and transparent to everyone? Is it defined in a way that provides guidance and flexibility to the Development Team? The aim of this article is to raise awareness on the importance of having a Sprint Goal defined and to provide some suggestions on how to create one.

A few days ago, I was observing a Sprint Retrospective. The Scrum Team decided to work on the Definition of Done (DoD), identified as the most important topic to adapt for the next Sprint. The discussions were open and animated, when an unexpected discussion emerged during the session.

In 2016 the Scrum Values were added to the Scrum Guide. In this article I share a workshop I run several times, with excellent feedbacks, hoping that you'll see value in reusing it in your working environment.

Bottom line - WiP limits must be applied to improve flow of the delivery of value. It's a key lever to improve the performance of Professional Scrum Teams, and it's required by the Kanban Guide for Scrum.

Over the centuries, humans have managed to adapt to many situations and evolve to become what we are today. History shows that we have an innate ability to adapt and evolve. This remains valid as part of a change in business, such as the adoption of Scrum.

Today (November 7th 2017) Ken Schwaber and Jeff Sutherland released an update to the Scrum Guide.The Scrum Guide is the definitive definition of Scrum, authored by Ken and Jeff, the creators of Scrum.

This week, co-creators of Scrum, Ken Schwaber and Jeff Sutherland, released a new version of the Scrum Guide