Defining requirements up front is not compatible with Scrum, because Scrum teams don’t deliver value in one “big bang”.  Scrum teams deliver value incrementally.  In this article, we will explore how defining requirements up front limits the Scrum team’s ability to learn, inhibits incremental delivery, and ultimately clashes with Scrum.

The Sprint backlog, a cornerstone of Scrum, offers teams a transparent view of their current work and progress. It's essential to differentiate between the Sprint goal and the Sprint backlog, ensuring that teams set achievable goals while maintaining flexibility to adapt to changing needs.

Organizations don't change overnight. Going from for instance waterfall to Scrum is a complicated process, with lots of people involved. Scrum Masters can be the right people to support this transition.

What if management has something important to share with the Scrum Team that they should improve? Or what if the Scrum Team wants to discuss something with management during the Sprint Retrospective? Evelien Roos and Sander Dur discuss this question right here.

Learn how these Scrum anti-patterns categories manifest themselves and how they affect value creation for customers and the long-term sustainability of the organization — Scrum Anti-Patterns Taxonomy (1)

Tipp 7: Bessere Ideen entstehen durch viele Ideen 6 weitere Tipps, wie Scrum Teams endlich mehr Verbesserungsideen in der Retrospektive generieren, erfährst du in diesem Artikel.

El concepto de Sprint 0 en Scrum se refiere a un período de tiempo en el proceso ágil de desarrollo de software, particularmente en el marco de trabajo Scrum. Muchas organizaciones asocian que es el espacio donde se realizan actividades de preparación y planificación antes de que comience el primer sprint oficial.

A personal experience and a tangible exercise to show why complexity requires ‘doing’ instead of ‘thinking’

If you are eager to drive change and improve your business agility, check out this video by PST Robert Pieper.

The concept of limiting work in progress revolves around the principle that focusing on fewer tasks at a time leads to better outcomes. In a Scrum context, this involves setting a cap on the number of user stories, features, or tasks that the development team is actively working on during a sprint. By doing so, teams prevent themselves from spreading thin and promote a concentrated effort on a select number of items.

Cette vidéo fournit une introduction de Scrum, un framework agile très populaire. Découvrez les rôles, les événements et les artefacts qui composent Scrum et comment cela peut vous aider à créer de meilleurs produits et améliorer la satisfaction de vos clients.

How does your Product Owner support adaptation in order to minimise deviations from agreed goals? Each of the Scrum Accountabilities has a role to play. So does the Product Owner. Check it out!

There are many sources for unplanned work: production support, developer pet projects and management requests, to name a few. What is a Scrum Team to do?

🏋️‍♂️🔄 Agile Practices = Gym Memberships? Discover the unexpected connection in our latest article! Just as people sign up for gym memberships with good intentions but don’t always follow through, companies can adopt Agile methodologies without fully reaping the benefits. Learn how to avoid being stuck with an 'unused membership' and elevate your Agile game to its full potential.💡💪

Entdecke eine Reihe sorgfältig zusammengestellter Sammlungen von wichtigen Büchern, Newslettern, Podcasts und Tools, um dein Fachwissen als Scrum Master und Product Owner zu erweitern.

The order of the Product Backlog is incredibly important. How is a Product Owner supposed to prioritize such a critical artifact well? In this lightning round, PST's Robert Pieper and Jason Malmstadt discuss a few tactical tips to help get you started.

It's common practice to ask the Scrum Master to take on the role of facilitator in the 5 Scrum events. Let's go beyond this and move towards more learning strategies, for both the Scrum Master and the Scrum Team.

In this article, we will explore some tactics which I found valuable when I was in need to align Scrum with Project Management practices.

The Definition of Done and Acceptance Criteria both describe facets of a finished backlog item, don’t they? So what’s the difference? Does it matter? YES!! While they may seem similar, there are some crucial distinctions between these two, and confusing them may cause serious problems. I hope this quick video differentiating the two helps!

Warren Buffett once said: “Price is what you pay, value is what you get.”

If you are not getting the value you hoped for from your Scrum transformation, try adding a couple of Kanban practices to your Scrum implementation.

Use the Liberating Structure “Purpose-to-Practice” to create a plan for the Sprint, and revisit & update the P2P canvas during each Scrum event

Explore a series of carefully curated collections of essential books, newsletters, podcasts, and tools to elevate your agile expertise.

Muss ein Facilitator neutral sein? Die meisten bejahen diese Frage vorschnell. Aber was bedeutet neutral eigentlich? 🤔

El descanso en las organizaciones juega un papel esencial en el proceso productivo y de creación de las iniciativas, productos o servicios que prestamos. ¿Alguna vez te has preguntado cómo las organizaciones más exitosas logran mantener altos niveles de productividad y creatividad en sus equipos? Pues todo se basa en el descanso.

How does your Increment support adaptation in order to minimise deviations from agreed goals? Each of the Scrum Artifacts serve to adapt. So does the Increment. Check it out!

How do you uphold Scrum without becoming a Scrum dictator? How do you lead the Scrum Team to ever greater adoption of Scrum within the organization… without direct authority? This article explores the challenges faced by Scrum Masters in their balancing act and how they navigate through it to ensure effective team performance and continuous improvement.

⚡🌩️#StormsOfNeglect: The Cataclysmic Consequences of Ignoring Usable Products in Agile!🌩️⚡ What if I told you that neglecting usable working products in Agile is like navigating a stormy sea without a compass? 🌊🚢 If you think skipping usable products in iterations is harmless, brace yourself for the torrential downpour of woes it can unleash! From eroding stakeholder trust to the tsunami of technical debt, from getting engulfed in the quicksand of adaptability to the barren desert of feedback. It’s a whirlwind of compounding issues that no Agile team should weather! 🌪️💥 Dive in as I illuminate the catastrophic perils of neglecting usable working products when it should foster trust, alignment, adaptability, and quality! 🛡️⚙️

Warum Scrum hinter den Erwartungen zurückbleibt kann — eine Systematik

Organizations have a habit of setting Product Owners up for failure. In this episode, Jeff and Mike discuss common anti-patterns and what to do about them.

How validating the value of the Scrum team’s work during the Sprint limits risk and increases predictability

Explore the challenge of 'Escaping the Product Owner’s Trap' in this insightful blog post. Learn how Product Owners often find themselves entangled in component thinking, losing sight of broader objectives and value delivery. Uncover key principles such as Vision, Value, and Validation, and discover actionable strategies to shift towards a product and value-driven mindset. This guide illuminates the path from mere component management to genuine Product Ownership, offering tools and techniques to align with organizational goals and customer needs.

This case study analyzes the transformation journey using Org Topologies™ Scans and focuses on the Business Banking Hub. The article is valuable if you want to understand how Org Topologies™ can help improve organizational design.

At the heart of Scrum is a unique and indispensable accountability: the Scrum Master. This enigmatic figure may not possess the traditional authority associated with managers, nor do they hold executive powers. Yet, they play a vital and indispensable accountability in the success of the Scrum Team and the organization as a whole.

The Scrum Anti-Patterns Guide, nearing completion, categorizes over 180 anti-patterns by roles, events, artifacts, and commitments. However, it lacks a meta-level taxonomy to address Scrum anti-patterns on broader levels, raising the question of developing such a comprehensive strategy.

Für jeden Trainer kommt der Zeitpunkt, an dem man in den Spiegel schauen und über sehr wichtige Fragen nachdenken muss: 👉 Was bedeutet es wirklich, ein Trainer zu sein? 👉 Konzentriere ich mich auf das Wesentliche? 👉 Warum sind die Teilnehmer in meinem Training? Die Beantwortung dieser Fragen ist für mich mit drei Lektionen verbunden, die ich als Trainer in den vergangenen Jahren lernen musste:

In the post-COVID business landscape, companies must innovate, embrace experimentation, and eliminate silos for success. Clear leadership and Scrum methodology foster collaboration and value creation. A shared vision and self-managed teams maximize value and navigate challenges effectively.

Scrum es un marco de trabajo para maximizar la entrega de valor. Con frecuencia se confunde el valor con entregar más cantidad de cosas en un menor tiempo. El valor es diferente viene desde la perspectiva de entender al cliente, asumir una postura de incertidumbre sobre lo que creemos o definimos acerca del mismo y entender la necesidad de aprender continuamente a través de la experimentación para descubrir, validar y aprender a través del uso de producto para adaptarnos de acuerdo con esto.

Are you using Scrum but not getting the results you want? If you're not producing usable increments, you're not alone. In this video I will explore why the increment is so important in Scrum and how to produce it consistently. I'll also share tips for mitigating risk, delivering value to stakeholders, and providing feedback and insights.

Managers in Agile organizations often struggle when their teams don't evolve into high-performing, self-managing teams. The struggle is to find the right balance between command and control management and being completely hands-off, letting the teams do whatever they want. How might a manager discover adjustments they can try to help their teams grow? this video blog might offer some ideas...

How does your Sprint Backlog support adaptation in order to minimise deviations from agreed goals? Each of the Scrum Artifacts serve to adapt. So does the Sprint Backlog. Check it out!

Does your Scrum Team often find itself with carryover work from the previous Sprint? Does that make your team an unproductive one? Whose fault is it? In this episode, Jeff and Mike share how to limit sprint-to-sprint carryover.  Listen and share with your team so things get DONE.

Find a better balance between solving problems and enabling growth and autonomy

🚀💥#UsableWorkingProduct: Your Ultimate Weapon Against Risks in Agile💥🚀 ⚠️ Ever wondered why some Agile projects falter? Is your fortress of documentation crumbling against the relentless tides of market change? 🌊 Here’s the secret sauce - It’s all about Usable Working Products! 🎯🔧 Too many Agile teams are trapped in the illusion of progress without creating shippable products. It’s time to unleash the secret weapon against risks - deliver increments that users can interact with, validate, and provide feedback on! 🛠🚀

In this article, we have crafted interview questions to help identify the best Product Owner for your Scrum team.

Scrum Werkzeuge, Teil 2: Von Design Thinking über Lean UX zu User Story Mapping

Learn how Scrum Product Owners and Scrum Masters can employ techniques to enhance the user experience and ensure product success.

Dispelling Agile and Scrum myths. Learn how Scrum enables Agile principles. Empower your teams to adapt, innovate, and deliver excellence.

ATTITUDE is the composition of our way of thinking, feeling, and acting. Every team member has an attitude defining their way of being in the Scrum Team. The question is if it is a constructive attitude or not.

The essence of a team is that people collaborate. Else it's incredibly hard to perform as an actual team, rather they just happen to work simultaneously and not together. What to do in such a case?