The Scrum Master is responsible for ensuring Scrum is understood and enacted. Scrum Masters do this by ensuring that the Scrum Team adheres to Scrum theory, practices, and rules. 
The Scrum Master is a servant-leader for the Scrum Team. The Scrum Master helps those outside the Scrum Team understand which of their interactions with the Scrum Team are helpful and which aren’t. The Scrum Master helps everyone change these interactions to maximize the value created by the Scrum Team.

Uncover the power of Kanban boards to visualize, manage, and optimize your workflow. This comprehensive guide will empower you to create effective Kanban boards, track progress, and achieve peak productivity.

Story points are a unit of measure for expressing an estimate of the effort required to fully implement a product backlog item or any other piece of work.

Become a Cucumber expert at your own pace with free online courses. Attend interactive in-person training, tailored for your needs. Learn more and get started.

The three major exam providers in comparison: Here you will find all the advantages and disadvantages at a glance! Which Scrum certification is suitable for whom?

From the Blog…

Many companies are using Scrum, however some struggle with achieving really effective teams. When teams feel the pressure from the business and Product Owner, look at all the work they have to do, and how much time they have to do it, working on improvements seems unimportant.

The sprint retrospective meeting in Scrum is a time for the team to reflect on how they're doing and find ways to improve.

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.

**Summary**: A meeting to prepare for the Sprint, typically divided into two parts (part one is “what” and part two is “how”). **Participants**: Part O...

I'm currently the Scrum Master of a 10 developer strong team. We've adopted Agile/Scrum methodologies for some time now and are currently on our 53rd Sprint. Our stakeholders actively like to understand the output of story points in advance of a Sprint. This is currently done on a capacity basis working on a focus factor of 60%.

Choosing the right iteration length is an important decision. These are important factors you should consider when selecting your team's iteration length.

I read a lot about the planning onion related to Agile environment.  Here at my office, I use the planning onion to effectively show the layers of responsibility that help us to get things don…

Learn from our scrum experts on how to create a good definition of Done and why it’s so critical in ensuring incremental improvement in product development.

There’s a saying in the music industry that the easiest way to ruin a song is to keep working on it. Add enough effects, extra guitar parts, or more cowbell, and you’ll turn Woody Guthrie into Guns N’ Roses. Knowing when a piece of art is “done” is subjective and often difficult to define. But...

And what to do when these questions don’t really help

Scrum teams estimate both product backlog items and sprint user stories--but in distinct units and at separate times.

Fibonacci agile estimation quantifies the effort needed to complete a development task. Learn how to employ this method in your agile process.

Free scrum guide for agile scrum team. Learn about how agile estimation can be performed. More free scrum resources are available.

Discover agile estimation principles & planning methods for project success. Dive into uncertainty, valuable estimates & agile delivery processes.

From its origins to its significance, almost every popular notion about the famous Fibonacci sequence is wrong.

The planning fallacy is a phenomenon in which predictions about how much time will be needed to complete a future task display an optimism bias and underestimate the time needed. This phenomenon sometimes occurs regardless of the individual's knowledge that past tasks of a similar nature have taken longer to complete than generally planned. The bias affects predictions only about one's own tasks. On the other hand, when outside observers predict task completion times, they tend to exhibit a pessimistic bias, overestimating the time needed. The planning fallacy involves estimates of task completion times more optimistic than those encountered in similar projects in the past.

Precision and accuracy in chronostratigraphy is very important when considering the age of moraines and other features in glacial geology!

Disclaimer: The content in this article is a mix from the references linked below and my personal experience. It is not meant to be an…

A good leader keeps everything in order. In this fast-paced era where agile methodologies have become a more often used framework, a good Scrum Master is what is needed. But what makes a good Scrum Master?

Discover 6 qualities of effective Scrum Masters, plus a bonus trait to help teams reach optimal performance.

In software development, a lot of terms are thrown around for how teams should be managed. Whether we say self-managed teams, self-directed teams, or self-organized teams, what does this mean?This can mean many things depending on the organization. First, let’s cover a basic definition from the interwebs:

In this Executive Update, we discuss why IT professionals must become more T-shaped, what it means to be more T-shaped, and how mid-career technology professionals need to continue to grow in their career in order to thrive in this rapidly changing world. We will also discuss how an executive understanding of this concept can be incorporated into business today to drive greater flexibility and value in the future.

What exactly is a self-organizing team? How do you create one, and why is having one is important to creating an Agile environment? Let's take a look.