From the Scrum Guide: “Scrum is a lightweight framework … for complex problems.”
We often hear that Scrum is designed for ‘complex problems,’ but what does that actually mean? And why does complexity matter so much in the way we work?
What is a complex problem?
The Cambridge Dictionary defines ‘complex’ as “involving a lot of different but related parts,” and ‘problem’ as “a difficulty; a matter about which it is difficult to decide what to do.” Put together, ‘complex problems’ are those that are multi-faceted, uncertain, and hard to solve.
For those who want to dive deeper, frameworks like the Stacey Complexity Model or Cynefin provide insights into navigating complexity. But to keep it simple: complexity is when there are far more unknowns than knowns.
A lot of different things might happen (or not), might be true (or not), and might influence one another (or not). Whether it’s related to technology, people, or shifting needs and expectations, complexity makes it impossible to fully predict or plan what will happen.
This is where Scrum comes in. Trying to plan every detail upfront won’t reduce uncertainty—in fact, it often increases it by introducing even more assumptions. What will help is experimenting, trying things out, inspecting, and adapting.
Scrum thrives in complexity by providing a framework for teams to learn quickly and respond effectively. It enables you to test ideas, gather feedback, and make adjustments as you go, rather than getting stuck trying to predict the unpredictable.
So, how does your initiative compare to complexity? Are you dealing with more unknowns than knowns? How are you uncovering and addressing those unknowns?
I’d love to hear your thoughts—please share them in the comments below!
I hope you find value in these short articles and if you are looking for more clarifications, feel free to take contact.
Don't want to miss any of these blog posts? Have the “The Scrum Guide Explored” series weekly in your mailbox.
Wishing you an inspiring read and a wonderful journey.
Scrum on!
