Rationale for Scrum Teams

Agile Scrum scrum master Scrum team

Rationale for Scrum Teams: to improve the speed, quality, and value of work in order to make work fun and fast.

Rationale for Scrum Teams

Scrum teams 

  • Speed up work
  • Improve happiness
  • Improve quality
  • Generate more revenue with less waste 
What is the rationale for Scrum Teams, better teams

Let's dive into the full story

Level up your agile and get professional training.

Scrum Master Certification

Before you go too far into this tutorial, it might be worth heading over to our most popular post, What Is Scrum where you can learn everything you need to now about Scrum fast. 

If you want to learn about why you should consider Scrum Teams, just keep reading.

Rationale for Scrum Teams, the big idea

Work is hard.  People are hard.  Doing work with people is really hard for all of the reasons you already know.  

There is also a related post to this post you might want to checkout it explains the rational for short sprints.

Scrum is a framework that takes 25 years of learning across many disciplines, such as Agile, Lean, Lean StartUp, and DevOps and combines them in a seamless and easy to follow way.

It accomplishes the four big benefits we've mentioned above giving your team a business advantage over companies that are not agile.

This Scrum tutorial will be short but to the point.  If you'd like to learn more contact us

Speed: Rationale for Scrum Teams

Scrum speeds up work.  It does this in two important ways.

  1. Clarifies what should be done
  2. Gives more relevant feedback

Let's talk about clarity for a moment. Most people don't know what they should be making or when they are done making it.

Hard to believe?

Go ask a first line knowledge worker what they are working on at any random moment.  Then, ask them, "how do you know this is what you should be working on?"

You're likely to get a lot of surprising answers including, "I just got an email asking for this."

If you're team assigns tasks by random emails (as many do), stop immediately.  This is the worst way possible to run a team.

Scrum builds a backlog of work and clearly defines what work will/won't be done each sprint.

Every developer on a Scrum team knows their assignment.

Getting more relevant feedback is a reason to have a scrum team

Scrum allows teams to get more relevant feedback by having real customers provide feedback each sprint at the sprint review.  This is why many teams opt for shorter sprints.

At the end of the sprint the product owner assembles the customers and the team gets feedback from the right people.  Customers.

That ensures the feedback is relevant. 

Most teams get feedback from program managers struggling to interrupt vague contracts written by lawyers.

Getting feedback from customers at the sprint review is a gift that speeds up work.

Scrum Teams Improve happiness

Need help improving team happiness?  Easy, listen more and let your team have their way whenever possible.

Scrum teams do this through their Sprint Retrospective event where the team meets to discuss team happiness and present ideas for a continuous improvement initiative for the next sprint.

Kaizen is the name of the team's continuous improvement event.

The biggest mistake teams make is not have a Kaizen event for a sprint.

The second biggest mistake teams make is not accomplishing their Kaizen event in the sprint.

You can improve happiness by having empowered and valued team members and Scrum lets you do that through sprint retrospectives each sprint.

Improving quality rationale for Scrum Teams

Scrum isn't just about being fast to accomplish your work and happy with your job though, it's also about improving quality.

It's common for people to wonder who's job is quality in Scrum.  

Nobody wants poor quality as it will ruin your business, which is why Scrum teams strive for constantly improving quality.

This happens as each Sprint the product owner and team inspect their work with a clear eye toward customer satisfaction and quality in mind.

Inspection criteria should be clear, fair, and understood by all team members.

If you do this, each sprint will see better quality as both product and process improve week after week.

Generate more revenue with less waste

Nobody wants to find a new job every few months, which means your business needs to be generating revenue.  You need to make money to survive and Scrum can help your teams generate tons of value.

The product owner should understand the business value of your product and should be in continuous communication with the customers or market.

This will let your teams focus on building the most valuable products and delivering the most profit.

Why do so many teams fail to generate revenue?

They build the wrong thing.

Scrum teams should know ahead of time if they are building the right thing because they should be in constant communication with their customers and market.

You need early feedback to know if you are on the right track and Scrum gives you that early feedback.


In today's tutorial you learned what the rationale for Scrum teams is.  To recap, the biggest reasons to use Scrum are:

  • Speed up work
  • Improve happiness
  • Improve quality
  • Generate more revenue with less waste 

Before you go, don't forget to subscribe to stay on the cutting edge of agile.

Scrum Events

Sprints typically last between one and four weeks, and they include several key events, including:

  1. Sprint planning: A collaborative event in which the team decides what work will be completed during the sprint and how it will be accomplished.
  2. Daily scrum: A 15-minute time-boxed event in which the team meets to discuss progress, identify roadblocks, and plan for the day ahead.
  3. Sprint review: A collaborative event in which the team demonstrates the work that has been completed during the sprint and receives feedback from stakeholders.
  4. Sprint retrospective: A collaborative event in which the team reflects on the sprint and identifies opportunities for improvement. Each of these events is time-boxed, which means that they have a set duration and are designed to keep the team focused and on track.

Registered Scrum Trainer, Scrum Expert, and author

Hey, I'm Jon the owner and writer here are goagileworks.  I'm a registered Scrum Trainer and a Registered Scrum at Scale trainer with over 20 years of leadership experience. I have certified hundreds of students as Scrum Masters from government, non-profit, the military, and many industrial sections. You can reach me by submitting a contact form through this site. I also write and publish at https://drink-mix-artist.com/ where I have fun helping people find great drinks and the best rum.

Older Post Newer Post

Leave a comment

Please note, comments must be approved before they are published