Scrum limita el riesgo, proporciona transparencia y ayuda a la adaptación a través de los Sprints y la entrega alto valor. Scrum funciona bien con equipos auto organizados que tienen todas las competencias para entregar el incremento de producto.

Scrum is easy to understand, yet difficult to master. The Scrum Guide says so and it's true. If you have worked with Scrum in your organization you probably recognize it also. It's not difficult to start with Scrum.

Scrum is intended as a simple, yet sufficient framework for complex product delivery. Scrum is not a one-size-fits-all solution, a silver bullet or a complete methodology.

In my experience, the word YES is one of the biggest things holding the organization back from focusing on their desire towards innovation, disruption, agile, or more customer-centric.

The Professional Scrum with Kanban (PSK) class was launched a year ago - Feb 26 to be precise.

In this little blog I share some tips for multi-team Product Backlog refinement.

In this blog post, we describe how to use Conversation Cafe, as a Liberating Structure, within Scrum.

In 2016 the Scrum Values were added to the Scrum Guide. In this article I share a workshop I run several times, with excellent feedbacks, hoping that you'll see value in reusing it in your working environment.

I just celebrated my 48th birthday. This is quite a milestone because being born with Cerebral Palsy the odds were not in my favor to reach this age, let alone a professional career in leading change and leading leaders.

In January 2019 I was at Prowareness in Delft, Holland, and attended the 2 day Professional Product Owner course delivered by Ralph Jocham, co-author of The Professional Product Owner book. I thought I'd share my thoughts on the course with you.

No hay necesariamente una relación directa entre la complejidad de un PBI definido en términos de puntos de historia y el tiempo de desarrollo. Es decir, un PBI o historia de usuario que tiene mayor complejidad en puntos de historia puede terminarse en menos tiempo que un Item que tenga menos puntos de historia.

As people become more empowered and capable of taking ownership of their process and executing on their decisions, the next area to focus

Agility is a continuously evolving state that is unique to a specific organization, given the organization’s people, its constructs and its history. A traditional (industrial) approach to becoming more Agile (adaptive) commonly creates no more than an illusion of agility.

The 2019 Scrum Master Trends Report is an update to the 2017 Scrum Master Salary Report that Age of the Product conducted in 2017. By partnering, we have secured a larger sample and broadened the reach of the research, growing from over 500 to more than 2,100 respondents and adding more geographies and a broader set of demographics.

Recently as I was delivering a keynote about leaders sharing their failures one person from the audience asked me mine. I shared some from my blog I wrote a couple years ago...

Hello, great people of the world. Welcome back to the Scrum Master blog series with yours truly. As we enter the new year, we are seeing Scrum becoming the most commonly used framework to manage complex product delivery in the industry.

In my career, I have had the great privilege to witness different companies undergo many different phases of agile transformations. I’ve met many amazing Scrum Masters along the way that have evolved to take on major responsibilities in their organizations.

How are you interacting with your employees today? Are you taking the time to make an authentic connection?

A discussion is raging among Project Managers about the Iron Triangle because the authors of Scrum say “Scrum breaks the Iron Triangle”.

Why would Product Owners prevent value delivery, you ask? They shouldn’t, and don’t want to, but yet I see them do it every day. And usually, it’s without them even knowing they’re doing it. Here’s four observations of how Product Owners prevent value delivery, and suggestions to improve.

Scrum stands on the three legs of transparency, inspection, and adaptation. Of these, transparency can arguably be said to come first. Unless a situation is made clear it cannot be inspected, and any consequent adaptation arising therefrom is likely to prove futile.

One common misconception of agile is that it simply allows you to get everything done faster. This is simply not true. Agile allows us to plan a much smaller scope of work, delivering iteratively and incrementally to deliver the least amount scope needed to solve the problem/capture the opportunity.

This is the third post in a series on tools for Scrum Masters and their teams.

The Professional Scrum with Kanban (PSK) course has now been out for more than 6 months at Scrum.org. As one of the first few trainers who wanted to teach this course when it came out, I find it is a great way to combine the Scrum framework with Kanban as a strategy to deliver value to your customer.

Scrum is simple to understand. The Scrum Guide is just 19 pages. Over the years, I've met many Scrum practitioners who have never read the Scrum Guide or they have read it once and once only. I believe there's something special about the Scrum Guide and because of this, it's important that we consider reading the Scrum Guide as an empirical process itself.

When practicing the guitar, there have been times when I got very demotivated and frustrated until I found out I was focusing on my mistakes instead of enjoying all the good licks I was producing on my guitar as well. I learned that focusing on the good things I play makes practicing the guitar much more enjoyable.

In working in today’s knowledge work economy, it surprises me that many leaders still use traditional ways of leading their people. Leaders still put most of the focus on the work to be done instead of focusing on the people to create an environment where great work can be done.

A couple of months ago I blogged about some of the tools and toys that live in the trunk of my car. I take these along everywhere I teach and coach. Since posting, people have suggested additional items that just must be in my toolbox.

In the past years I’ve been the king of procrastination... there's a way to reduce anxiety by thinking differently, this article explains my way of doing it.

Now that we’ve covered the essentials of self-organization and intrinsic motivation, let’s dive into how you make decisions that enable and empower others.

The year 2018 was about amplifying. Amplifying my message, thoughts, ideas, inspiration and passion. My energy and stamina are not what it once was. The journey ahead of me is smaller than the one behind me.

About 40 people gathered at the nlScrum meetup dedicated to physical and digital tools for the agile workspace. Tools that help developers, coaches and trainers to survive in the toughest environments.

A few days back I did a Scrum Tapas Video explaining a few of the rules within Scrum. Besides these rules, there are also certain guidelines which help Scrum Teams to make the best possible use of Scrum framework to create maximum Business Impact.

The Scrum framework deliberately leaves the manager role out, thus allowing business to structure and organize how it sees fit. 

As an agile coach and trainer, I have had the opportunity to reach thousands of students that are just beginning their journey into the Scrum and agile world.

Once you have started to create a strong foundation, the second action of an effective servant-leader is to empower and enable others.

The Development Team is both self-organizing and cross-functional and by the end of each Sprint provides an increment that is ‘done’ and releasable. The team defines how to organize work in a Sprint.

This is the truth. If we turn things upside down organizations can't truly embrace Agility. I would be lying if I said that we can improve our product delivery process even more. A small poem about Agility & Scrum

Most organizations are using Scrum, however, many of them feel like the agility of their organization has degraded, and they might be right! Often, using Scrum starts out as a way to improve development efforts coordinated within an IT division or department, but that is not the most effective organization structure to potentially get maximum benefit from Scrum.

Does a Scrum Master really need technical business knowledge? If you’re trying to break in the world of Scrum, you might be asking yourself: Does a Scrum Master really need technical knowledge? Do they need business knowledge? I’m here to set the record straight.

Servant-leaders must create a strong foundation that helps people feel empowered to take action, enables them to move forward in a common direction despite uncertainty, and to feel inspired and resourceful during challenging times.  The 4 V’s can help you establish this strong foundation:  Vision, Values, Value, Validation.

Many Agile coaches and Scrum Masters believe they know best. They believe teams must follow a certain set of steps and do things a certain way, and if they do, those teams will be more productive, happy, and successful than ever.

Hello great people of the world. It’s been a while since I wrote a blog post here. This time I want to share my experience working with Development Teams and a Product Owner at iPrice group who upgraded the way they ran their Sprint Planning.

When I work with my clients on Scrum in a Marketing context the discussion about the Marketing Backlog and how to move from a big bang marketing campaign to a more iterative approach via smaller slices of stories is naturally a key area we focus on. 

A short story illustrating how fear cripples estimating and how empathy can come to the rescue.

Scrum is based on self-managed teams. Self-managed teams are able to evolve and adapt quicker in today’s highly complex working environments than traditional command-and-control management structures.

At one point or another in our lives we have all experienced a long queue, stuck in a car on the motorway, sat on a train waiting for an open platform. My favorite memories stretch back to that line for the lunch at primary school where it was cake and custard day!

In Scrum, “Done” doesn’t support adjectives like “nearly”, “pretty much” or “almost”. Work is “Done” or it isn’t . And there is a very powerful, compelling reason behind this: the Scrum Framework only helps to reduce the risk of wasting money and effort when you deliver “Done” software every Sprint; a new version of your product that is, or with the proverbial press of a button can be, released to users. In this post I underscore how essential this rule is to Scrum.

Photography may sound simple but is actually a problem of complex domain. There are many variables - light, subject, motion, distance, composition, framing -  that come into play while capturing an image.

I’ve been in a situation a few times where I’ve interviewed a candidate for a role. I’ve matched their CV to a well-prepared job specification...