En este artículo exploramos el papel fundamental del Objetivo del Sprint como faro que guía al equipo hacia el logro de resultados valiosos para el cliente y la organización. A través de ejemplos prácticos en los sectores de mantenimiento, tecnología, construcción y alquileres de apartamentos, descu...

A personal experience of identifying the ideal Product Owner

How does Sprint Planning support adaptation in order to minimise deviations from agreed goals? Each of the Scrum Events serves to adapt. So does Sprint Planning. Check out our tips!

In this live session of Ask A Professional Scrum Trainer, Lavaneesh Gautam answers questions about the Daily Scrum, performance measurement, facilitating the Sprint Retrospective, Scrum with Kanban and more!

Nexus is a scaling framework that can be used to scale Scrum when there are three or more Scrum teams working together on the same Product. Teams using Nexus create a Sprint goal not only for each Scrum team, but also for all teams working together in the Nexus. This shared Sprint goal is called t...

The question we ask ourselves in this article is, "To what extent is Kniberg's graph still relevant to improving the performance of large-scale agile team collaboration?".

My excursion into creating useful Scrum Master interview questions with ChatGPT.

How can Developers detect undesirable variances in progress towards agreed goals? Each of the Scrum accountabilities participates in one or more inspections. So do the Developers. Check out our tips!

How poor facilitation of the Scrum events can cause Zombie Scrum, and how to create more engaging, impactful, and meaningful Scrum events with Liberating Structures.

Effective Stakeholder Engagement is key to the product's success and one of the essential skills all product people should have. This article is part 4 of the Effective Stakeholder Engagement series. - Stakeholder Exploration - Stakeholder Analysis & Mapping - Stakeholder Communication Strategy ...

Each of the Scrum Artifacts is inspected in one or more Scrum Events to detect undesired variances. So is the Sprint Backlog. Go check it out!

Unlike the other Scrum Events, the Sprint isn’t a meeting. Instead, it’s the container for all of the work that’s done by a Scrum Team to achieve a Sprint Goal. The Daily Scrum, Sprint Planning, Sprint Review and Sprint Retrospective all fall within the Sprint.

To keep work moving smoothly, the Developers get together for 15 minutes every day to focus on the Sprint Goal and to plan the upcoming day’s work. During the Daily Scrum, they identify any issues they need help in resolving, ask for help when they need it and adjust the Sprint Backlog, if necessary.

Every Sprint starts with Sprint Planning where the Scrum Team determines what they plan to accomplish during the course of the Sprint. They make this transparent by creating a Sprint Backlog including the Sprint Goal, the selected Product Backlog Items and the Developers’ plan for delivering the work

In this recorded session of Ask a Professional Scrum Trainer, Reshma (Simran) Nagrani answers questions about the Scrum Master Accountability, estimations, metrics, facilitation techniques and more! (58:45 Minutes)

Solving your customers’ problems in a complex environment requires communication skills, empathy, patience, diplomacy, and professionalism. So let’s have a look at some typical agile negotiation scenarios.

The Scrum Guide gives us a maximum one-month timebox for the Sprint. That means while it can’t be longer than a month, it can — and likely needs to be — shorter. So, how do we choose the right Sprint length for our product? In this article, I share three questions to determine the right Sprint lengt...

​​​​​​​Agile coaches have long recognized that busyness does not necessarily equal success. Checking off a to-do list does not mean you are adding value.  You might accomplish many organizational tasks, but the activity likely has little benefit if these tasks don’t contribute to the company’s goals...

Each Scrum Event serves Inspection, the second pillar of Empiricism. So does the Daily Scrum. How? Find out ...

Lernen Sie, wie Sie mit ChatGPT Workshops für agile Praktiker wie Scrum Master oder Product Owner erstellen können.

Who makes and maintains the Sprint Backlog? Who Creates the Sprint Goal? Do you need a Sprint Goal every Sprint? Can you have more than one? Watch this video to find out

The Scrum values help create a culture of collaboration and continuous improvement, guiding the team toward better results and a more satisfying work experience. I’ve written and talked a lot about the Scrum values over my consulting and coaching career because I’ve seen how they can galvanize teams...

Learn how to use ChatGPT to create workshops for agile practitioners such as Scrum Masters

Each Scrum Event serves Inspection, the second pillar of Empiricism. So does Sprint Planning. How? Find out ...

Sprint Goals and Product Goals are really tough to grasp an apply. Most people just restate the PBIs as the goal. Here's a checklist to help you make useful Sprint Goals and Product Goals.

In the following interview with Marjolein Pilon, she describes how Scrum has empowered the Scrum Teams she has worked with to approach the challenging problem of Climate Change.

I ran three comparisons, using the identical prompt to trigger answers from the new GPT-4 and previous GPT-3.5 models. Read on and learn what happened. It was not a foregone conclusion.

In this session of Ask a Professional Scrum Trainer, Joanna Plaskonka and Magdalena Kucharska answered questions focused on the Scrum Master, estimation, user stories, metrics, Scrum events and more! (59:15 Minutes)

How Liberating Structures and servant leadership create an environment for Scrum Masters to find support, offer help, and draw inspiration

La facilitazione permette di guidare persone e team verso obiettivi concordati. Traduzione dell’articolo originale in inglese sul sito scrum.org.

The Definition of 'Done' is probably the most misunderstood concept of the Scrum framework. In this article we will discuss:  What Is the Definition of 'Done'  How it can be used in Scrum Events

Lassen Sie uns darüber nachdenken, warum die Beantwortung dieser veralteten Daily Scrum Fragen einen negativen Einfluss auf das Scrum-Team hat — Making Your Scrum Work (29).

Sprint Planning initiates the Sprint by laying out the work to be performed for the Sprint. This resulting plan is created by the collaborative work of the entire Scrum Team.

The Definition of Done creates transparency by providing everyone a shared understanding of what work was completed and what standards were met as part of the Increment. If a Product Backlog Item does not meet the Definition of Done, it cannot be released yet. Think of the Definition of Done as the ...

The Sprint Goal is the single objective for the Sprint. Although the Sprint Goal is a commitment by the Developers, it provides flexibility in terms of the exact work needed to achieve it. The Sprint Goal also creates cohesiveness and focus, encouraging the Scrum Team to work together rather than on...

The Sprint Backlog is a plan by and for the Developers. It is a highly visible, real-time picture of the work that the Developers plan to accomplish during the Sprint in order to achieve the Sprint Goal.

The Product Goal describes a future state of the product which can serve as a target for the Scrum Team to plan against. The Product Goal is the long-term objective for the Scrum Team.

The Daily Scrum is a 15-minute event for the Developers of the Scrum Team. To reduce complexity, it is held at the same time and place every working day of the Sprint. If the Product Owner or Scrum Master are actively working on items in the Sprint Backlog, they participate as Developers.

Sprints are fixed length periods of work that last one month or less to create consistency and ensure short iterations for feedback in order to inspect and adapt both how work is done and what is being worked on. If cycles are longer, then the spirit of frequent feedback cycles can be lost. Longer S...

It is important to remember that a Developer is not necessarily a software developer. They can focus on any type of product work whether software or not and any aspect of helping to design, build, test or ship the product. The specific skills needed by the Developers are often broad and will vary ba...

How do the Product Owner and the Scrum Team navigate unexpected customer requests? What happens when a high priority customer issue is discovered mid-Sprint? Should the Scrum Team ignore the emergency or interrupt the Sprint? Like so many things in Scrum, the answer is that it depends.

Take your Daily Scrum from a reporting session to true teamwork and consider why answering the obsolete 3 Daily Scrum questions negatively impacts that ambition.

El Product Goal es un objetivo a largo plazo que establece la dirección general para el equipo Scrum y se enfoca en el valor que se entregará al cliente. Por otro lado, el Sprint Goal es un objetivo específico que se establece para cada Sprint en particular. Tener ambos objetivos en un equipo Scrum ...

La paradoja de Jevons, también conocida como la "paradoja del progreso", se refiere a la observación de que a medida que aumenta la eficiencia en el uso de un recurso, su consumo total puede aumentar en lugar de disminuir. Esta paradoja fue nombrada en honor al economista británico William Stanley J...

Read on and learn what ChatGPT considers to be a Scrum Master’s typical workload, excluding the removal of impediments.

En este artículo, un Scrum Master trabaja en una startup de tecnología y se enfrenta al desafío de un equipo que se resiste a participar en la daily scrum. El equipo tiene varias razones para no querer participar, incluyendo la percepción de que es una pérdida de tiempo, que interrumpe su trabajo di...

Facilitating the dynamics and interactions of Scrum Events is essential towards guiding the scrum team collectively to a shared objective. These five facilitation principles work hand in hand to ensure that your scrum events will become more focused, productive and effective.

What transparency can the Developers bring to the Scrum Team and the stakeholders of your product? Transparency, being one of the core underlying concepts of the Scrum framework, we can expect the Developers to actively work on this.

Many of us find it difficult to ask for help at work, which is a problem if you are part of a Scrum Team. Interdependence and collaboration are central to Scrum, but these practices don’t always come naturally to those new to the framework. In this post, we explore the incorrect assumptions tied up ...

About Sprint Planning Event Purpose: Initiates the Sprint by laying out the work to be performed for the Sprint. Output is a Sprint Backlog (Sprint Goal + selected PBIs + Plan) Facilitator Focus: Enable a collaborative and transparent environment with a clear objective. Keep the team f...