Jordan Job

Professional Scrum Trainer at Scrum.org, software developer, guitarist, aerial RC pilot, photographer, constant learner, and more

  • Home
  • About Me
  • Scrum

Connect

  • Instagram
  • LinkedIn
  • Twitter
  • YouTube

The ‘Scrum Whys’ Blog Series

March 9, 2018 By Jordan Job Leave a Comment

“Why does Scrum require that you only have one person ‘own’ a product?”
“Why do we have to be done with something in a month or less? That would make our testing process really inefficient.”
“Why is everyone on a development team called a ‘developer’? Why is it called a development team anyways? My teams don’t build software.”
“Why should I use Scrum? When shouldn’t I use Scrum?”

These are just a few of the common questions I hear from attendees during my Professional Scrum classes, and I often hear these questions from individuals who have been using Scrum for several years. In our new ‘Scrum Whys’ blog series, we will explore the whys behind Scrum so you are better equipped to understand when, where, how, and why to apply Scrum.

Earlier this week I wrote about how many Agile coaches are getting one very important thing wrong – they are applying cookie-cutter practices from ‘the agile methodology’ and expecting teams to be more productive, happy, and successful than ever. The problem is that those cookie-cutter practices almost never deliver even 25% of the promised benefits because those ‘cookie-cutters’ were created within a specific organization at a specific time to solve a specific problem with a certain type of individuals, and people very often use the cookie-cutters without taking into account the differences in their context.

Scrum is sometimes criticized for being a cookie-cutter and for being too prescriptive, and those criticisms often come from people who have been unfortunate enough to work in organizations that practice cookie-cutter Scrum. This is when teams are told exactly how they should use Scrum, down to very specific practices. When teams try to deviate from those practices, they get ‘slapped on the wrist’ and quickly learn to stay between the lines. Cookie-cutter Scrum discourages creativity and innovation because people aren’t allowed to ask why or try a different approach.

One of the ‘aha’ moments attendees often experience in my Professional Scrum Master classes is when they realize Scrum is not a collection of cookie-cutter practices but just a framework that can be adapted to varying contexts, circumstances, and cultures. Once they understand the ‘whys’ behind each piece of Scrum, they feel better equipped to make it work in their team or organization rather than following the recipe book from their Agile coach (or what they read on the Internet).

The goal of this Scrum Whys blog series is to explain the whys behind Scrum so that you can get real results by making more educated and strategic decisions about applying Scrum in your context.

  • Part 1: Why Scrum Doesn’t Give You the Kitchen Sink
  • Part 2: Increase Your Agility with One Product Owner

Share this:

  • Click to share on LinkedIn (Opens in new window)
  • Click to share on Twitter (Opens in new window)
  • Click to share on Facebook (Opens in new window)
  • Click to email this to a friend (Opens in new window)
  • Click to print (Opens in new window)

Related

Filed Under: Scrum Tagged With: Scrum whys

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Search

Categories

  • Agile
  • Scrum
  • Uncategorized

Recent Posts

  • 5 things people get wrong with user stories
  • Your Agile adoption needs to be agile
  • 5 Things Management Must Do for Successful Agile Transformation

Tags

agile adoption Agile Basics agile certification Agile Coaching agile transformation Backlog Book Review change management Community of Practice Daily Scrum Estimation Facilitation Introversion leadership Lean Startup MBTI Organizational Disorders Personality Prioritization scaling Scrum Scrum Diagram Scrum Master scrummerfall Scrum training Scrum whys servant leadership Stand-Up Story Points Taylorism user stories velocity video

© 2019 JordanJob.me

loading Cancel
Post was not sent - check your email addresses!
Email check failed, please try again
Sorry, your blog cannot share posts by email.