Everyone Can Benefit From Using Agile Practices
Recently, I have been reflecting on the landscape of product development methodologies, ranging from traditional to agile approaches. At the core, I believe that, regardless of the chosen approach, the goal remains the same: to create outstanding products that delight our customers.
Over the years, I’ve had the privilege of fostering environments that truly embraced Scrum in self-managing settings. Seeing how empowered people collaborate and create more value together than they could individually, and how they engage in collective continuous learning, has been truly magical.
Likewise, I’ve navigated more traditional environments, discovering significant value in integrating them with agile practices in “Projagiles” or “Scrumjects.”
Even though I believe that a focused use of the Scrum framework can lead to delivering value sooner and promote continuous learning, I still see value in combining more traditional project management methods with agile practices in organizations with a less pronounced appetite for agile thinking.
It is, however, important to adjust our goals and understand that we cannot expect to reap the same benefits as when fully embracing the Scrum Framework and self-management.
When is it Scrum, and When is it Something Else?
I don’t agree with the argument that Scrum is too strict or lacks flexibility. Scrum, as outlined in the Scrum Guide, is distinct and should not be confused with other sets of agile practices; doing so dilutes its significance in our discourse.
Don’t misunderstand; I fully support experimenting with various practices, including agile ones, to identify what best suits our specific context. However, for clarity in our discussions, if we deviate from Scrum, we should refer to our approach differently.
Imagine: The confusion and potential chaos if you attended a football match only to discover that the game was being played with rugby rules. Both include a ball, but they are not the same.
What Do You Call Your Approach?
A friend of the house once posed an intriguing question: What do you call your agile practices when you’re unable to adhere to the Scrum framework entirely?
After careful thought, I concluded that the answer should be tied to your objectives for adopting agile. If your aspiration is to align with the Scrum Guide, then it’s Scrum. Otherwise, you should feel encouraged to be as inventive as necessary in naming the unique blend of agile practices you’ve adopted.
Let’s Collaborate, Not Battle
So, let’s refrain from battling over what is best, but instead collaborate on finding the best solution for our specific context.
The key principles:
- Understand your goals for adopting agile practices
- Be honest about what you’re actually doing
- If it’s Scrum, call it Scrum
- If it’s something else, give it an appropriate name
- Focus on what works in your context
Let’s be courageous together!
Usikker på om I faktisk kører Scrum?
Lad os tale om jeres nuværende tilgang og finde ud af hvad der giver mest mening for jeres kontekst.
Book Samtale