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.

Coaching conversations typically occur in a “zone of comfortable debate.”. However, to deal with issues at their core, it’s important to enter the ZOUD: the “Zone of Uncomfortable Debate.”

“Scrum begins with Done”. The assertion might seem counter-intuitive, as though we must start by defining the end.

"It's not always easy to be a good Scrum Master. Learn some common pitfalls of Scrum Masters, and to recover from them, or avoid them altogether."

Muchas veces sucede que la comunicación no es clara cuando se quiere definir que es terminado. Por ejemplo, cuándo un usuario especifica que requiere un reporte con cuatro columnas y que la última columna tenga un total parece algo sencillo.

We talk about coaching a lot in the agile world. However, what we are actually expected to do is not usually about coaching.  We do other things.

We find this a common thread amongst our customer teams, which can be attributed to a lack of backlog refinement.

"It's not our fault! The Product Owner is responsible for backlog management, the PBIs aren't well defined."

The previous weeks I've taken some time to re-write the white paper "The 8 Stances of a Scrum Master". Given my sessions at Scrum Day London, Scrum Day Warsaw and Scrum Day Europe I wanted to offer the participants a paper with my latest insights and lessons learned. In this blog post I'll share the changes in this 2nd edition.

Recently I had the opportunity to give a guest lecture about "Agile Essentials" at a University of Applied Science. These students, the lecturer told me beforehand, would only be partly interested and engaged.

Does this headline make you cringe or cheer? Scrum.org’s Steve Porter and ActionableAgile’s Daniel Vacanti weigh in on whether we should blend these two approaches.

In one of my previous blog articles, I wrote about the Scrum Master journey through the different levels of influence to achieve greatness. In this blog, we will explore the number one skill I believe is needed for a Scrum Master (servant leader) to be effective in order to create change and impact a Scrum team and organization.

Agility is important to an organization and the path to agility becomes more clear by understanding the purpose of pursuing agility. The product owner role is key in increasing the benefits an organization can gain in their path to agility.

Do you ever wonder what determines our actions? Most people think that what we do is the outcome of our personality, however, the truth is more straightforward. It’s our mindset that controls our behavior. 

When talking about Scrum, people often imagine the picture above: framework and its roles, artifacts, and events. Scrum rules are fairly simple, and they are thoroughly described in the Scrum Guide.

“Do not accustom yourself to consider debt only as an inconvenience; you will find it a calamity” - Samuel Johnson

"As remote teams become more and more common, Scrum Masters must find a way to effectively do Scrum while working with far flung team members."

Most of the organizational change initiatives focus on the "hard" aspects such as organizational design, process or tools. Although those are critical, often other "soft" aspects such as values, principles or culture are overlooked. As the iceberg metaphor: consider them or they may sink yout Scrum adoption!

How Much Software Inventory Do You Have? When I ask this question of people in IT departments, even among senior managers and finance people, I get a variety of responses.

Leadership is developed, not discovered (I have found inspiration in John C. Maxwell's various books).  John defines leadership as influence, and a good Scrum Master has to climb the different levels of influence to achieve a good to great mindset.

Respect is essential in solving complex problems and growing high performing teams.  This likely seems obvious, so I am going to share some of the more subtle examples of the value of respect in Scrum.

I am sharing the learnings from my recently read books which helped me improve my listening skills. Inspired by one of the tools from the Book "People Tools" by Alan C Fox  here is the first Tool/Tactic for Scrum Masters.

Many times, clients ask Agile Coaches like me to come in and share our "expertise" with them. But sometimes they really don't want our "Expertise". What they really want is someone with lots of TLA's to come and tell them that there pre-existing opinions are correct.

Sometime back I read a short SciFi story in a book named People Tools, Story was about a spaceship conducting man’s third ten year ex