A question, “What exactly is Agile?”, keeps troubling people.
They either make reference to the manifesto or map it with Scrum and then get circled in its events and practices.
Though Agile movement started as a better way of developing software, it has moved beyond software development.
Agility has evolved into a way of thinking, permeated to organizational work culture, experimentations, better ways of doing business, product development and servicing customers.
It started in the context of and in reaction to the Waterfall approach initially. Now it doesn’t have anything specific to compare to. It’s ever-evolving.
That’s the reason, even though the movement began with Agile manifesto, the manifesto in itself didn’t remain a constraint in making further improvements ever. In the last few years, people have evolved and embraced Modern Agile concepts, Lean thinking, Lean Startup and Design Thinking approaches for the same reason.
Definition
If you look at the online dictionary, ‘agile’ means “able to move quickly and easily” with an emphasis on changing direction. Taking a cue from its dictionary meaning – ‘agile’ is the ability to create and respond to change, quickly and with ease in order to succeed in an uncertain and turbulent environment.
From the software development perspective, in the late 1990’s, several software development frameworks emphasized close collaboration between the development team and business stakeholders; frequent delivery of business value, self-organizing teams; and smart ways to craft, confirm, and deliver code.
In early 2001, 17 software development practitioners gathered in Utah to discuss their shared ideas and various approaches to software development.
— Alistair Cockburn
Once these practitioners had the word in place, they had to decide what it meant to them for the purpose of writing software. They chose 4 values to centre themselves in the world while working and added 12 principles.
Question: There may be innumerable practices suited to, or may evolve in a context. How to ensure if those are acceptable in Agile methods?
Answer: Agile methods are based on common sense. As long as a method or practice is in line with the intent of agility and with Agile values and principles, you are fine.
For instance, a team realized that distributed retrospective along with the customer team was not helping them in solving local problems. They decided to have a local retrospective as well and it worked pretty well for them. Similarly, though the definition of Ready is not essential in the Scrum guide, it is tremendously useful in the context of distributed teams working in opposite time zones.
Summary
Essentially, agile is about:
- Are we able to create change and respond to changes, quickly and with ease in an uncertain and turbulent environment?
- Do we center ourselves on manifesto’s four values and principles?
Nicely put Shrikant,its a nice read..thank you for sharing
Agile means embracing change. Just like Beck said on the front cover of the very first Agile book. Everything else follows from that.
Beck says he learned this from watching how his engineer father worked with teams. So that begs the question … just how far back does agile culture really go?
I trace it back about 4,000 years. Here’s what Lao Tzu had to say about it. Back then, Agile was pronounced “sheng ren”. But it amounts to the same:
Agility is practical, not mystical –
A way of working, not a state of grace.
Listening as if crossing thin ice,
Testing as surrounded by danger,
Learning as in a strange land,
Simplifying as thawing snow,
Integrating as the deep woods,
Leading as the river valley,
Innovating as the spring silt.
Imagine the ice solid or the stream clear,
Stop to plan your way ahead,
Ignore what moves underfoot;
You fall and disappear.
From “The Agile Tao” at https://leanpub.com/agiletao