work-for-scrum-trainer-talk

Trainer Talk Podcast: What Work Isn’t Suitable for Scrum?

work-for-scrum-trainer-talk
Share on facebook
Share on twitter
Share on linkedin
Share on email

Episode Description:

In this episode of Trainer Talk – the supplemental series to the Agile Coaches’ Corner podcast – Sam Falco, an agile coach and Certified Scrum Professional, answers the question, “Are there any types of work which aren’t suitable for Scrum?”

Listen on Google Play Music


Scrum is for Complex Work

Scrum lives in the area of complexity, where more is unknown than is known — about requirements, about how to fulfill them — and we have to apply an empirical approach in order to discover what we need to know and how to solve the problem.

 

Scrum is Unnecessary for Simple Work

Scrum would not be suitable for very simple work domains, where cause and effect are obvious to everyone, and all needed information can be known. This is the realm of “best practices,” meaning there is one way to solve the problem; it is known to everyone involved, and following the known process will provide the expected result. As a concrete example, think of an oil change. In simple work, Scrum is unnecessary.

 

Scrum is Overkill for Complicated Work

For more complicated work that is not complex, more is known than unknown about the problem to be solved. This is the realm of “good practices.” The problem is not as precise or easily defined as in simple work, and there are likely a few different ways to solve it. The example I always use is when I had to have a new roof put on my house. Everyone agreed on the requirements: Make my roof water-tight! But there are multiple types of roofing technologies and my house’s roof has a peculiar design. Those complications required analysis before we could decide on the appropriate approach. For complicated problems, an empirical approach like Scrum could work, but it would likely be overkill.

 

Scrum is Not Suitable When We Know Nothing

Finally, Scrum is not likely to be suitable for a chaotic environment, when almost nothing is known about the problem that needs to be solved or how to solve it. The classic example is a natural disaster, but I’ve also worked in an environment where no one could agree on what was wanted and any plan we made could be invalidated at a moments’ notice.

 

Provide Feedback

Let us know what you thought about this supplemental episode of the Agile Coaches’ Corner. If you’re interested in training, visit agilethought.com/training or call us at 877.514.9180 to learn more. And if you have a question you want us to answer on the next Trainer Talk episode, email us at podcast@agilethought.com.

 

Want to Learn More?

Stay Up-To-Date