"Simply the best Scrum course I have attended so far"

★★★★★
4.9 out of 5 (89 Reviews)

The Essential Companion For Solving Scrum Problems

The Scrum Repair Guide is the first online video course to go beyond basics and deal with the challenges you’ll inevitably experience.

By using this guide, when you do face a challenge using Scrum, you’ll know how to fix it.

That means you no longer have to work through problems on your own, or struggle with the time-wasting process of trial and error. The Scrum Repair Guide gets you back on track so you can focus on the very reason for using Scrum: shipping high-quality products with maximum speed and efficiency.

Whether you’re a new or seasoned Scrum practitioner, this course will help you:

Pinpoint problems quickly and find solutions before productivity is at risk.

Why Too Many Teams Struggle with Scrum

Scrum is a proven to decrease time-to-market, increase quality and keep customers happy... but adapting it to your organization and team can be difficult.

In an ideal world, you’d train your teams on Scrum and things would just work.

But that rarely (if ever) happens. In reality, many Scrum practitioners face:

Unrealistic (yet forceful) stakeholder demands.

Team members that focus on ‘individual progress’ to the detriment of the team.

Confusion and delays from a chaotic product backlog.

The inability to catch your breath and actually find time to solve problems as they occur.

What’s more, despite a mountain of resources for how to get started with Scrum, few address this key challenge:

Every Scrum team and organization is unique.

Which means:

You Need to Adapt Scrum to Your Unique Needs
(WITHOUT Making This Mistake…)

Many teams that hit a few bumps in the road after using Scrum, decide to adopt the following practice (mistakenly so):

They assume that because they’re experiencing problems, Scrum perhaps needs modifying to suit their particular needs.

And so they start to reject certain rules of Scrum and change the framework, bit-by-bit. For example:

Team members complain that sprints aren’t sustainable back-to-back, they’re burnt out - so the Scrum Master introduces a gap week to catch-up.

A testing backlog is building up during the sprint - so the team decides to separate testing and development sprints.

These things won’t work

Changing the fundamental principles of Scrum will only make things more difficult in the long term.

You need to know how to solve problems in a way that works best for the unique needs of your organization, without compromising what makes Scrum so effective.

That’s not easy.

Fortunately, the Scrum Repair Guide shows you how.

This course goes much further than just treating basics. It really deals with well-known problems probably every Scrum Master and/or Scrum Coach experiences. Mike always offers several solutions considering different circumstances introducing appropriate examples as well. With his extensive knowledge of all parts of agility he convinces and encourages me to try out his hints without hesitation. I really like the length of the videos, all necessary is said and all unnecessary is omitted. The content is really absolutely substantial, interesting and helpful. I recommend this course to every practising SM and agile Coach.

Eva Gysling

Why The Scrum Repair Guide Works

Nearly 1,000 students have signed-up for, and benefited from this course. Like them, you’ll get instant and lifetime access to the online video course comprising seven modules (see below for details of each module).

Each module contains advice to identify and solve the problems that threaten your Scrum projects. And with videos between 2-11 minutes, you can learn when it suits your schedule.

Most of all, The Scrum Repair Guide works because you get:

Real-world recommendations The content is based on what Mike has seen work for hundreds of Scrum teams.

Adaptable guidance You often get several solutions to try depending on different circumstances.

Multiple recipes For handling complex and delicate situations.

Help with cultural change Sometimes it’s not the rules that are the problem, it’s getting people to stick to them.

Practical advice Right down to specific actions, exercises and even the words you should use to solve problems.

Mike has this rare ability of examining complex situations with a lot of gray areas and presenting them with sound recommendations and without any nonsense in simple black and white. Thank you Mike.

Hector Rovira

What You'll Learn:

Module 1: The Product Backlog

A well-organized product backlog lets a team start strong at the beginning of each sprint. But it can become messy and chaotic, costing the team valuable time. In this module, you’ll see how to:

Keep the product backlog up-to-date so the team doesn’t waste time during the sprint searching for key information.

Remove resistance from a product owner who is reluctant to allow technical work within a sprint .

Increase your chances of delivering a potentially shippable product by choosing the right number of product backlog items for the size of your team.

Module 2: Estimating and Planning

Without useful estimates, stakeholders can’t make long term projections and product owners risk making mistakes when prioritizing product backlog items. Even if your team is reluctant to make estimates, this module will show you how to:

Make developers feel safe about estimating (so they don’t try and sabotage results).

Build the credibility and respect for a team through a series of accurate estimates. This helps stakeholders listen In the future, if the team says something can’t be done.

Master communicating estimates so that stakeholders are happy and the team doesn’t feel pressured.

Use the ‘no partial credit rule’ to encourage the team to perform better (even if they try to fight it).

Module 3: Sprinting

Many frustrating challenges can derail even an experienced team during a sprint. Fortunately, you’ll have the Scrum Repair Guide, so you can:

Identify the tell-tale symptoms of a sprint that is too short (or too long) and how to fix it.

Understand the top 5 reasons teams under-deliver, and how to avoid this.

Make sure your team doesn’t misinterpret ‘potentially shippable’ and think a sprint will fail when it can actually be saved.

Stop sprints becoming meaningless milestones when work is left unfinished at the end of a sprint.

Module 4: Problems During Meetings

Meetings are a common source of wasted time and team frustration. This module tackles this head on and shows you:

Why the “2 hours per week of the sprint” advice isn’t always the right length for the sprint planning meeting.

Why a team shouldn’t think of every task in the sprint planning meeting and how many tasks they should actually identify.

How to use the sprint planning meeting to stop the worst habit of all: failing to deliver

3 ways to have a successful sprint review if you have functionality that you can’t demonstrate.

Module 5: Stakeholders

Keeping stakeholders and the team happy can be difficult, but there are ways to handle requests diplomatically without sacrificing the flexibility and morale of the team. In this module we’ll dive into:

How to use project success sliders to get a meaningful discussion about (true) stakeholder priorities.

3 great questions for stakeholders that give you flexibility on scope schedule and cost.

Why a one-handed clock is a powerful illustration to make stakeholders clear about what is flexible, and what is non-negotiable.

How to really move from documentation to discussion, by proving which documents are truly necessary.

Module 6: Teamwork

Ideally everyone should be working not just in the team but for the team. As you know, this doesn’t always happen. This module shows you how to:

Get team members to focus on group throughput rather than individual productivity.

Encourage team members to work outside their role (and understand when this won’t work).

Have team members do smaller handoffs earlier, so that testing isn’t left until the last few days.

Support an overly busy product owner so that you can get their input when you need it.

Module 7: Culture

Scrum should create a positive working environment, but a misunderstanding of Scrum rules can put pressure on the team and create resistance. See how to prevent this and learn how to:

Use 3 ways to work at a sustainable pace and eliminate burnout.

Understand exactly why separating sprints for testing and programming is a bad idea.

Quantify risk so that you can estimate it more accurately.

Choose 4 different ways to reward a team (and understand which incentive is the most damaging to motivation).

Bonus: Discussion Area

As a member you also get access to a discussion area about the course. Have a specific question about any of the videos or applying them to your situation? Post it here, and receive the answer you need to get moving again.

This course was absolutely packed with tips, advice, and best practices for both avoiding and resolving issues that occur in using Scrum. I probably checked off a dozen or more issues that I personally experienced over the past 4-5 years that I’d have paid big money for to have the insights that Mike provided in this course. This was by far the most practical, useful course on Scrum I’ve ever taken. I plan to review this course over again as there is just so much useful stuff.

Gregory Luze

About Mike Cohn

Learn scrum and agile processes directly from Mike Cohn, one of the industry's most well respected Certified Scrum Trainers (CST). Mike Cohn is the author of User Stories Applied for Agile Software Development, Agile Estimating and Planning, and Succeeding with Agile. He is a co-founder and former board member of the Scrum Alliance, and a co-founder of the non-profit Agile Alliance, home of the Agile Manifesto. Mike is also the founder of FrontRowAgile.com, an online agile training website.

Choose How You Want to Learn

Buy a Streaming-Only License

Streaming licenses are valid for one person, enabling them to stream the video course as many times as desired.