From the Scrum Guide:
"Try it as is."
From Cambridge Dictionary:
Try: "To test something to see if it is suitable, useful, or if it works."
As is: "In the state that something is in at the present time."
Many teams tweak, adapt, or customize Scrum too soon—often before fully understanding its principles. The result? Suboptimal performance, frustration, and ineffective delivery.
The advice "try it as is" is grounded in real-world experience: many teams struggle with Scrum not because it doesn’t work, but because they never truly tried it as designed.
In an earlier post, I covered the word framework. One of the key characteristics of Scrum is that you can add complementary practices—but the core elements of Scrum work together as a system. Removing or modifying parts too soon weakens the framework.
So, before you start making changes, ask yourself:
Are you really using Scrum "As Is"?
Some examples:
Do you have a real #ProductOwner, #ScrumMaster, and Developers who are self-managing and truly cross-functional?
Common issue: a lack of time to collaborate as one team, or missing key skills needed to build a complete solution.
Do you hold all the Scrum Events—and actually achieve their goals?
Common issue: rushing through events without achieving their purpose, and turning them into status updates instead of decision-making moments.
Do you use the artifacts properly to create transparency?
Common issue: avoiding tough conversations, a lack of openness about risks and challenges, or failing to acknowledge when more time is needed to finish work.
Discomfort is not a reason to modify Scrum.
Many teams modify Scrum because it feels uncomfortable—without realizing that this discomfort is part of the learning process.
Since 2001, I have never felt the need to change the Scrum framework itself.
Instead, the real improvements have always been fundamental organizational changes—better alignment, better team structures, better focus, and better leadership support.
A challenge: try Scrum "As Is" for five Sprints.
- Have you truly tried Scrum "as is," or did you modify it before fully understanding it?
- If your team is struggling, is it really because of Scrum—or because of something else?
- What would happen if you committed to trying Scrum "as is" for five Sprints before making any changes?
I’d love to hear your thoughts in the comments below!
I hope you find value in these short articles and if you are looking for more clarifications, feel free to make 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!
