En su reciente reporte anual, LinkedIn ha considerado el de Scrum Master como uno de los trabajos con más futuro del 2017. Con un salario medio anual de 100.000$, el número de puestos disponibles para Scrum Masters está previsto que se duplique este año.

I want to address those of you who don't really want the feedback. I mean, as important as feedback is, and as many times as you've heard that the central point of a Sprint Review is feedback…you're tired of it. It's pesky. And it just gets in the way of you doing what you know is right anyway.

'Scrum isn't perfect' is something I hear quite frequently, be it as an excuse not to stick to the few rules Scrum has or not to use it at all. The thing is though that no set of rules is perfect, but we're used to stick to them anyway.

I recently had the pleasure of conducting Scrum.org’s Professional Scrum Foundations workshop to a group of students at the nonprofit job-training program, Year Up, in Boston. Teaching this group of millennials -- motivated, talented young adults from low-income background -- was an illuminating experience that ended up teaching me something about being a Scrum trainer as well as the future of software development.  

La velocidad es uno de los temas de Scrum más discutidos online y offline. Sólo hace falta acercarse a la comunidad de Scrum Masters en Facebook para comprobar como muchas de las cuestiones planteadas están en la linea de la velocidad de entrega de los equipos de desarrollo de Software.

El Sprint Backlog suele generar bastantes dudas en cuanto a su gestión. En ocasiones se convierte en un arma arromadiza que los stakeholders, el Producto Owner o incluso el Scrum Master utilizan para controlar el equipo. ¿Es esta su función?

In Scrum, the Product Owner is an entrepreneur and the mini-CEO of a product, who is able to make fast decisions. The success of the Scrum Team and company as a whole depends on whether the Product Owner is real.

This blog post will be about the question "Should a Scrum Master be technical?". I'll describe my personal journey, share some opinions of other experiences and give you some examples of Technical Scrum Masters I've worked with.

Comme dit le dicton ce n'est pas la destination, mais la route qui compte. On pourrait dire la même chose pour DevOps et de son implantation dans une organisation. Oui, le résultat est magique puisqu'il vise à nous faire livrer quotidiennement de la valeur d'affaires, mais le périple l'est d'autant plus. Ce périple est rempli de découvertes organisationnelles, technologies, mais surtout humaines.

Most of the Agile transformations I have witnessed have started like this: First, a company raises a strategic initiative on so-called Agile implementation. A large budget is allocated and a tender is arranged to purchase Agile coaching services from companies on the market. Then employees are trained, and the pilot teams start working. However, they immediately stall, because there is lots of tension between them and an old cultural landscape.

“The secret of success is to be ready when your opportunity comes” - Benjamin Disraeli  

I hear it all the time. Whether it is a consulting engagement or in a Professional Scrum Course, the desire to modify Scrum comes up frequently.

People don't always think of Scrum Teams handling customer needs. But, for a Scrum Team to have success understanding the customer is key.

This blog post will focus on how to get started and succeed with Zombie-Scrum. What do you really need to have in place? What are the tips & tricks to give your Zombie-Scrum implementation a kick-start? How to make it sustainable? This article will offer you some nice recommendations.

Just as teams benefit from diverse, multi-functional teams, at the macro-level organizations can benefit from diverse practices such as systems thinking, design thinking, Lean practices and Agile.

After experiencing my fair share of frustrating Sprint Review moments, I want to share some tips to improve the feedback you receive.

Some companies develop 1 product with 10s to 100s of people using Scrum. And they do that without adding any roles, events or processes to Scrum. They can do this because they use an organisational design that optimises for the right goals.

I have read in several Lean and DevOps sources that the Sprint events imply a kind of waste, so teams are supposed to move to a Continuous Delivery or Kanban lifecycle as they become mature.

In this blog post I'll share my view on the question "What is a Scrum Master actually doing during the day?" I will use different sources and perspectives to answer this question and clarify the title and describe a day in the life of a Scrum Master.

In part 1 of this blog, we looked at what software inventory is and why it's problematic for business.

Scrum is often called the art of the possible. This means we do the best we can with what we

This blog post will be about the question: can you rotate the Scrum Master role? With rotating the Scrum Master role I mean frequently changing the person fulfilling this role.

The Sprint Goal is an important part of Scrum. It's like a burning torch that unites the Development Team and helps it move forward during the Sprint.

The truth is, worrying about velocity is a trap: it says “we don’t care where we end up, so long as we get there fast.” That’s just wrong. Teams who measure their velocity but don’t or can’t measure customer outcomes may, quite simply, be driving in the wrong direction.

In this blog post I'll share my view on the question: Can you be a part-time Scrum Master?

Check out this job advertisement:

True story - happened in one of my recent Professional Scrum Master workshops. I think had just mentioned that there is no "Sprint Commitment" in Scrum, only a "Sprint Forecast".

Like many old, boring people, my favorite radio channel in the car is National Public Radio. Since I live in Dallas, TX, my local channel is KERA. Of all the shows in KERA, my favorite is a show called Think With Krys Boyd. Almost each show I listen to leaves an imprint on my mind and modifies the way I think.

The role of the Scrum Product Owner is probably the most misunderstood of the three Scrum Roles. As I look back at the different incarnations and interpretations I have seen of Product Ownership, I thought it was time to articulate the different stances I thought an Effective and Professional Scrum Product Owner might consider.

Several of us in the Kanban and Scrum community got together recently to build a bridge between Scrum and Kanban. We are writing a series of blog posts looking at this bridge from different perspectives. In this post, we present a primer on the Scrum Framework from a Kanban perspective.

Having been part of this recent activity, allow me to share with you my personal account of my first Global Face-to-Face meeting with the Trainers Community.

Although I’m generally considered to be a strong leader with the people I am privileged to serve, I am still susceptible to making mistakes.

Are you ready to escape the average and become awesome? Do you want to overcome your fears and follow your dreams? 

Pour avoir un aperçu de la perception et compréhension des personnes de quelque chose, il suffit de regarder les réseaux sociaux.

To get an insight into people's perception and understanding of something, just look at the social networks.

"Coming together is a beginning, keeping together is progress, working together is success." - Henry Ford  What do the Ford Motor company (Henry Ford, Clarence Avery, Peter Martin, Charles Sorensen), the Google team (Serg

Recently I attended training on Nexus at Scrum.org’s Boston headquarters. Nexus is based on the core principles and values of Scrum and allows companies to apply Scrum at scale while retaining the bottom-up intelligence of self-organisation.

One of the most important things to understand in modern business (and quite possibly life in general) is the concept of complexity. While we use the words complicated and complex almost interchangeable in everyday language, they mean very different things. Let’s explore my favourite model on complexity called Cynefin.

I work with a lot of companies that are learning to use Scrum as a tool for agility driver. Recently, I spotted a trend: if a Scrum Team cannot articulate their Sprint Goal, the problem quite often lies with the Product Backlog.

Ah, the Daily Scrum, so often misused as an instrument of status (see https://youtu.be/i7_RPceEIYE for a discussion). Often the way the Daily Scrum is conducted lends itself to a report of status.

We always hear athletes talking about being 'in the zone.' But you don't have to be LeBron James to feel this type of hyper-focus. Learn how Scrum teams can harness it.

Several of us in the Kanban and Scrum community got together recently to build a bridge between Scrum and Kanban. We are writing a series of blog posts looking at this bridge from different perspectives.

What makes a great team? Why do some teams achieve greatness, seeing their vision become reality, while others seem to go nowhere?

Exploring the accountabilities in a Scrum Team through a Longship metaphor.

If agility is why your organization adopts Scrum, look for more sophistication in employing Scrum. Through Scrum, teams and organizations create the opportunity of having a releasable version of product no later tha

What makes the software development work great? Obviously, technology, right... Wrong! In an interesting article in "Peopleware", authors Tom and Timothy describe how the most important aspect of software development is not technology, but people.

What is the difference between a traditional and an Agile Manager? Keep reading, if you want to learn how a manager evolves.

Have you ever sat on a bus or plane, and rather than offering the vacant seat next to you to others, you hope that no one takes it, so you might have more space.

Congratulations! You replied to the job advert for an agile position, and you’ve got an interview. Genuinely keen to work in an agile way, you know that the organization must have picked up on your credentials.

Many of those practicing Scrum mistakenly call the Sprint Review a Demo. Is it just a matter of terminology? From my point of view, the Sprint Review is the most underestimated Scrum Event, and for many companies, its potential is yet to be revealed. It is true that the Demonstration or Demo is an essential part of the Sprint Review, but it isn't the only one.