Those of us who consider ourselves Post-Agilists have taken what worked and cross-bred it with the best bits of dozens of other approaches and disciplines, creating new variants that have the potential to be even more exciting, daring and shocking.
– Jason Gorman Post-Agilism – Beyond the Shock of the New
I call this brand of process skepticism exhibited by experienced Agilists “Post-Agilism”.
Test your process, and strive for improvement. Be skeptical, and don’t be afraid to follow good Post-Agilist thinking. Some good Post-Agilist thinkers are former process zealots who know and enjoy Agile development, but also don’t throw out anything that isn’t generally accepted by Agilists.
– Jonathan Kohl Post-Agilism: Process Skepticism
The Software World is moving beyond “Agile” into the post-Agile world — and for good reason. The main problem with Agile, is that it was invented in the 90s, to solve the problems of the 80s. Problems that are different and unrelated to what we have today. But the world has changed – while the Agile practices and mindset have not kept pace.
Waterfall: Production is King. Spiral/Agile: Customer is King. Post Agile? User is King.
– Kathy Sierra What comes after usability?
What is Post-Agilism?
This requires a two part answer. Post-Agilism is: 1) a growing movement of former Agilists who have moved beyond Agile methods, using a wide variety of software development tools and methodologies in their work. 2) an emerging era. Now that the Agile movement has moved to the mainstream, what’s next?
– Jonathan Kohl Post-Agilism Frequently Asked Questions
… as far as I can tell, the objections to the term “Post-Agilism” seem to be largely territorial.
I’m not attempting to claim any territory for myself. I am arguing that it belongs to nobody, and we are free to roam and explore as far as we see fit. This, I suspect, was the spirit in which the whole “Agile” thing got started in the first place. It’s a free-thinking, pioneering spirit that has somehow been lost as the term “Agile” has become cynically commodotised.
– Jason Gorman Post-Agilism Explained (Pretentiously)
The Agile Manifesto was a welcome development in an industry that seemed mired in paperwork and process. Unfortunately, “Agile” can be carried too far. I propose our rallying cry not be Agile, but value – both to our customers and our teams. If we are delivering what our customers need, and we are building up our teams and those we interact with, does it matter what it is called? Let’s stop worrying about whether what we do is “agile” or not, and go back to calling it software development. Let’s worry about how we can do that to the best of our ability.
– Jonathan Kohl Is ‘Agile’ Distracting You?
This is the new face of Agile as I see it, an agile that embraces the value system of the Agile community but within the context and realities of getting something done in large enterprise organizations. In the last few years though, I’ve come across a number of agile experts (or agilistas) who have 8 to 10 years of experience in agile techniques but little awareness (even at the broadest levels) of disciplines outside of Design and Implementation. I’m frequently surprised at the level of dogma that surrounds their interpretation of Agile and the lack of tolerance for anything outside of the realm of Design and Implementation. Most have little appreciation for different roles on a project let alone artifacts or awareness of different stakeholder needs. Increasingly agile is becoming a marketing term and it’s being leveraged to justify poor work habits and an exclusively developer centric perspective on building software.
I’m not alone in these observations and I’ve noticed others starting to write about Post-Agilism like Jonathan Kohl and Jason Gorman. Philippe Krutchen recently wrote a very interesting piece called Voyage in the Agile Memeplex which discusses agile as a culture and the effects this has on software development and effective communication.
– Bryan Campbell Post-Agilism: The Next Wave
I like to fuse different ideas together and see if I can create something new from the combination. There may be stark lines drawn between the fields where the ideas come from, but that doesn’t bother me too much. It gets me into trouble sometimes, but the ideas are what are important to me. When it comes to software development, I don’t really care if an idea is “Agile”, “waterfall” or has no label at all. If it’s a good idea to me, it’s a good idea. Sometimes on software development projects, I weave together combinations of these ideas in a way that may seem strange to some. I’ve started calling this style that I and others are exploring: “software development process fusion.”
– Jonathan Kohl Software Development Process Fusion: Part 1
Software development process fusion involves taking different kinds of processes and tools and utilizing a combination on your project to help you reach your goals. You aren’t just using one particular methodology or school of thought or toolset, you are using a combination of tools that fits your unique needs on your project to help create value.
– Jonathan Kohl Software Development Process Fusion: Part 2
One of the Post-Agile ideals I have witnessed and encourage is the breaking down of walls between methodology camps. When teams apply practices, processes, rituals and tools from Agile methodologies and create a fusion with other, compatible processes in order to create value, interesting things occur. In spite of apparent differences, many good ideas can be gleaned from dissimilar processes, and applied and adapted on your team with great effect.
Methodology wars are the inevitable outcome of process visionaries working against the grain to introduce new ideas, and the resistance they face from the more established process idealists. Sometimes radical behavior or extreme statements are an effective way to get attention for ideas that are dismissed. Now that Agilism has become as well known as other process communities, it’s time to stop fighting and find the areas where we agree, and try to improve how we all develop software. Instead of posturing over what process movement is “best”, let’s focus on the value we can create together.
– Jonathan Kohl A Post-Agilist Concept: End Methodology Wars
- Agility has crossed the chasm
- But Agility is not an end in itself
The agile movement brought:
- Awareness of the importance of the people factor
- Efficient software development practices, exploiting iterations and feedback
- Some dogmatism, blindness, and memory loss.
Post‐agilism takes a skeptical look at the agile movement, and moves forward.
– Philippe Kruchten Agility Situated: Is Agility Simply a New Passing Fad? A post‐agilist view
Agile promises solutions it cannot deliver. It promotes sloppy requirements, hides the true cost of development and prevents effective management. Contrary to what we’re told to expect, this leads to long-running projects, dissatisfied customers and an overall IT ineffectiveness.
– Lajos Moczar Why agile isn’t working
…post-Agilism is basically a movement in the software development community of people who see themselves as moving beyond Agile methods. They have used Agile and not-so-agile methodologies and have moved beyond both to using an amalgamation of tools and methods that best facilitate them doing their job. Post-Agilism is not about evangelizing a particular process or a set of practices or even the Agile Manifesto, it is about getting to the core of the issues that process in general tries to address and solving them in the best ways possible.
– Alan Skorkin Are You Actually A Post-Agilist?
Don’t get me wrong. There are absolutely good things that Agile has brought to software development. Iterative development and constant communication between Engineering and Product have become industry standards in modern software development. Agile has some great ideas, and is a vast improvement over what existed before it. But the zealots go too far, claiming that Agile can work for every team and every situation, and if those teams fail, it’s because they didn’t follow the rules strictly enough.
– Talia Fukuroe Breaking Free From the Cult: 6 Reasons Why Agile Doesn’t Work
Agile is futile without Value
- Processes, tools, methodologies, etc. are worthwhile to the extent that they help us create value.
- Agile methodologies can help you create value or they can distract you from creating value.
- Practicing Agile does not guarantee you will create value.
– Jonathan Kohl Video: What’s More Important: Being Agile or Creating Value?