Yes! Scrum Teams can be effective when working remotely. However, it takes intentionally effort and discipline to break down the barriers that are inherent in remote work.

The Product Goal is a powerful magnet that propels Scrum teams towards value delivery. It guides efforts, prioritizes activities, fosters collaboration, and ensures focus on delivering value to customers. Regular evaluation and refinement are essential to maintain its effectiveness in driving value.

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

In diesem Artikel erfährst du vier Prinzipien, die dir helfen eine effektive Sprint Retrospektive durchzuführen.

Learn from your colleagues. It's approved every time!

10 Liberating Structures To Help Your Organization Lose Weight And Increase Agility

He visto un artículo titulado “Surprise, I am no wizard (Agile nor Scrum)” escrito por Gunther Verheyen, que explora la percepción errónea de que los Agile Coach o Scrum Master son expertos o “magos” en agilidad.

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!

In the agile world, Scrum stands out as a Goldilocks framework. Scrum strikes a delicate balance, providing enough structure to guide teams without stifling their creativity and adaptability. Unlike traditional project management methodologies with rigid processes and exhaustive documentation, Scrum empowers teams to find what works best in their unique environments. Let's delve deeper into what makes Scrum the Goldilocks framework: Not too rigid, not too loose, but just right.

Embracing self-management can be challenging for teams transitioning to Scrum. It involves new skills and a different approach to getting work done. Scrum Masters play a critical role in helping their teams embrace greater autonomy. Let’s look at how.

Workshops ohne Vorstellungsrunde beginnen? In diesen Artikel teile ich 4 Beispiel mit dir, wie du die Teilnehmer deiner Online-Workshops und Trainings von der ersten Minute an einbeziehen kannst.

Scrum.org's Evidence-Based Management (EBM) effectively combines the Scrum framework with an emphasis on value, vision, and strategy. This approach appreciates the unpredictability of product development, promoting fact-based management over speculation. EBM's core involves continuous inspection and adaptation, creating an iterative, incremental process for problem-solving.

In the last “Ask a Professional Scrum Trainer” episode I got a question that was not answered during the session. We discover Non Violent Communication, good coaching questions and patience as key Scrum Master skill.

In this article, we discuss how forecasting in VUCA has always been problematic and the questions that should be asked instead.

In Scrum, the emphasis is on collaboration and flexibility. In this context, a cross-functional team refers to a group of individuals with diverse skills and expertise necessary to complete a software project. These teams self-organize and self-manage and are empowered to make decisions collectively.

How Elon Musk Would Run YOUR Business mit Joe Justice — Hands-on Agile EXTRA, May 4, 2023

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.

Wie unterstützt du als Scrum Master einen neuen Product Owner? Der beste Startpunkt der Schnittpunkt zwischen Entwickler, Stakeholdern und Kunden. Mehr dazu in diesem Artikel.

In this paper, we discuss the stages of Agile transformation based on extensive research and collaboration with experienced Agile coaches.

Each of the Scrum accountabilities participates in one or more inspections. So is the Product Owner. Go check it out!

Eine einfache Möglichkeit, Ihre Retrospektiven großartig zu machen

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 - Inspect & Adapt All the above steps are fundamental to having a sound Stakeholder Engagement strategy.

アジャイルテストの４象限とスクラムチームとしての活用方法

By offering just enough structure, Scrum enables teams to work together effectively while promoting innovation and adaptability.

El desarrollo ágil y centrado en el cliente de productos y servicios se basa en aprender lo antes posible, y de manera empírica, las necesidades del cliente y cómo entregar soluciones que funcionen. En este artículo explicamos 5 ideas que pueden mejorar el valor que entregan tus productos a los usuarios.

Want to elevate your Retrospectives from Good to 🦄 Great? Check out the following ten benefits of this one Retrospective facilitation practice.

Schwierigkeiten bei der Einführung von Sprint-Zielen? In diesem Artikel teile ich 5 Methoden mit dir, die den Einstieg erleichtern.

How a simple experiment can have a huge impact!

Although Scrum is a well-known framework for agile software development, implementing Scrum alone won’t guarantee success. Software development in an agile setting calls for specialized technical abilities, effective process management, and collaborative skills that help teams produce high-quality solutions in short iterations.

While some find it a trendy fad, or a confusing concept, servant leadership can be the key to your agile team’s success and growth. Professional Scrum Trainer Gregory Crown and I will explore the concept of servant leadership, highlighting its historical roots and relevance in the agile community.

El Agile Coaching, también conocido como coaching ágil, es un enfoque utilizado en el desarrollo de software y en la gestión de proyectos fomentando la adopción y mejora continua de los principios y prácticas ágiles.

The Creating Agile Organizations approach is about designing your own organizational framework and coaching its adoption. It is important to note that it is different from frameworks like Scrum, LeSS or SAFe, which have specific structures, rules, events, and artefacts to build upon. Instead, Creating Agile Organizations provides none of that, but provides two sets of guidelines that draw upon decades of academic research and practical experience in organizations similar to yours.

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

Ein Leitfaden zur Erstellung von LLM-Prompts, der die Grundlagen, Dienste zur Verbesserung deiner Prompts und die Verwendung von ChatGPT zur Erstellung von Prompts behandelt. (Ja, das funktioniert auch.)

Don't be afraid to hurry up and get started!

Was ist der Unterschied zwischen Inkrement und Produkt ist, was ist der Unterschied zwischen ungetaner Arbeit und technischer Schuld und warum du dies als Scrum Master unterschieden können solltest, erfährst du in diesem Artikel...

When our brains feel a threat, we shut down. This is often called neurobiological flooding. When flooding happens, creativity and rational thought are extremely limited. For most of our work, that is extremely damaging

A thought, quotes, quick step, and questions on delegated tension within organizations.

A prompt engineering guide covering the basics, services to enhance your prompts, and how to use ChatGPT to generate prompts. (Yup, that works, too.)

Jeder Scrum Master kennt diese Probleme: Problem 1: Wie gehe ich vor, wenn die Timebox der Retrospektive endet, aber das Scrum Team keine Lösung gefunden hat? Problem 2: Was mache ich, wenn sich das Team einig ist, dass es sich uneinig ist? Problem 3: Was kann ich tun, wenn ein Mitglied meines Teams kein Interesse an konstruktiven Ergebnissen hat? In diesem Artikel findest du Ideen, diese anzugehen.

Let’s explore four ways Scrum Teams can manage production support in Scrum effectively.

En Scrum, los desarrolladores desempeñan un papel fundamental en la entrega de un producto o incremento de producto potencialmente entregable al final de cada iteración o “Sprint”.

Scrum Masters and management, when faced with failures in their initiatives related to multifunctional learning, conclude that people do not want to learn. But people are glad to learn when organizational design supports multifunctional development.

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!

This post continues my ongoing series revisiting the principles behind the Agile Manifesto. This time we are focussing on the following Agile principle - “Business people and Developers must work together daily throughout the project.”

Vor einiger Zeit habe ich einen Scrum-Pulse-Webcast für Scrum.org aufgenommen und es hat mir riesigen Spaß gemacht. Eine der Fragen, die mir am Ende gestellt wurden, hat mich allerdings zum Nachdenken angeregt – und ich habe seitdem immer wieder darüber nachgegrübelt. „Verbesserungen in der Retrospektive betreffen oft grundlegende Probleme, die sich nicht in einem Sprint lösen lassen. Wie geht man mit solchen Verbesserungen um?“ Eine ausführliche Antwort gibt es in diesem Beitrag:

Die Lösung der Probleme Ihrer Kunden in einer komplexen Umgebung Kommunikationsfähigkeit, Einfühlungsvermögen, Geduld, Diplomatie und Professionalität. Lassen Sie uns also einen Blick auf einige typische agile Verhandlungen werfen.

This article describes how I used the Org Topologies™ Map to coach a team toward ownership of their own agile transformation journey. Read this article to learn how Org Topologie™s can be applied to coaching the agnostic, framework-free thinking tool.

What is SAFe’s perspective on the Product Owner role? How does it differ from the Scrum Guide? Why is Product Ownership split to Product Owner and Product Manager in SAFe? SAFe’s approach to Product Ownership draws quite a bit of criticism. As a Professional Scrum Trainer who’s also a SAFe Fellow/SPCT, here’s my perspective…

Mito: El Scrum Master actúa como policía para que se use Scrum. Esta es una metáfora para representar un Scrum Master que se enfoca más en el cumplimiento de Scrum de una forma mecánica sin usar los valores de Scrum ni enfocarse en la autogestión. El Policía de Scrum actua de forma impositiva y directiva. Impone Scrum y la forma de usarlo, puede usar reportes o métricas para aumentar el control y el cumplimiento de tareas individuales. Este tipo de Scrum Master limita el crecimiento del equipo, el aprendizaje, la experimentación y daña la creación de un ambiente de confianza basado en los valores de Scrum.