Agile: Adaptive & Value Driven

Product development cycles are getting shorter, at the same time customers getting used to high quality user experiences – Companies looking ways to overcome such challenges on ever shrinking budgets, can ill afford to spend millions on products/projects that take months (if not years) to develop and have longer return on investment (ROI) periods.

This is why more and more companies are adopting Agile methodologies.

 Going agile isn’t about developing software quickly, it is about developing products which are customer centric, delivering prioritised features iteratively allowing benefit realisation early. It is also about enabling companies to adopt to market dynamics – hence Agile in two words – is Value Driven and Adaptive. 

Value Driven

As the enabling toolset of continuous integration & delivery matures, it becoming easier to deliver software iteratively – and when features with higher relative values are delivered early, right from the word go, and followed through with a regular stream of newer features, it is possible to address and exceed customer expectations – technology leaders are already setting up benchmarks with daily or even shorter release cycles into production. Agile methodologies also challenge sponsor to think about what constitutes value – (e.g. is a design document of value? only if the customer thinks so) enabling teams to generate ROI right from the start.

Adaptive

Another major premise is the ability to adapt – hence the Agility. Delivering features early may not be enough when the goalpost you are shooting for moves, but shorter feedback and corrective cycles means that you can correct the course of action early and able to respond to emerging market opportunities.

 

Obviously, there is no magic bullet, the journey would still have to be made, with team doing all that is necessary for the application to rise – what is different though, is that team will not be in the dark about how they are going to get to the end, customers will not have to wait till the end to touch and feel the product, there won’t be any grand change control processes if the goalpost keeps moving, instead business will be able to change their minds and team will be able to adapt, learn and produce valuable piece of software along the way.

Here on this site, I would try and bring out my own unique perspective and experience of Agile processes – and I hope that will give something for readers to chew on, I look forward to any comments/insights from everyone on this or future pieces on all things Agile.