Here are the slides for this webcast.

Hear why SearchSoftwareQuality author Valerie Silverthorne says that Dave West, CEO of Scrum.org is the perfect person to talk with when you feel the sky is falling. 

I am listing out some commonly observed Scrum Myths, Mysteries, and Misconceptions from my experience.

Scrum.org founder and co-creator of Scrum, Ken Schwaber named as a BBJ Innovation All-Star Lifetime Achievement Honoree.

UNFLATTERING WISDOM OF HIND SIGHT

Improving Consistency of Scrum Training Around the World by Connecting Training Companies with Premium Training from the Scrum.org Professional Scrum Trainer (PST) Community

Agile implementations may be disappointing due to failure to limit risk, long lead times, consistent cost-overruns, and the fact that no one knows why you do what you do.

SCRUM IS NOT THE END. IT IS A MEANS TO THE END… The end goal of empirically building strong, self-organizing Scrum Teams to help your business…

The Nexus Integration Team (NIT) is a new role that is essential within the Nexus™ framework. It is a role that is performed by a team of people. As described in the Nexus Guide, “the Nexus Integration Team exists to coordinate, coach, and supervise the application of Nexus and the operation of Scrum so the best outcomes are derived.”

Scrum.org CEO, Dave West takes a look at the role of the Product Owner and how they can look at delivering Roadmaps and Plans in agile environments.

Are people not really challenging each other in your Retrospecitives? Are the burning issues not discussed? Learn how to turn that around in this article.

I see four common reasons an agile implementation doesn't get the benefits hoped for. These reasons include a failure to limit risk, long end-to-end delivery lead times, consistent cost-overruns, and no one knows why you do what you do.

This week I got a question from a colleague about the Scrum Retrospective. She's Scrum Master of a team that for sure has room for improvement.

Why does the software industry act differently from many other industries where a code of ethics isn't required to act "professionally"? Read more to learn how some of our PSTs think this should change.

In the Professional Scrum Product Owner course, we teach that high performing Product Owners are entrepreneurial. They not only act with the business in mind, they have the authority to make important decisions. What should we do now versus later?

Watch our international panel of Professional Scrum Trainers, as they share ethical challenges they have seen software delivery teams face in the real world and learn about an interesting approach your teams might use to tackle these challenges.

 

A small software shop within a government organization where multiple Scrum Teams are serving the same cause is building one product that has several sub-systems. Sometimes, those sub-systems need to be integrated.

You hear a lot in Agile circles these days about the ‘declining need for managers.’ We may not need the managers of yesterday but, make no mistake, we certainly need the leaders of tomorrow.

The Daily Scrum, or most of the time referred to as  the "stand up." Probably the most well-known event when we talk about Scrum.

Organizations who don’t understand why they want to become Agile also often take the wrong path to get there. Agility requires empowering teams and helping them make decisions on their own, learning from their experiences as they go.

Large Office Expansion Enables Organization Dedicated to Helping Improve the Profession of Software Delivery to Accommodate Larger Numbers of Students in its Professional Scrum Training Courses

Birthdays are a great time for reflecting on the past and looking to the future. So, what is coming up on the horizon for Scrum?

The article contains my PST Barry Overeem's experiences as a Scrum Master and includes my most important findings while researching the 8 different stances by studying books, articles, and videos.

In this edition of Hey Coach, PST Philippe Sauve looks at teams and the complex environment around us. This time we shall discuss the not-too-controversial topic of keeping track of work.

I’m currently helping a small software shop within a government organization where multiple Scrum Teams are serving the same cause. They are building one product that has several sub-systems, which sometimes need to be integrated.

This is the original paper on Scrum, based on the presentation at OOPSLA 1995 where the concept of Scrum was initially introduced.

Scrum.org CEO, Dave West takes a look at how Scrum can be used in the DevOps world, addresses often heard concerns that they conflict and gives guidance on how to overcome those concerns.

This poster represents the Nexus Framework as developed and designed by Ken Schwaber, the co-creator of Scrum.

ScrumButs are reasons why teams can’t take full advantage of Scrum to solve their problems and realize the full benefits of product development using Scrum. Every Scrum role, rule, and timebox is designed to provide the desired benefits and address predictable recurring problems.

According to the Scrum Guide, 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.

I’ve spent a lot of time looking at how organizations are using DevOps to improve their software delivery cycle time, their ability to innovate, and their ability to improve quality.

In this session, Karel Deman, global agile lead at Avanade, and Patricia Kong, who leads the Scrum.org scaling initiative, will describe how Avanade improved their organizational agility. They will also share the successes and challenges Avanade faced in scaling ability across the enterprise to best deliver solutions to their clients using Scrum and agile practices.

This summer, during the Olympics, the Euro Soccer Championships and the Tour the France, while cheering  in front of the tv, I noticed something in the way teams perform. And it worried me.

Agile approaches, including Scrum, are empirical approaches to delivering software and business value.

The Nexus Sprint Backlog is created during Nexus Sprint Planning. It is a visualization of the work across the Nexus that has dependencies. The purpose of Nexus Sprint Planning is to coordinate the activities of all Scrum Teams in a Nexus for a single Sprint. Read more to see what Professional Scrum Trainer Rob Maher and Scrum.org Product Owner for Enterprise Solutions Patricia Kong have to say.

On July 7th the Scrum community gathered in Amsterdam (The Netherlands) for the 5th edition of Scrum Day Europe. This year's theme was 'the next iteration'.

In this Scrum Pulse session, our PST panel will share their experiences, challenges and insights from guiding the effective adoption of Scrum in multi-cultural Scrum.

Throughout the Agile Alliance 2016 conference, I was struck by a recurring feeling that many people don’t understand what the Sprint Review is.

More and more large companies in traditional industries are singing the Agile song. I have noticed, though, that there seems to be a general misconception that Agile is onlyabout creating happy teams.

Download this datasheet to learn more about the Applying Professional Scrum for Software Development training class.

Download this datasheet to learn more about the Professional Scrum Product Owner training.

Download this datasheet to learn more about the Scaled Professional Scrum training.

This document provides an overview of the different Scrum.org training classes that are offered by our Professional Scrum Trainers around the world.

This document provides and overview of the different Scrum.org certification assessments that are available. These Professional Scrum assessments come with the industry recognized Professional Scrum certification for those who pass.  

Download this datasheet to learn more about the Professional Scrum Master (PSM) training class.

An overview of documents and books to help understand the role of the Product Owner organized by assessment categories.

An overview of documents and books to help understand the accountabilities of Developers on a Scrum Team working in the Software Delivery domain organized by assessment categories.