"Fr-Agile" - New Way of Going Agile
Agile methodology is catching on. Here's a look at Fluid-ready Agile, or Fragile.
Join the DZone community and get the full member experience.Join For Free
What if someone says "Agile" was not relevant or effective so far in its true sense, will we believe that?
Will we believe that "Agile" was really meeting its speed and following its profound manifesto?
Was the "Agile" concept itself enough to secure the need of time-to-market which industry was seeking for so many years?
With the so many disruptive technologies (one of my earlier posts - https://dzone.com/articles/emerging-and-disruptive) coming to rescue us from the unsatisfying need to provide value to our human ecosystem in terms of business, social responsibilities, and self-motivated programs, we always thrive to deliver in shorter time but in chunks. That's what we expect in agile, isn't it? But Agile of its own has limited capability. Agile is a discipline with some defined processes, standards, and tools.
There are multiple Agile-related platforms which not only help to increase agility of the delivery, but also provide governance frameworks to measure the usability and effectiveness of using agile process. Agile doesn't dictate technology or infrastructure or the "architecture" behind the platform or product to be built. But I think that was a big gap to bring true agility in value-driven changes to our work. That is what was missing for so many years in conventional wisdom.
Think of a monolithic system built over time and still being developed/changed for new requirement or existing defects. Isn't this a big pain to take a monolithic application through all the steps from evaluating ideas to deploy in production though in a smaller and faster release through sprint based delivery methodology?
Wasn't there a risk of regression? How these changes be tested and deployed simultaneously? Was there the right technology, architecture, platform, infrastructure, and process in place so that we can build and test as needed or on-demand, or on continuous basis or in silo with minimum effect of regression?
I think all these questions are being answered partly or mostly by combining three major concept. Yes "DevOps" and innovative "Microservice Architecture," and "Cloud" what make the new Agile principle called "Fr-Agile" (Ironically called "Fragile," Fr is pronounced as Fluid-ready")? It is fluid because it can flow, glide, roll and not having any defined shape. It makes the movement from one place to another (from one state to another) easy, speedy, and agile. I am not sure if anyone has coined this term but I deemed this to be a next generation revolutionary movement. Agile will truly be "agile" with the changes being pushed, tested, integrated, verified, and deployed through Continuous Integration, delivery, and deployment. With containerization as well as microservice architecture, the code can be termed as shippable and self-contained. The services/applications can be deployed as self-unit (not depending on plethora of other components/modules) and devoid the complexity of a monolith. Last but not the least, Cloud will give flexibility from infrastructure perspective and boost on how Devops, microservices, and containerization can help to drive agile collaboratively.
With the evolution of API based ecosystem, all these 4 concepts (Agile, DevOps, Microservices, and Cloud) merge even closer and depict the true need of an agile system.
Opinions expressed by DZone contributors are their own.