Community Blog

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.

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.

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.

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. 

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

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.

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.

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

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!

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.

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

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.

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.

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. 

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.

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.

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

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

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.

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.

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.

From Scrum Master to Development Team members, this set of questions addresses the foundations of a Scrum Team capability to build valuable products: technical excellence and what it takes to achieve this proficiency level.

What's good awesome people? I hope you are well and safe wherever you may be when watching today's vlog.

Ideas on how to use Powerful Questions virtually and help teams find their own solutions to persistent problems.

This article shares examples of the power of transparency and how it can be used to create breakthroughs in performance.

In Leslie Morse's first Scrum.org blog post she explores the intersection of professional coaching and agile coaching, and the opportunity we have as agilists to overcome the limitations of an industrialized mindset and create space for ushering in the future of work.

Un Equipo de Desarrollo en Scrum no tiene sub equipos, roles o títulos. En el equipo pueden y es bueno que existan especialistas como expertos en pruebas, desarrollo, arquitectura, etc. Pero estos especialistas aportan para que el equipo pueda lograr el objetivo del Sprint y del producto como equipo complementando sus competencias.

Desde la Revolución Industrial, la creciente competencia ha impulsado a las empresas hacia estrategias que preservan y aumentan su participación de mercado. 

On the 25th birthday of Scrum, I have a free gift for all Scrum practitioners... Do you know any Executive who is willing to spend 15 minutes to save 15% or more on the cost of their company's Scrum adoption...? ;)

TL; DR: The Cargo Cult Agile Checklist for Download You want to know the state of agility in your organization? Here we go: Download the checklist, distribute it generously among your colleagues, and run a quick poll.

Ser un Scrum Master puede ser una carrera divertida, emocionante y muy gratificante. Pero, ¿cómo consigues un primer trabajo de Scrum Master si aún no tienes experiencia?

What's up awesome people. Scrum will have its 25 year anniversary. Have Scrum impacted your personal or professional life?

Esta semana he recibido 2 llamadas profesionales que me han llegado al corazón. Una ha sido de una persona pidiendo mentoría y otra de una persona dando las gracias por haberla ayudado.

Une Sprint Rétrospective est une opportunité, pour l'équipe Scrum, d'inspecter le déroulement du Sprint et créer un plan d'amélioration à adopter lors du prochain Sprint.

Me gustaria compartir un plan para pasar el PSM I en 10 días. Recuerda que lo puedes comprar por libre en Scrum.org sin necesidad de tomar el curso. Puedes hacerlo aquí