Die Minimum Viable Library Product Owner Edition ist verfügbar! Entdecken Sie eine Reihe sorgfältig zusammengestellter Bücher, Newsletter, Podcasts und Tools, um Ihr Fachwissen zu erweitern.

Ser un Scrum Master efectivo que ayude a un equipo a ser exitoso puede tener sus complicaciones y llevar a un Scrum Master a mal interpretar la forma adecuada de ayudar y dar soporte. En este artículo presentamos tres errores comunes que muchos Scrum Master asumen.

Those newly introduced to the Scrum framework often have the same first question: What’s the difference between Scrum and traditional project management? Most people are familiar with the basics of traditional project management, so the question is a great place to start for understanding Scrum and its benefits.

Jeff and Mike discuss guaranteed ways to make a Scrum Master fail. Do the opposite to aid in their success!

Here are some study notes that I created whilst learning more about Evidence-Based Management from Scrum.org. These are shared as a revision resource intended to summarise the key elements from The Evidence-Based Management Guide.

What is release planning? When is it done? How do we manage stakeholder expectations and answer the infamous "when will it be done" question? How do we forecast? What numbers and methods can we use to forecast more accurately?

Working virtually can be challenging when it comes to feeling you truly working as a team. This guest asked us what you could do or try to create a team feeling in a remote environment.

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

Test which rules really matter and trigger a wave of change in your organization

Was kannst du von „Karl Klammer“ über Produktziele lernen?

Unleash Scrum's Potential: Discover Where to Start for Efficient Value Delivery (Product) and Continuous Improvement via Value Stream Mapping

How to use your brain better when working on complex problems.

Don't write Product Backlog Items, have a conversation about them!

Organizations have been taking their efforts toward Agility for many years. Some of them seem to be successful in this field, and some of them are not. So, how to measure the results and benefits of this effort?

Are your Developers really making VALUABLE adaptations towards the next Product Goal? In order to minimise deviations from agreed goals? Each of the Scrum Accountabilities has a role to play. So do the Developers. Check it out!

🔍 Discover the underpinnings of a transparent and promising future in Agile Product Management! My latest blog post explores the indispensable role of an ordered Product Backlog that is coherent, refined, and rightly sized.

Wie läuft ein typisches Meeting ab? Wenn deine Antwort lautet: Viel Stress, wenig Ideenvielfalt, niedriges gemeinsamen Verständnis und dadurch viel Frustration bei den Teilnehmern, dann solltest du weiterlesen:

Erfahren Sie, wie sich diese Scrum-Anti-Muster-Kategorien manifestieren und wie sie sich auf die Wertschöpfung für Kunden und die langfristige Nachhaltigkeit der Organisation auswirken.

This must be one of the most asked questions that we get; what books do we recommend.

Quel est le rôle du product owner dans scrum ? Product Owner définition ? Que doit-il faire ? Quelles sont ses responsabilités? Quelles sont les erreurs très souvent commises? Dans cette vidéo nous répondrons à toutes ces questions. Ce sont des informations basées sur le guide scrum 2020.

To excel as an Agile facilitator, understanding the importance of facilitation skills and mastering the essential Scrum facilitation techniques are paramount. This blog post provides insights into these essentials while shedding light on how our Professional Scrum Facilitation Skills™ course can aid your Agile journey.

In this article we discuss why agile engineering practices in software development are essential To achieve agility.

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! 🛡️⚙️