Resources

The Scrum Guide Reordered 2020 is based on about 95 percent of the text of the Scrum Guide 2020, extending its original structure by adding additional categories, for example, on self-management, commitments, or accountability.

In this podcast Scrum Facilitators from the Netherlands Sjoerd Kranendonk and Jasper Alblas discuss the new Scrum Guide (version 2020) with Scrum Coaches Steve Trapps and Andy Hiles from the UK.

The new Scrum Guide describes the whole Scrum Team as self-managing. But how do you lead these teams? Do they need leaders? And if so, where should we leaders focus on? Peter Koning - author of Agile Leadership Toolkit - gives three practical tips

In the 2020 Scrum Guide, the Definition of Done is created by the Scrum Team. In previous versions of the Scrum Guide, this responsibility was explicitly owned by the Development Team. I will explain the intention of the change and what it means for Scrum Teams.

With the launch of the new Scrum Guide, we also created a new illustration of the Scrum framework.

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.

The Scrum Guide 2020 defines Accountabilities within one team, Scrum Team. This video with Professional Scrum Trainer Ralph Jocham explains the Accountabilities. (3:21 Minutes)

The Product Goal is now the commitment of the Product Backlog. This video with Professional Scrum Trainer Ralph Jocham explains the Product Goal. (2:26 Minutes)

The Sprint Planning has been enriched with a third topic - Why. This video with Professional Scrum Trainer Ralph Jocham explains the change to the Sprint Planning event in Scrum. (2:24 Minutes)

Scrum.org has announced updates to the Scrum Framework as it celebrates its 25th anniversary. Updates include simplified language, less prescriptive and emphasis on the Scrum team and its need to be self-managing. 

This is an audio version of the 2020 Scrum Guide created by the Agile Wire Podcast with Professional Scrum Trainers Jeff Bubolz and Jeff Maleski.

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.

Sprint Retrospective is the last Scrum event within a Sprint. During this event entire Scrum Team- Scrum Master, Product Owner & Development Team inspects the Sprint and decides how to improve the next Sprint.

DEVOPSdigest posed the following question to the development community: How should DevOps and development adapt to the new normal? In response, DevOps industry experts offered their best recommendations for how development teams can adapt to this new remote work environment. Part 3 covers visibility and alignment.

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.

En noviembre de 2020, los co-creadores de Scrum, Ken Schwaber y Jeff Sutherland, han publicado una actualización de la Guía de Scrum...

Un cambio muy esperado ha sido finalmente la eliminación de las tres preguntas sugeridas en el Daily Scrum.

Hoy ha salido la nueva Scrum Guide 2020.  Aún estoy digiriendo los cambios que he ido viendo mientras reviso la nueva guía scrum.  Estoy analizando y no descarto todas las grandes o pequeñas consideraciones.

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.

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. 

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. 

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.

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, 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.

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.

This blog post talks about the addition of Commitments to each Artifact in the updated Scrum Guide.

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

Ken Schwaber and Jeff Sutherland are joined by Dave West, JJ Sutherland, Don McGreal and Avi Schneier as they discuss the release of the updated Scrum Guide and celebrate 25 years of Scrum.

A reflection on four key changes in the 2020 Scrum Guide, why they were made, and why that is a big deal

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.

In the 2020 update of the Scrum Guide, the Sprint Planning section has had a very welcome update. Every part of Scrum has a purpose, a reason to why it's included in the framework, and this update made the purpose - raison d'etre - of the Sprint Planning clearer. Let's see how!

Scrum is defined completely in the Scrum Guide by Ken Schwaber and Jeff Sutherland, the originators of Scrum.  The Scrum Guide is maintained independently of any company or vendor and therefore lives on a brand neutral site.  The Scrum Guide is translated and available in over 30 languages.

Heute, am 18. November 2020, pünktlich zum 25. Geburtstag von Scrum, haben Ken Schwaber und Jeff Sutherland den Scrum Guide aktualisiert.  Um eines gleich vorwegzunehmen: Scrum bleibt Scrum. Ein einfaches Rahmenwerk, welches es Teams ermöglicht, mit der Arbeit an komplexen Problemen zu beginnen. Und der Scrum Guide 2020 ändert daran nichts.  Einige Dinge sind jedoch neu und denen widmen wir uns jetzt. 

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.

New updates include simplified language, less prescriptive and emphasis on the Scrum Team and its need to be self-managing

TL; DR: The Scrum Guide 2020-The Scrum Guide 2020 is available now: Change is coming to make Scrum more accessible and inclusive beyond software development.

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.

A side-by-side comparison of The Scrum Guide 2020 and The Scrum Guide 2017 that will help you see all changes.

We updated our Scrum Framework poster to reflect the Scrum Guide 2020.

One of the more challenging aspects of Product Management is to create a tangible relationship between the work we do today and the business strategy. Product Goals are an often overlooked mechanism that can help you in this area.

This blog provides 15 tips to improve your agility in a complex world constantly changing as technological advances are driving globalization, changing our environment and influencing society which in turn calls for new solutions to these challenges.

Doing Scrum is not enough! The precious result will not be achieved just by understanding and following the rules and principles of the Scrum Framework. Every day organisations are starting and failing with business agility, praise and blame Scrum.

In this episode of Ask a Professional Scrum Trainer originally recorded on November 11, 2020, PST Matt Dominici answered some of the toughest Scrum questions from our live audience.

Do you know anyone in a management role who is part of an "Agile Transformation" (I prefer "Agile Enablement"). How are they doing? Are they experiencing any stress or anxiety?

A Sprint Planning checklist? How dare you: Agile is a mindset, not a methodology. It is a journey, not a destination. There is no one-size-fits-all approach, and what else could you possibly cover with a checklist, the mother of all standardized processes?

Scrum se basa en un proceso empírico. El empirismo se basa en tomar decisiones basados en la información concreta obtenida de la observación que muestra el progreso del desarrollo de producto, los cambios en el mercado y los comentarios de los cliente.

In this webinar, we discuss the power of using a Lean Agile Procurement approach to shrink value stream cycles by months. Is it hard to bring together people in and outside your company to really focus on delivering? In this webinar, we will discuss the power of using a Lean Agile Procurement approach to shrink value stream cycles by months. The creator of this approach, Mirko Kleiner and Professional Scrum Trainer Simon Reindl explore how using this technique establishes an Agile way of working from the outset. We explore how it impacts on each of the Key Value Areas of the Evidence-Based Management (EBM) framework, and empowers a more collaborative approach between supplier and company.

Behavior-Driven Development (BDD) is a well-known practice for collaboration and teams use it to bridge the gap between product management and the software development team. It is also very popular among quality engineers to develop test automation frameworks.

Un gran Product Owner tiene que estar enfocado en producir experiencias e impactos sorprendentes en los clientes a la vez que soporta el cambio de la organización hacia la agilidad con un enfoque de producto brindando el soporte necesario para que el equipo de desarrollo pueda optimizar el trabajo que realiza...