En la gestión de producto la visión de producto es muy importante para proveer motivación y propósito al equipo de Scrum y el alineamiento con el negocio. Con una visión apropiada la autogestión llega a tener sentido para orientar adecuadamente el foco del esfuerzo compartido para entregar valor.

Self-managing doesn’t mean that the Scrum Team — or the Scrum Master — is all-powerful.  (Sorry, not sorry!)  It means that the organization gives the Scrum Team the mandate to deliver value according to the product vision and goal within a set of guardrails.  

How shall we successfully pursue an agile transformation? Shall we outsource the effort to one of the big consultancies? Or shall we embark on an agile transformation with ChatGPT providing guidance?

Der Scrum Guide leistet bereits eine gute Arbeit, das Scrum-Rahmenwerk in seiner Ganzheit zu erklären. Für Scrum-Neulinge ist diese Darstellung zu theoretisch, sie suchen als ersten Einstieg einen Schnelldurchlauf durch einen Sprint. Wenn du weiter liest, dann bekommst du diesen Schnelldurchlauf.

A Scrum Master is effective when their team is effective. As the Scrum Guide says, Scrum Masters are accountable for the effectiveness of the Scrum Team.  Let’s explore what this entails.

Organizations sometimes misconstrue the role of a project manager with the accountability of the Scrum Master. While a project manager and a Scrum Master are similar in that they both work and interact with teams, there are distinct differences between their roles. 

Let’s harden a popular Scrum Master interview guide in the age of ChatGPT!

Help your Scrum team to avoid getting stuck in analysis paralysis by applying Itamar Gilad’s Confidence Meter.

In this ServerSide/TechTarget article, Dave West, CEO of Scrum.org shares his thoughts on who should be the Product Owner in Scrum.

Card, Conversation and Confirmation. Understand what professional confirmation looks like.

Nützliche ChatGPT-Prompts für Scrum Master, Product Owner und Entwickler

The idea of self-managing teams who have flexible scope and timelines can be perceived as daunting to some executives and senior leaders. In this session, Professional Scrum Trainer, Mary Iqbal talks about some of the common misconceptions about Scrum and Agile in general from a leader’s perspective and how to overcome them.

En esta sesión Alex Ballarín, Professional Scrum Trainer, te solucionará como:¿Es el Sprint Review el lugar donde se acepta el trabajo?, ¿Acepta el Product Owner el trabajo de los desarrolladores?, ¿Cómo funciona el criterio de aceptación? y mas!

The PO must consider the impact of each stakeholder request on the overall goal and vision for the product, as well as the available resources and time constraints. Sometimes the best response to stakeholder requests is "no".

Advanced ChatGPT Prompts for Scrum Masters, Product Owners, and Developers

Add a constraint to the length of the Product Backlog and see what happens next.

Empiricism is one of the underlying concepts of the Scrum framework. Scrum is founded on empirical process control, and transparency is the first of the three pillars. How does this show during Sprint Retrospective?

In this vlog, PST Joshua Partogi shares what needs to be considered when appointing someone to be the Product Owner and the negative consequences that arise when the Product Owner is not the right person ...

Kann ein großes Sprachmodell, das nicht auf „Agile“ spezialisiert ist, bereit heute ein Sondierungsgespräch für eine Scrum-Master-Stelle bestehen? Werden Scrum Master zumindest anteilig künftig durch einen Chatbot ersetzt?

Several years ago, I was the Scrum Master for a team working on a technology product.  Two of the team’s Developers told me they would like to try pair programming.  

A scenario showing how the scrum framework and metrics can help a team self manage for improvement.

Will Scrum Masters and Agile Coaches soon be replaced with a chatbot? In this ChatGPT job interview, I put OpenAI’s latest generative AI to the test.

Moderation ist im Scrum Rahmenwerk fest verankert. Sprint Planning, Daily Scrum, Sprint Review und Sprint Retrospektive sind dadurch bestimmt, dass innerhalb einer vorgeschriebenen Zeitspanne ein Ergebnis erreicht werden soll. Der Scrum Master facilitiert die Zusammenarbeit so, dass das Scrum Team dieses Ergebnis auch erreicht. Was ist, wenn er nicht zur Verfügung steht? Scrum Master, die ihr Moderationswissen nicht mit ihrem Team teilen, können so schnell zum Hindernis für die Teamarbeit werden. Wenn du nicht zu diesen Scrum Mastern gehören willst, dann lies weiter. Ich verrate dir mein bewährtes Entwicklungsmodell. Es liefert dir eine schrittweise Anleitung, wie du die Facilitation-Fertigkeiten im gesamten Scrum Team entwickeln kannst.

Agile approaches like Scrum have long promoted the importance of working at a sustainable pace. This principle was made part of the Agile Manifesto due to a common practice in the software industry where people were(/are) expected to work extra hours in order to meet a deadline. Commonly this was(/is) used to mask inevitable inaccuracies in planning, poor management and quality issues.

What happens when a Scrum Team becomes overwhelmed with requests that stakeholders make directly to the Developers instead of the Product Owner?  

In this episode of the Scrum.org Community Podcast, Professional Scrum Trainer Sander Dur from Xebia joins host Dave West for a discussion about leadership where they delve into topics including the importance of building trust, transparency and psychological safety in Scrum Teams and organizations. (27:35 Minutes)

Il est fréquent de demander au Scrum Master de tenir le rôle de facilitateur dans les 5 événements de Scrum. Dépassons ce cap pour aller vers des stratégies plus apprenantes, à la fois pour le Scrum Master et pour la Scrum Team.

Almost all Scrum Teams use a type of board to visualize their work giving them a better understanding of where they are currently and helping them make upcoming decisions. In this post, we investigate the techniques of effective collaboration on Sprint Board one by one.

Grow confidence, celebrate small successes, and build the muscle to get through the hard stuff.

Scrum Master mit Personalverantwortung im Team – ein Antipattern? Ich habe noch nie einen Scrum Master getroffen, der diese Idee nicht als Scrum-Antipattern bezeichnen würde. Als Argumente werden dafür meist drei Gründe angeführt:

Is your Product Ownership consistently optimizing sustainable, measurable value from your products and services? Or do you feel that Product Ownership is stuck in your company? If you fall in the second category, this video blog is for you! You will learn 6 ways to get Product Ownership unstuck by combining ideas from the world of Scrum, Agile Product Management and Co-Active Coaching.

Empiricism is one of the underlying concepts of the Scrum framework. Scrum is founded on empirical process control, and transparency is the first of the three pillars. How does this show during Sprint Planning?

Scrum is a lightweight framework for solving complex problems. The mechanics are relatively easy to understand, and your Scrum Master will help you with this. However, it is much more important for a Product Owner to exploit the benefits of Scrum from a business perspective.

„Als [Rolle] möchte ich [Funktion], um [Nutzen].“ User Stories, die so geschrieben sind, bergen drei große Probleme: 1. Sie ignorieren den Kontext oder die konkrete Situation. 2. Sie verwenden Personas. 3. Sie koppeln die Funktion mit dem Ergebnis für den Nutzer. Hier die Probleme im Detail:

In the heat of "the battle" teams tend to forget why they use the Scrum framework after all and what the foundations are of it. Why do we have Sprint Planning sessions every other week, why does our Product Owner has these or those accountabilities, why did we started using a team board after all, why did... 

In Scrum planen wir viel: Es gibt einen täglichen Plan, wenn die Entwickler während des Daily Scrum darüber nachdenken, wie sie heute dem Sprint-Ziel näher kommen können. Natürlich spiegelt das Sprint-Ziel selbst ein größeres Etappenziel wider, das das Scrum-Team für wertvoll hält, um die Probleme seiner Kunden zu lösen. Außerdem gibt es das noch Produkt-Ziel, ein mittel- oder langfristiges Ziel des Scrum-Teams. Schauen wir uns drei kritische Probleme an, die Scrum-Teams mit Produkt-Zielen haben, und ein praktisches Tool, das Ihnen hilft, das Durcheinander zu vermeiden.

Sprint Planning is one of those events that even experienced teams don’t use to its fullest potential.  Here’s why. Many teams see the Sprint Planning event as the time for selecting which Product Backlog items (PBIs) they will deliver in the upcoming Sprint.  And that’s it.  There is so much more that teams can do to maximize the value they get from Sprint Planning.

Are you a product owner? Do you need some coping strategies? Here are two tried and tested strategies. First, become a developer and use the notion of a product owner helper from large scale scrum. Secondly, have a speak now or forever hold your silence meeting.

We plan a lot in Scrum: There is a daily plan when the Developers think about progressing toward the Sprint Goal during the Daily Scrum. Of course, the Sprint Goal reflects an intermediate target the Scrum team considers valuable to solve their customers’ problems. Moreover, there is the Product Goal, a mid- or long-term objective of the Scrum team. Let’s check three critical issues Scrum teams have with Product Goals and a practical tool that helps you avoid the mess.

In this article, I will try to give you some ideas on how a Scrum Master can serve the organization and also some practical examples.

Does the following situation ring a bell? You enter a room and immediately get involved in a situation, listen how a problem is described, see a task or read a request. A single look, a single sentence, a small wink makes you think you perfectly know what is going on. This blogpost invites you to step back and listen before you act. It provides questioning techniques to help you as Scrum Master, Product Owner, Developer or Agile Leader to stay a little bit longer in the state of "actively do nothing" and listen before you act.

Let’s unpack what defines trust and how, although it does not sit among them, the Scrum values help build trust among team members.

In this episode of the Scrum.org Community Podcast, Kurt Bittner guest hosts and has Professional Scrum Trainers Peter Goetz and Thomas Schissler on to talk about the relationship between software architecture and Agile Teams. They discuss common misconceptions Agile teams have about software architecture, the role of the Product Owner in software architecture and more! (35:23 Minutes)

Nexus es el marco ideal para escalar Scrum debido a que no modifica Scrum. Es ideal para quienes ya usan Scrum debido a que su adopción se basa en Scrum. Nexus mejora la visiblidad y transparencia de las dependencias entre los equipos, dependencias externas y de otro tipo que elevan el riesgo de no entregar incremento de producto integrado entre todos los equipos que escalan a través de Nexus. Un evento clave es el Nexus Daily Scrum donde participan al menos un integrante de cada equipo Scrum del escalamiento además del equipo de Integración, Product Owner y Scrum Master.

In this year's 2023 DevOps Digest's predictions for Agile, Dave West and Patricia Kong of Scrum.org shared their predictions for 2023.

Vor ein paar Tagen hat OpenAI ein neues Modell einer generative KI zur Verfügung gestellt, welche "Gespräche führen" kann: ChatGPT. Ich dachte, es könnte interessant sein, ChatGPT ein paar Fragen über Business Agilität im Allgemeinen und Scrum im Besonderen zu stellen.

During refinement, the team discusses what we will deliver with each Product Backlog item. Although it's easy to drift into sorting out how we will deliver each PBI during these discussions, planning at this stage is a mistake. 

What if a Generative AI can not just answer questions but also learn while constantly improving its model? Wouldn’t that lead to the long-run obsolescence of many knowledge workers, for example, Scrum Masters, agile coaches, product managers, and Product Owners?

En una brillante conversación que hemos tenido hoy con un grupo hemos llevado adelante esta conversación sobre si un product owner es distinto de un product manager. ¿Quieres ver cómo es la diferencia?

In this episode of Ask a Professional Scrum Trainer, PST Jay Rahman will be available answers questions on leadership, Product Ownership, Scrum Mastery and more! (58:14 Minutes)