In your office corridors and around the cafeteria, are you hearing whispers that Agile has failed? Do comments such as "Agile/Scrum is a Failure" or "Agile Doesn't Work" seem to be resonating more and more in team discussions and across workplace gatherings? Before we dismiss Agile lets do an "Agile Fit Test"
1. Discerning "Agile Principles" from "Agile Practices"
This is Agile
Individuals and interactions over processes and tools.
Working software over comprehensive documentation.
Customer collaboration over contract negotiation.
Responding to change over following a plan.
This is NOT Agile
User Story format "As a I want to so that ..."
Daily Standup 15 min.
Retrospective every Sprint.
No changes to Sprint after start.
Story Point Estimation.
Velocity Chart.
Kanban Board.
Scrum, Kanban, SAFe
And list goes on and on ...
Agile Practices Don't Define Agile They are merely examples of "techniques and methods" that can be used to implement Agile
At the heart of Agile lies its foundational values and principles, as captured in the Agile Manifesto. Agile is fundamentally a philosophy or mindset.
Its characterized by a focus on adaptability, prioritizing customer satisfaction, fostering collaboration, and maintaining a readiness to respond to change rather than rigidly sticking to predefined plans and processes.
Agile practices, such as those mentioned above (e.g., Daily Standup, Sprint Planning, Retrospectives), are concrete methods or techniques that teams can adopt to implement this Agile philosophy in their day-to-day work.
These practices are not prescriptive or exhaustive; different teams might find success with different sets of practices based on their unique circumstances, challenges, and goals.
Agile on Highways
Lets see an example where we follow Agile to its core without using any of the practices mentioned above.
2. Agile "Fit Test" for Your Team
Embracing Agile means embracing a mindset shift. Challenging the deeply ingrained practices of traditional waterfall methodologies is not trivial. If you're on the fence about whether Agile is the right fit for your team or company, then you can start by asking by asking 4 questions.
Ask yourself:
Choose the Agile Principles that Align with Your Team's Core Values and Priorities:
Do we prioritize individuals and their interactions over processes and tools?
Do we value customer collaboration over contract negotiations?
Is delivering working software more important to us than comprehensive documentation?
Do we prefer adapting to change over strictly following a predetermined plan?
0-1 "Yes": Allergen Alert
Agile might not be the best fit for you. It appears you could be experiencing what's known as 'Agile Allergy,' a condition where employing Agile methodologies leads to a range of discomforts. Therefore, it might be advisable not to include Agile in your 'diet.' These discomforts can include, but are not limited to:
Resistance to Change
Frequent Complaints
Visible Frustration
Isolated Resistance
Occasional confusion and misunderstandings
2 "Yeses": Bite Size Sampler
Give Agile a Chance. Start by sampling the Agile methodology as an appetizer, a little teaser to whet your appetite. It will spark your curiosity, making you eager for more. Before you know it, you'll be craving the full course.
A good start will be to break large pieces of work into smaller, more manageable tasks and adapt iterative processes. This approach encourages you to focus on delivering value incrementally, allowing for regular feedback and adjustments along the way.
As you become more comfortable with these bite-sized pieces, you can introduce other practices one dish at a time.
3 "Yeses": Essential Diet
Agile should be a routine part of diet. Its a daily multivitamin packed with all the essentials you need to keep your team’s energy up and operations slick.
Neglecting it? That’s like skipping your fruits and veggies—before you know it, you’re running on low, growth stunted and the efficiency dipping. Make Agile a non-negotiable on your team’s menu, and watch as you all get ready to tackle anything the workday throws your way.
4 "Yeses": Daily Diet
All your meals should be prepared using Agile ingredients. Pick from the tried-and-tested recipes like Scrum, Kanban or SAFe. But hey, don’t be shy! Tweak those recipes, throw in your own secret spices, or go gourmet and create a brand new dish. The kitchen is yours, so cook up something that’ll have everyone coming back for seconds.
Don't be Shy, Take the Survey
Choose the Agile Principles that Align with Your Team's Core Values and Priorities
1. Individuals and interactions over processes and tools?
2. Working software over comprehensive documentation?
3. Customer collaboration over contract negotiation?
4. Responding to change over following a plan?
You can vote for more than one answer.
4. Conclusion
The narrative that Agile methodologies fail frequently stems from misconceptions rather than inherent flaws in Agile itself. It's crucial to recognize that the challenges some teams face when adopting Agile often arise from a rigid application of practices that may not fit the team's experience level or the organizational culture. This misalignment is mistakenly interpreted as a failure of Agile principles.
At its core, Agile is fundamentally about adapting to change, valuing human connections, and cultivating an environment where continuous improvement is the norm. It is less a rigid set of rules to be followed blindly and more a collection of principles and practices to be adapted and adopted as needed.
Comments