In this second video in the series about responsibility, Professional Scrum Trainer Mark Wavle explores the leader's role in unwrecking responsibility issues.

A few years ago, before the pandemic, I visited an Agile conference in Kyiv, Ukraine. At the very end of it there was a panel discussion with some of the big names in the European Agile world.

In jedem Professional Scrum Product Owner Training werden die gleichen 10 Fragen gestellt. Und das zu Recht! Das sind die Dinge, mit denen die Teilnehmer am meisten zu kämpfen haben.

Here's my twist on an old classic. If I've learnt anything by writing this, it's that I should stick to training Scrum and not writing poetry!

SAFe® has always been a controversial topic within the agile community. Therefore, back in 2017, I ran a survey on the Net Promoter Score® of the Scaled Agile Framework SAFe®. The result back then was -52. Four and a half years later, I believe it is time to rerun the poll: SAFe® has been through several iterations, and many more agile practitioners have experienced working with it. Moreover, the question still is: Would you recommend SAFe ®?

Familiarize yourself with the principles of Liberating Structures and learn how they can strengthen your Scrum Team.

Extremes of responsibility are wreckers of teams and leaders. In this Unstuck Leadership Moment, Mark explores two unhelpful and unhealthy responsibility stances.

Wie können Scrum Teams in ihrer Entwicklungsarbeit den Nutzer niemals aus dem Auge verlieren? Hier 3 einfache Praktiken, die sie von YouTube, LinkedIn, Microsoft lernen können.

A common question we get asked is how do we get started with creating a Definition of Done? Let's explore how we can obtain transparency of where you are, your destination should be, and what your possible first steps are to get there!

La autoorganización es un proceso en el que alguna forma de coordinación surge de las interacciones entre los componentes de un sistema inicialmente desordenado.

A roadmap is a complementary practice that a Scrum Team might use to forecast upcoming deliveries or to translate Product Backlog items into a visual representation. This article includes a few Roadmap templates for Product Owners to use to communicate their forecast to customers and stakeholders. Give them a try and let me know what you think in the comments section!

If you are an agile leader - do you know whether your teams are currently operating at a sustainable pace? Do you care? Would you rather not know because you’re afraid of the answer? 

El Scrum Master es un líder servicial que se enfoca en el crecimiento de las personas, trabajo en equipo, la adopción del empirismo y la autogestión para ayudar a maximizar la entrega de valor. Ser exitoso como líder servicial se evidencia cuando las personas a las cuales se sirven son exitosas.

In this blog post, PST David Sabine shares a real life story focused around transparency.

Read on and learn more on how to best sabotage a Scrum Master from the exercise results of more than ten PSM I and PSM II classes. (I slightly edited the suggestions for better readability.)

Über 100 Jahre Industriezeitalter haben uns gelehrt, dass die Lieferung von Produkten den Erfolg eines Unternehmens bestimmt.

Myth 1 – Scrum is a Methodology To bust this first myth, I would prefer to differentiate between the concepts of methodology and framework. Methodology vs. Framework

In this Unstuck Leadership Moment, PST Mark Wavle explores the power of building a sense of ownership with the people we lead.

Last week, we talked about common misconceptions related to the Daily Scrum.  This week we’ll focus more broadly on misconceptions impacting everything from the Product Backlog to the composition of the Scrum Team itself.  

TL; DR: Designing Powerful Questions with Daniel Stillman Powerful Conversations are the environment that drives change.

Why it matters to have a shared understanding of the product your Scrum team is building.

The Project Mindset approach, in which success is defined upfront based on Scope, Time and Budget, will (based on experiences) lead to less business involvement and more task management. The Product Mindset approach, in which success is continuously driven by business metrics like User adaption/retention, revenue cost saving per feature, will (based on experiences) lead to less waste, more creativity and more releases.

Kanban et Scrum sont deux outils qui se complètent très bien. L’un apporte des informations pour analyser la performance du flux de création de valeur, l’autre apporte des artéfacts et des boucles de rétroaction pour rendre transparent la performance de vos processus.

La réussite de l’entreprise est directement liée la satisfaction des utilisateurs aujourd’hui mais aussi dans la durée. Pour assurer cette réussite, l’implémentation de différents « Key Value Measures » pour piloter ensemble les quatre « Key Value Areas » proposés par « Evidence-Based Management » offre un pilotage avec une vision globale de la situation, approche nettement plus pertinente qu’une optimisation locale portée par les KPI habituels.

What is happening awesome people? I hope you had a great weekend and ready for the week. Throughout 2021 I am seeing more companies are using Scrum.

The Agile Manifesto hasn’t changed since its creation in 2001. Scrum however, has been updated many times. Is the connection between the Agile Manifesto and Scrum still there?

Toll, die PSPO I Zertifizierung gilt lebenslänglich, d.h. man muss sie nicht erneuern.

Wann ist das Feature fertig? Diese legitime Frage, die Stakeholder im Sprint Review stellen und welche regelmäßig Mitglieder des Scrum Teams zusammenzucken lässt, sollte jeder erfahrene Product Owner beantworten können.

Insights from 7 scientific studies into what it is that Product Owners do and what makes them successful

Not all trainers use an online classroom for the distribution of course materials. However, if your Professional Scrum Trainer (PST) informed you that you would be able to access post-class materials in the Scrum.org "online classroom.", here is an image that explains where you can find the link.

Even a well-set team with clear objectives may fail to finish each thing when the Sprint ends.

Aligning Scrum Team Topology to Strategy with OKRs and Product Goals

Hier mein bewährtes Rezept, wie Product Owner das Sprint Review zu einem gemeinschaftlichen Arbeitstermin machen können und nicht zu einer Demonstration, Präsentation oder Feature-Abnahme verkommen lassen.

In my recent post, I told the story of the time I was fired as a Scrum Master. This time I will tell you about a time I decided to quit (probably shortly before I would have been fired!).

TL; DR: Ignoring the Capacity Check during Sprint Planning There are plenty of failure possibilities with Scrum.

Many self-managing teams struggle to reach a truly high-performing state. When an organisation moves to a self-management model, a key service centralised management traditionally played – giving feedback – is often ignored, leaving teams struggling to truly grow. In this article, we share how to give effective feedback to improve both team and individual performance.

A culture of feedback is a critical element of an adaptive organisation. While people have talked about how to give effective feedback, little has been said on how to receive it, until now.

It might surprise you that even those with years of Scrum practice sometimes make statements about the framework that are, well, inaccurate. The Scrum Guide outlines how teams can learn to work together to deliver complex work. It’s not a how-to list of instructions, and perhaps that’s what leads to misinterpretation.  Last week, we discussed some of the most common, if well-meaning, misconceptions about Scrum in general.  Today, we’ll dive further into this topic with a focus on the Daily Scrum event.

The Professional Scrum Product Owner (PSPO) course has evolved over the years and the PSPO I assessment has become even more difficult! I consider this assessment the most difficult of all the Scrum.org entry level assessments and it pays to be prepared. Here then, is my updated guide on how to pass the PSPO I assessment.

Want fabulous teams that build great products? Great teams don’t happen by accident. And they don’t have to take a long time to build. Learn more from Richard Kasperowski on employing core protocols for psychological safety and emotional intelligence from this Hands-on Agile session.

Eine bewährte Anleitung, wie Du als angehender Product Owner ein Sprint Planning in Jira durchführst

​​​​​​​According to the 15th annual State of Agile Report, there has been a tremendous increase in the adoption of agile frameworks this year.  Within software teams, agile adoption grew from 37% in 2020 to 86% in 2021.  This rapid growth undoubtedly means many individuals working within agile frameworks have not undertaken formal training in it.  It’s the perfect environment for misinformation to spread.  Below are a few of the most common misconceptions about Scrum.  

German blog on 5 lessons that I learned in the first year as a product owner that can save you a lot of time and frustration

TL; DR: The Agile Metrics Survey 2021 If you value agile practices, it is crucial to know if a job offering or a prospective business partner that claims to be “agile” really keeps its promises.

Is your preferred approach to starting an Agile "Transformation" sending a bunch of worker-bees to Agile Training and then waiting for the magic to happen?

As long as the Scrum team has the drive to learn and to run experiments to figure out what works for them, Zombie Scrum (or fake Agile) won’t find futile ground and can’t take root!

In this vlog, PST Joshua Partogi shares how Sprint Review is often misunderstood as a demo or showcasing or an acceptance testing session. In this vlog, he busts myths around Sprint Review and how a Sprint Review should look like according to Scrum Guide 2020.

One of the most common reasons for organizations to adopt Agile is to improve quality.

You may have heard of the phrase 'Scrum ceremony'. Which is odd because it's never appeared in the Scrum Guide. But clearly it exists and it's in common use. So, where did it come from? What does it mean? Let's find out.

10+ years of helping organizations scale Scrum from one team to 500+ teams has taught me one thing - most practitioners abandon the scientific principles and core values of Scrum in their pursuit of scaling Scrum. To many of these practitioners, Scaling Scrum is a whole another ball-game to which Scrum principles and values do not apply.