Resources

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.

Agile practices rely on empiricism for the best solution to emerge. But what is ‘empiricism,’ anyway? And how does that affect the development of the optimum product? In this session, Professional Scrum Trainer Mark Noneman looks at what it takes to be a Product Owner who practices empiricism. 

In their first attempt at attaining agility, Intralinks took a well-intentioned “mechanical” implementation of Scrum - done in good faith and with lots of hard work - but failed to deliver against their goal of greater agility. So, they took on a “Scrum Reboot” and succeeded by augmenting the mechanics of Scrum with the fundamental idea of inspection and adaptation and the Scrum Values of Courage, Focus, Openness, Respect and Commitment.

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.

I was speaking at a conference recently, and during the Q&A an audience member asked a question that I hear a lot: what should an Agile organization measure, and where should they start? My answer: start by measuring customer outcomes.

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:

Are you ready to get your Scrum effort underway, but your company won't fund it until you have a detailed business plan outlining the exact results and all the people, resources and other needs it will take to get them?  

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.

In 2016, a leading security products company adopted Scrum to support teams working in complex product development, in order to make the organization more adaptive and able to react faster to change. It began with one Scrum Team of IT developers focused on mobile applications.

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.

Many organizations find themselves faced with the challenge of making distributed agile work. Mergers and market consolidation, geographic expansion, and offshoring have made multi-site development the norm rather than the exception. Companies with sites in competitive labor markets can find distributed team members as an alternative when they can’t recruit locally.

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.

Any agile certification that doesn't require candidates to have some kind of hands-on, practical training or testing is detrimental, not just for the candidates, but for organizations that hire them and for the software development field in general, says Dave West, product owner at Scrum.org, which provides professional assessments, training in scrum and agile principles and certifications.

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.

Scrum is an overall approach to problem solving that avoids strict specifics versus a rigid, step-by-step set of instructions, according to Eric Naiburg, Vice President of Marketing at Scrum.org. Because teams, people, and projects change and evolve over time, “ having a single way to do something just doesn’t enable growth,” Naiburg says. Simply put: Scrum is the opposite of a to-do list—instead, it’s a way of approaching group projects with flexibility.

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 (Sergey Br

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.

In this article, the author gives a brief overview of Scrum and what it contains.  Although he may have deviated slightly from the Scrum Guide, he insights are helpful to learn from and read. You can also learn more about Scrum in our What is Scrum section of this website.

Although Scrum has been around for more than 21 years, and is practiced by more than an estimated 18 million people around the world, we are always learning. In this webinar, learn some of the basics of Scrum and how to apply them.

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.

Find the books written by our Professional Scrum Trainers to help you learn more about Scrum and Agile.

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 than by the e

Learn how to Maximize the value delivered by a combination of internal and external Scrum Team members as we walk through the steps of creating a client-agency partnership using Scrum with Scrum.Org and Blue Coda.

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.

In this edition of ScrumPulse, Hiren Doshi, Scrum.org Trainer and Coach talks through his practical experience leading numerous Agile Transformations for clients like Tesco, BookMyShow, DELL EMC, Bank of America, Sabre Travels, etc. on what it takes to be an effective Scrum Coach.

As part of the Scrum Tapas video series, Professional Scrum Trainer Robert Pieper talks about how Gantt Charts and Burn-Down Charts are often used to manage agile projects, why they are fundamentally different ways of measuring progress toward a release and best ways to measure that progress. 3:29 Minutes

Many organizations face two key risks in their adoption of Scrum: TACTICAL SCRUM and DEATH BY MANDATE. In this special ScrumPulse Double Header, Professional Scrum Trainer Ravi Verma breaks the conversation into two parts to managing risk.

As part of the Scrum Tapas video series, Professional Scrum Trainer Stephanie Ockerman explores the myth that a Daily Scrum is status meeting.  Through her discussion, she dives into several areas as to why it the Daily Scrum is much more than a status meeting and how they differ.  6:29 Minutes