Fourth blog, in a blog series about the upcoming book: Creating Agile Organizations - A Systemic Approach, by Cesario Ramos & Ilia Pavlichenko.

In this blog series, we’ll share the gaps that many Scrum Masters face as they work to become better agile leaders and Scrum professionals. We’ll call out biases and misperceptions and also offer suggestions on how to overcome these challenges in order to influence change.

Powerful Product Owner. It sounds like a threat, isn’t it?  Anyone overpowering affects the whole team’s activity and outcome. No wonder this affects retrospectives as well. 

El intraemprendimiento es la aplicación de la mentalidad y prácticas de los emprendedores, que crean nuevas empresas o despliegan iniciativas sociales, dentro de las empresas consolidadas.

TL; DR: How to Pass the Product Owner Certification — Scrum.org’s PSPO I to III The 

In this blog post, Sander Dur explains technical debt vs undone work...

Viele angehende Scrum Master erzählen mir im Professional Scrum Master Training, dass sie es schwierig finden, diese vier Dinge zu vereinen. Hier 3 Tipps, wie ich diese Situation in der Vergangenheit gemeistert habe.

La agilidad de negocio es la capacidad de deleitar continuamente a los clientes con entregas de valor e inspirar a los empleados en medio de los desafíos emergentes. 

Live & online training, when done well can be as effective, or even more effective than in-person training.

Why many Scrum teams struggle with continuous improvement, and how you can do better

Once the team has selected a point system, they need to decide which types of items to classify as a 1, 2, and so on. In this article, we will provide an exercise that can help your team create a point system organically no matter what’s in the Product Backlog.

Keine andere Rolle in Scrum kann so sehr zu mittelmäßigen Ergebnissen beitragen wie der Product Owner — Garbage in, Garbage out. Die folgende Liste mit den häufigsten Product Owner Fehlverhalten könnte daher ein Ausgangspunkt sein, über die Tätigkeit als Product Owner nachzudenken; vielleicht gibt es Verbesserungspotential?

Scrum is by far the most popular framework these days. In fact, the 15th Annual State of Agile shows that 66% of respondees use this particular framework.

Practical ideas on how to improve Scrum, personally.

In this video, Mark how healthy rework can maximize learning and, ultimately, effective value for your customers. We'll explore two principles of healthy rework and two principles of unhealthy rework you can use to lean into learning!

The third blog, in a blog series about the upcoming book: Creating Agile Organizations - A Systemic Approach

TL; DR: Scrum Master Anti-Patterns No other role in Scrum can contribute to mediocre outcomes like the Product Owner—garbage in, garbage out.

Three simple retrospective formats based on the Liberating Structures "Conversation Cafe", "Troika Consulting", and "Discovery & Action Dialogue"

Schon seit Jahren beobachte ich bei Scrum Teams dieses Phänomen: Die Einträge im Sprint Backlog bewegen sich tagelang gar nicht. Und dann wird in letzter Minute doch alles fertig. 

In this vlog, PST Joshua Partogi demystifies Product Backlog Refinement ... what it is, where, when, how long and how often it happens also how refined should each Product Backlog item be.

Vamos a proporcionar una descripción general rápida de cada animal, veremos por qué son tan peligrosos y ofreceremos algunos consejos sobre cómo domesticarlos para ver qué animal de producto eres o son los que te rod

An exploration of the color theory of change, and how it illustrates a bias in our community that may explain our failure to enact meaningful change

Das Sprint Planning ist ein zentrales Scrum-Ereignis, welches entscheidet, wie sich das Leben Ihrer Kunden mit dem nächsten Inkrement verbessern wird. Erfahren Sie mehr darüber, wie Sie Ihren Kunden durch die Vermeidung von 20 gängigen Sprint Planning Anti-Patterns helfen können.

In this post, I share a few questions you, as a manager - or any other stakeholder, can ask Product Owners and the rest of the Scrum Team to support them in doing the right thing.

Das klingt jetzt erst mal abschreckend. Nein, bitte nicht entmutigen lassen. Als ich die Zertifizierung gemacht habe, hatte ich schon etliche Jahre Scrum Erfahrung. Dennoch die PSM I Prüfung ist in erster Linie eine Validierung von Wissen. Die höheren Prüfungen PSM II und PSM III fokussieren dann auf schwierige Praxis-Fragen.  

The Scrum Guide doesn't provide a complete list of the skills required for any of the accountabilities on a Scrum Team. For example, it doesn't specify that Developers must use Java or C# code. The Scrum Guide simply states that Developers need all of the skills to deliver a Done increment of product each Sprint. We intuitively know that the skills required depend on the product. 

TL; DR: Scrum Master Anti-Patterns The Sprint Planning is a core event that defines how your customers’ lives will improve with the following Product Increment.

Im 15. State of Agile Report berichten nur 23 % der Befragten, dass sie Lean-UX-Praktiken in agilen Teams anwenden. 

Many problems at the workplace are not the fault of the individual managers or teams. They are often the result of working in an organizational design(OD) that impedes rather than supports Agility. The OD determines, to a large extent, how people cooperate, the prevailing mental models, and how work gets done. To change all of this takes time and requires people to unlearn old lessons and relearn new ones that support Agility. 

Ponerse metas siempre es importante. Tener rumbo siempre es importante. ¿Pero qué pasa si una organización no tiene claras sus metas?

In this article you will learn: - Why enabling Scrum Teams with UX Design capabilities is important. - Why introducing UX capabilities to Scrum team is frequently hard. - What is the job of an UX Leader in a product development organization. - How to use a UX Design maturity level to coach teams to deliver better outcome

Why is the Scrum Master Role So Uncomfortable? Ryan and Todd discuss the hectic life of a Professional Scrum Master and their challenges when confronting complexity in an organization.

In this podcast Professional Scrum Trainer Joshua Partogi shared how Scrum Masters can propel agility in the company by demonstrating behaviours that reflect the Scrum Values.

In meinen Trainings werde ich immer wieder nach praktischen Tipps und Erklärungen zum Umgang mit den Scrum Artefakten gefragt.

La guía de Scrum cambió la definición de priorizado por ordenado. La definición tiene un sentido que refuerza el uso del empirismo en Scrum y la capacidad de toma de decisiones del Product Owner sobre el Product Backlog.

Die Gründe, warum Scrum Master den Geist des Scrum Guides verletzen, sind vielschichtig. Scrum Master Fehlverhalten reichen von unpassenden persönlichen Eigenschaften über die Verfolgung persönlicher Agenden bis hin zur Frustration mit dem Scrum Team selbst.

Wir sind uns einig, dass die Entwicklung von Features nicht den Beginn eines Entwicklungsvorhabens darstellen sollte. 

Welcome to Scrum Sutra – a blog series where I shall share a 3-min overview of each element of Scrum and how it connects with the other elements in the bead to form Scrum Sutra.

The reasons Scrum Masters violate the spirit of the Scrum Guide are multi-faceted. Typical Scrum Master anti-patterns run from ill-suited personal traits to complacency to pursuing individual agendas to frustration with the team itself.

First, in a blog series about the upcoming book:

In Scrum, part of the Product Owner accountability is to provide a forecast that sheds light on possible answers to the when will we get there question. In my last post, we discussed three ways to size Product Backlog items (PBIs). Today, we’ll discuss ways the Product Owner can use this information to create a meaningful forecast.

Three simple retrospective formats based on the Liberating Structures "Conversation Cafe", "Troika Consulting", and "Discovery & Action Dialogue"

Scrum ist ein taktisches Framework für die Entwicklung von Produkten, vorausgesetzt, Sie erkennen im Voraus, was es wert ist, entwickelt zu werden. Aber selbst nach einer erfolgreichen Produktentdeckungsphase, neudeutsch: Product Discovery, kann es Ihnen schwer fallen, das Richtige auf die Beine zu stellen, wenn Ihr Product Backlog der Aufgabe nicht gewachsen ist: Garbage in, Garbage out. Der folgende Artikel zeigt 27 gängige Product Backlog Anti-Patterns — auch für den Produktbacklog-Verfeinerungsprozesses — auf, die den Erfolg Ihres Scrum-Teams beschränken.

When you aspire to a Scrum Master role, some form of certification on your resume is a must. Scrum.org offers the acclaimed PSM learning journey to support Scrum Masters to professionalise their skills. I am a Professional Scrum Trainer for scrum.org and I have trained hundreds of Scrum Masters over the past few years.  Newcomers start their career with a PSM-I class to gain an understanding of Professional Scrum and the essence of the role of the Scrum Master. I observe that many experienced Scrum Masters hesitate to join a PSM-II class. Possibly that's because it is unclear to many what the PSM-II training has to offer.

When will we get there?  It’s not just something you might hear from the back seat of a car on a long road trip.  It’s something that a Scrum Team’s stakeholders, customers, managers and many others want to know.  When will that thing you are working on be done?  How long do I have to wait for you to deliver what I want? Sound familiar? Today, we’re going to discuss three ways to estimate and in my next post, we’ll talk about forecasting.

Scrum is a tactical framework to build products, provided you identify what is worth making in advance. But even after a successful product discovery phase, you may struggle to create the right thing in the right way if your Product Backlog is not up to the job—garbage in, garbage out.

Was haben eine Agile Transformation, die Dienstleistung einer Personalabteilung und ein Softwareprodukt gemeinsam?

Imagine the stress of getting to work and observing your heart rate rising. It feels as if everyone is out for blood, anything you say can be used against you no matter how genuine it may seem-and managers don't really know what's going on either; they've got favourites among their team members who make most decisions behind closed doors with just a few people involved in each one (those "in the know").

This blog talks about Integrating UX with Scrum.

Hoy me vengo arriba un poco. Vengo a comentar que competencias creo que tendría que tener un líder agile.