What's up awesome people. I hope you are all having a great week.

Commitment is key. Commitment is somethins every team, every manager, every organization wants and needs. Commitment promises better results, engaged people, good relationship with work and many other benefits. The problem is that it can be misunderstood. 

The Spotify "model" pops up as either advocated practice (especially by large consulting companies) or some sort of a hoax and hated practice. I wrote this text few years back, but it appears to be valid more than ever. Join me in discovering 10 lessons from my "spotify" encounters.

La idea de este video es obtener algunas prácticas concretas de trabajo en línea, desarrollar algunas habilidades y reunirse nuevamente y compartir nuevos conocimientos y preguntas.

Many organisations don't really want to change how they do business and believe that they can continue in the way they always have while still getting better at delivering software. They are wrong!

Scrum está dirigido a un único Producto producido por un solo Equipo Scrum. Dos equipos, y a veces tres, pueden usar Scrum para desarrollar un solo producto. Pero a medida que se agregan más equipos, los equipos necesitan un poco más que Scrum para administrar sus dependencias entre equipos para garantizar que puedan ofrecer incrementos de productos que funcionen.

Like most tools, if you want to run successful training in Microsoft Teams you need to do some homework and some configuration before your class.

Usually conversation between developers and Product Owner goes around acceptance criteria just to negotiate scope of requirements for one user story, but knowledge and context are not conveyed in the same structured way. User Story Canvas can help Scrum Team to fix these problems by focusing team to confirm more complex aspects.

With the new normal, I have been delivering all of my 

TL; DR: The Agile Movers & Shakers Interview w/ Ryan Ripley Today’s guest is Ryan Ripley. Ryan is a Professional Scrum Trainer (PST) with Scrum.org.

For many years, many of us have had strong opinions about the importance of having teams that are co-located.

Would like a tool that delivers better product and customer outcomes and actually pays for itself? Read on.

If you were in my class, you probably remember the exercise, where participants list roles, artifacts and events in Scrum.

At many customers I visit, I see a lot of effort being put into classification and managing bugs.

Something very close to my heart is helping folks understand the origin of the practices that are commonly used in management today. I feel that only with an understanding of history can we figure out how to change the future.

One of the most asked question in my PSPO class is "What is the difference between Product Manager and Product Owner?", "Who has higher authority than the other?". There are many blogs, articles and youtube videos on the internet that compares Product Manager and Product Owner.

Experiments, practices, and strategies that help Scrum Masters prove their value to the organization.

"Scrum and Organizational Design in practice" is my contribution to 

TL; DR: Remote Agile Transitions We are used to saying the Scrum is a perfect probe for organizations, as it will reliably discover all dysfunctionalities.

First of all, I'd like to note that models and terms I am using and discuss are not mine. They come from training and coaching sessions belonging to Vroemen from Teamchange. The connection I make to Scrum is my interpretation. 

There are many books and articles written differentiating between machines and people. An organization is a group of people.

Un gran Product Owner tiene que estar enfocado en producir experiencias e impactos sorprendentes en los clientes a la vez que soporta el cambio de la organización hacia la agilidad con un enfoque de producto brindando el soporte necesario para que el equipo de desarrollo pueda optimizar el trabajo que realiza.

How to make sure that the definition of Done is used properly at a sprint planning session? Continue reading ...

Le Daily Scrum est majoritairement incompris. Vu comme une réunion d'avancement, il est en réalité un levier à l'auto-gestion des équipes. Il n'a rien à voir avec un point d'avancement, re-découvrons-le…

Несмотря на то, что глобально адаптация Скрам в настоящее время составляет 75% (источник: 14-й доклад о состоянии Agile-2020), многим по-прежнему трудно понять профессию Скрам Мастера.

A few years ago, I became a Product Owner. But not in the traditional ways most do.

The contradiction and tension between the empirical process of Scrum and the often-used efficiency mindset.

The Scrum Master tactics series are a series of articles in which I write about and explore contemporary techniques that will aid you in your journey as a Scrum Master. The tactics explained stem from my personal experience as a Scrum Master which I accumulated over the years in working with many different teams and contexts.

Last week, 30-plus participants in the 23rd Hands-on Agile meetup had a virtual strategy session where they explored Liberating Structures’ Critical Uncertainties microstructure. They identified robust and hedging strategies for Scrum Masters and agile coaches regarding the challenges of remote work and distributed agile teams.

Even though the global Scrum adoption is now at 75% (source: 14th State of Agile report 2020), the Scrum Master profession is still difficult to grasp for ma

In my daily life as a Scrum Master, I witness many crazy situations. I want to share my discoveries via this comic series featuring Koos Coach, the silly Scrum Master struggling to understand and master Scrum.

I've learned and experienced that most symptoms can be traced back to not adhering to the Scrum Roles. Let's have a closer look at the Scrum Master role.

How do we run a virtual open space event or BarCamp with a large number of participants? Principally, we could use break-out rooms for organizing the sessions.

In our professional world of software development, it is very common someone asking “What is this Agile?”

I was once told that we have one mouth and two ears and that we should use them in those proportions. Now, those who know me will know that I struggle with that....

A lot of people are trying to do agile without being agile. But what does that mean and why should you care?

Scrum is all about self-organizing. But what does that mean? And more specifically, how can Liberating Structures support that? In this post, we reflect on Liberating Structures from the perspective of self-organization.

The concept I describe below is tested, proven, and modeled after my virtual Professional Scrum training classes.

Scrum Teams are always dealing with complex problems, unpredictability, and change.

The fact is, Scrum and DevOps works well together.

Many scrum teams use a metric called velocity as their primary metric. Velocity is commonly defined as the number of story points you finish over time, usually measured by sprints. Measured from sprint to sprint, it becomes a sort of gauge of success. If it stays the same or goes up, that’s great. If it goes down repeatedly, there’s a problem that needs to be investigated.

In this story, I describe and debrief a difficult moment I experienced as a coach. In addition to this writeup being my personal reflection, it might serve as a source of learning for you.

As the name “Test First” suggests, you write a test first before the actual code and keep them running all the time. Well, maybe not the second part explicitly. Yet what if I said to you that it actually means more than that?

With the new normal, online training has exploded, but potential students are confused about what makes a great online training course and the results seem hit and miss.

Here is a list of 8 Questions for Scrum Masters to improve the effectiveness of Sprint Reviews

Shu-Ha-Ri has been a frequent topic within Agile communities for years to capture the essence, the progress of the journey we embark on as we grow and learn better ways of working.

TL; DR: The Agile Movers & Shakers Interview w/ Christiaan Verwijs & Barry Overeem Today we welcome Christiaan Verwijs & Barry Overeem.

A physical build monitor - like a light that turns red when a build fails - is a great way to get fast feedback. Its also a fun & educational activity for Development Teams, as it gives them a product of their own they can apply their craft to. And it encourages a Developer Culture.