The Siren song of SAFe

I've been using a visualization that people find useful for understanding the relationship between the various Lean/Agile requirement containers. Some people call the full model a dinosaur. Others are reminded of the snake who ate an elephant from "The Little Prince". (I'm sure there is a good connection to elephant carpaccio somewhere in here ...). In this article I'll explore this model and connect it to the stances of the Scrum Product Owner. 

In light of the new normal and the last 20 years of technological progress, we need to 

As more and more organisations move towards a higher degree of agility, they inevitably also move towards DevOps practices like Continuous Delivery to facilitate shortening the feedback loops.

In this blog post, we share our experience, recommendations, and lessons learned by providing the online PSM II class.

Habits first and then progress follows! There is a huge power in the little things.

Many organizations I have seen in my life does not care for their Development Team. Join me in a short analysis of why that happens and what - in fact - is a Development Team.

A Sprint Review is perhaps one of the most difficult elements in the product development with Scrum.

Lors de mes formations Scrum

TL; DR: Results of a Test of Using Unhangout to Host Virtual Barcamps Last week, 30-plus attendees of the 24th Hands-on Agile meetup ran a virtual Barcamp experiment w/ MIT’s Unhangout, an open-source platform for organizing attendee-driven v

Extremes are everywhere - with nutrition, training, health, mindset, software, hardware, frameworks, business, competition , process, tools and people etc.

A few years ago, I became acquainted with a lady running a charity for a child who was having medical bills pile up. She was holding a charity bazaar to raise money for the child's family.

Personal Fitness and Business Agility have a lot in common. Both are about bringing small, sustainable changes in your day to day behaviours, habits and mindset.

Cuando queremos construir una buena base de conocimiento a partir de una historia de usuario, entonces necesitamos hablar sobre las personas, las necesidades de las partes interesadas, el contexto del uso del producto, el dominio comercial, las restricciones, la disponibilidad de datos, etc.

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.

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

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

Le Daily Scrum n’est-il pas l’événement où l’on vient vérifier que l’équipe de développement avance comme prévu ?

Несмотря на то, что глобально адаптация Скрам в настоящее время составляет 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.