In a recent episode of Your Daily Scrum, Professional Scrum Trainers Todd Miller and Ryan Ripley address a general question in Scrum circles: What Does a Scrum Product Owner Do All Day?

In a recent episode of Your Daily Scrum, Professional Scrum Trainers Todd Miller and Ryan Ripley teach you the Scrum Framework in 7 minutes!

In a recent episode of Your Daily Scrum, Professional Scrum Trainers Todd Miller and Ryan Ripley debunk a general myth in Scrum circles: Creating a High Performing Scrum Team is NOT the Goal!

It's time to look at the Scrum Events

In today's vlog, PST Joshua Partogi will show you how your Scrum Team can save time and make a forecast during Sprint Planning with #NoEstimates & Kanban metrics.

Scrum celebrated its 25 year anniversary last year with an update to the Scrum Guide and lots of socially distanced parties. Over that quarter of a century, Scrum has gone from a niche method used by software developers to mainstream adoption with many millions of people using Scrum or at least parts of Scrum every day. Now Scrum is not just a smart way of delivering software, it is a fundamental part of any enterprise agility transformation. 

​​​​​​​The Sprint Review meeting is one of the Product Owner’s most important events.  But even the most important events can become a little stale over time.  Here are five ideas to spice up your Sprint Review meeting. 

Die Firma Skype hat in den frühen 2010er Jahren Scrum eingesetzt, und alle zwei bis vier Wochen Releases rausgebracht. Dennoch hat WhatsApp sie völlig abgehängt, wie wir heute wissen. Und das obwohl die Mannschaft hinter WhatsApp viel kleiner war als die hinter Skype. Wie konnte das passieren?

All teams have leaders. They're re accountable, amongst other things, for their team’s effectiveness. Perhaps the best way to enable this effectiveness is to empower the team. But how to empower the team? This article covers three easy tips to do just that.

Das Problem mit Features ist, dass sie fertiggestellt und ausgeliefert werden sowie perfekt funktionieren, aber dennoch keinen Wert liefern können.

Alguna vez te has preguntado: ¿Cuáles son los beneficios de usar Scrum y trabajar en equipo con el marco?

Being a Scrum Master can be tough. You are accountable for helping organisations change the way they approach complex work. If you upset enough of the wrong people you may end up “changing” yourself out of a job.

In this Unstuck Leadership Moment, PST Mark Wavle explores the question, "How do I help an unmotivated team?"

A lot of talk in the Agile space centres on breaking down silos, and yet it appears that in practice it is one of the things that is met with the most inertia.

We started the Scrum Guide for Leaders series with a discussion of what Scrum means for you as a Leader. Next, we discussed the conditions where Scrum's Empiricism, Self-Management, and Continuous Improvement can thrive. We then explored some concrete examples of how adopting the Scrum Values as a Leader can help you create these conditions.

There are plenty of failure possibilities with Scrum. Since Scrum is an intentionally incomplete framework with a reasonable yet short “manual,” this effect should not surprise anyone.

As mentioned earlier, Scrum is founded on empiricism - transparency, inspection, and adaptation. Empiricism is only possible in certain cultures and contexts. Leaders have the role of creating and nurturing the culture and shaping the context.

The 2020 version of the Scrum Guide dropped the classic “three questions” of the Daily Scrum. Yet many teams stick with the practice, even when it doesn’t produce the collaboration that is the hallmark of a valuable Daily Scrum. When a Scrum Team I worked with said that their Daily Scrum was lackluster and unproductive, I challenged them to design a better one. The new pattern we created shifted the focus from individual action to team collaboration toward the Sprint Goal.

Häufiges Feedback ist der Motor, meine Schulungen ständig zu verbessern.

The more ambiguous the requirement, the more difficult it is to calculate how long something will take. But teams still need to estimate their work to forecast releases. Relative sizing provides a realistic method for estimating. Ultimately, your team will find their own value scale and their own language that is meaningful to them. Until then, these Practical Fibonacci tips will help kick-start your relative sizing.

The future is unknown and although some people claim to be able to predict the future, most people can't. But to look a little ahead, into the future, to have a sense of when certain items on the Product Backlog are finished, predictability would be very useful. Although we can't be completely predictable, it is helpful if we are a little more predictable than we are now. And therefore we need some measurement results from the near past.

(And that should benefit experienced Scrum Masters too)

In today's vlog I would like to come back to the fundamentals of Scrum ... Done Increment.

In this Unstuck Leadership Moment, PST Mark Wavle explores the question, "How do I know if my measures are the best ones?"

TL; DR: My Top Ten Worst Scrum Anti-Patterns I recently was invited to a Scrum.org Webinar, and I picked a topic close to my heart: the worst Scrum anti-patterns.

A Scrum Event is a meeting. So why don't we just call it that? Why create a new word? Given the poor reputation that meetings have, maybe it's not a surprise. Rather than replicate the name and pain of meetings, the Scrum Events are designed to replace them and be all that you need. The power of the Scrum Events is in the way they're time-boxed and in their purpose. Let's take a closer look.

If you’re leading Scrum Teams or generally are a leader in an organization that’s leveraging Scrum?

Scrum Teams entwickeln eben nicht nur Produkte und Services, sondern betreiben diese auch. Ohne den Betrieb einer Anwendung ist es unmöglich, Feedback zu erhalten. Allerdings ist Feedback essenzielle für erfolgreiche Scrum Teams, da es die Triebfeder ist, um Nutzer- und Kundenwünsche zu erfüllen. Beim Betrieb von Produkten und Services kommt es zwangsläufig zu ungeplanter Arbeit. Fehler treten auf, Nutzer geben Feedback, Kunden brauchen Support und Notfälle treten ein.

Let me share some of the controversial findings and discussions with you. As always, there are no simple answers in complex environments.

The term 'Scrum Master' seems to have been around as long as Scrum. But has it? In this article I talk about where the term came from and why it was initially used.

Why hire a professional Scrum Master? They cost extra and you can always get one of the developers to do the work, part-time. Big saving, right? Not so much. Here's why.

This question comes up when discussing the accountabilities of the Scrum Team and the Developers. The Scrum Guide says on page 5: 

So many times, I’ve heard that round about 50–70 % of all software features are rarely or never used. In the Cloud we can now even measure it.

The Applying Professional Scrum class is frequently overlooked when it comes to public classes.  People tend to go for the Professional Scrum Master class or the Professional Scrum Product Owner class instead.  And those are really great classes.  That is… they’re great for those who already have an understanding of the Scrum framework.

The Scrum Guide has a lot to say about the Product Backlog, and rightly so. It's pivotal to everything a Scrum Team does. But one thing the Scrum Guide doesn't tell you, is how you create a Product Backlog. So, here's one way you can do exactly that.

In June 2012, I wrote the world's first ever article that advised readers on how to pass the Professional Scrum Master I (PSM I) assessment from Scrum.org.  It was hugely popular and I'm flattered that it's been copied so many times.

When you first start to use Scrum you will need to decide which day to start your first Sprint, and there will be implications to that decision. Here are some possibilities and their implications to help you make the best decision.

Scrum of Scrums describes one of the first approaches to scale Scrum and is often confused with Nexus Daily Scrum.  

In today's vlog, we will explore the ingredients to use Scrum with User Experience (UX).

TL; DR: The Obsession with Commitment Matching Velocity Despite decades-long efforts of the whole agile community—books, blogs, conferences, webinars, videos, meetups; you name it—we are still confronted in many supposedly agile organizations

La agilidad provee capacidades para ser adaptables para crear productos innovadores y responder a los cambios. Esta innovación debe basarse en un nuevo modelo de negocio para responder a la incertidumbre del mercado.

Measurement is important, but it's not just about what we measure. It's about understanding why we measure and how we use those measures. In this post, I will share some common patterns I have noticed that lead to using measures poorly.

If the Empire had used Scrum, then Darth Vader would surely have been considered the Product Owner for the Death Star.  While Darth Vader does appear to have engaged in some of the traditional activities of a Product Owner, such as stakeholder engagement, his methods and his lack of faith in the Scrum framework are… disturbing.  

All elements of the Scrum framework play a role in enabling empirical process control. Sprint Goal is a commitment that reinforces empiricism, however, it remains a part of Scrum which often is being neglected or causes challenges to many Scrum Teams.

In a recent episode of Your Daily Scrum, Professional Scrum Trainers Todd Miller and Ryan Ripley address a general question in Scrum circles: How Do You Increase the Velocity of a Scrum Team?

In this blog post, Dave West answers the question - How do you, for the lack of a better word, “manage” Stakeholders?

Agile isn’t the right fit for every business problem–it’s simply a tool in the toolkit–one of many.

Many Scrum Teams make use of Velocity. In the right hands, it's an incredibly useful measure. In the wrong hands, it can become a tool of obfuscation and even oppression.

In a recent class, a student asked, “What are the common difficulties teams face when starting with Agile?”  To  answer this question, I refer to the Tuckman Model of group development. Psychologist Bruce Tuckman discussed team performance in his 1965 paper, Developmental Sequence in Small Groups, introducing the four phases of team dynamics.  He labelled these phases "forming, storming, norming, and performing.” For Agile teams, the goal of the Scrum Master or Agile coach is to get teams through the first three phases (Forming, Storming and Norming) as quickly as possible so that the team can get to Performing.  In this article, I will discuss the tools that are used at each phase of the Tuckman model to coach teams towards peak performance.

This latest update to the interview guide addresses Product Owner anti-patterns from Product Backlog management and refinement to the Sprint Review.