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.

In this video you will get some helpful tips for facilitating a Product Backlog refinement session. (4:41 Minutes)

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

In this episode Dave West interviews Jim Ewel and Melissa Reeve from the Agile Marketing Alliance to talk about how marketers use Scrum and other Agile frameworks (29:57 Minutes)

In this episode of the Women in Agile Podcast, Hayley Rodd and Renae Craven explore the topic of imposter syndrome and some strategies for overcoming it when you feel it bubbling to the surface. (36:55 Minutes)  

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 ...

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

In this webinar LAP pioneer Mirko Kleiner and PST Simon Reindl explored how to bring agility to the wider business, and tackle the challenges of complex procurement.

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 usua...

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 s...

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, Creati...

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.)

This episode of the Women in Agile Podcast explores the topic of what agile is today and what we have noticed in how it has shifted in organizations over the last 15 years. About the Featured Guest Sam Liang is an agile coach and her personal motto is ‘be brave’. Sam embodies this by tak...

In diesem Scrum-Pulse-Webcast stellt Professional Scrum Trainer Simon Flossmann weitverbreitete Mythen über Scrum vor.

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 ...

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 Re...

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.

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.

The Sprint Review is a working meeting where the Scrum Team presents their completed work to stakeholders and asks for feedback. The Scrum Team and stakeholders discuss the progress made toward the Product Goal, emerging changes in the business or technical climate and collaborate on what to do next

The Sprint Retrospective is the last event in the Sprint. Unlike other Scrum Events where the focus is on inspecting and adapting ways to improve the product, the Sprint Retrospective is a place for the Scrum Team to inspect and adapt their working practices.

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)

To help ensure that the work the Scrum Team delivers is valuable, they need to work together, share ideas and responsibilities and have team ownership while also working closely with their stakeholders, including customers and end users.

The five Scrum Events provide regular opportunities for enacting the Scrum pillars of Inspection, Adaptation and Transparency. In addition, they help teams keep aligned with the Sprint and Product Goals, improve Developer productivity, remove impediments and reduce the need to schedule too many additional meetings.

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.

Scrum Teams need to make decisions all the time. Helping teams reach a decision effectively, and gaining necessary buy-in from all team members can be challenging, especially when team members are unclear on who has the final say in making it. Understanding the decision rule, how a decision is made and whose input is required, is necessary because ambiguity in the decision process causes confusion and frustration.