September 28 & 29, 2020 | Virtual
Please login or join to subscribe to this thread
It's obviously not a new trend because agile ideas have become popular over several decades. In the field of technology and knowledge work a key driver has been the fact that technology has grown in diversity and complexity such that predictive planning and development is much harder to get right than iterative and continuous delivery. More generally, the pace of innovation, globalisation and market change means that being able to respond rapidly to changing conditions is much more important than predictability.
That´s not true, sorry. Mainly because waterfall is a life cycle which Agile is an approach. You can use Agile with waterfall life cycle. In fact, is what we are doing today and I am doing from long time ago. Take a look to Tom Gilb´s work for example.
I agree with Sergio here. Both are different and it can not be generalized that organizations are adopting agile over. You cannot simply apply agile to a project which needs to follow waterfall.
- Faster ROI
- Greater stakeholder satisfaction
- Improved quality
- Improved ability to respond to change
But adaptive approaches need to fit the context of a project - it should never be "we only do waterfall" or "we only do agile".
You can use a waterfall life cycle and still be agile.
If there is a perception of a contradiction it is caused by agile marketing.
The life cycle is just pro-jecting an intended strategy to reach a goal, to the best of the knowledge available at the start. We do this all the time because we prefer security and structure emotionally.
Waterfall is having a step-by-step approach going forward until a defined end. This is also done in most agile environments (see sprint cycles, backlogs, ..).
Agile mindset means to be observant to changes (which becomes more and more important due to accelerating change) and learnings, and be able to respond within the life cycle.
Tabassum, in today's dynamic world, the prioritization review has to be more frequent. Agile / scrum methodology are designed for that culture. Waterfall gives you less of such opportunities.
They both can and do co-exist in the same project delivery ecosystem. There are a lot of benefits with adopting an agile MINDSET (note: not method!) - change appreciation, dynamic risk-response capacilities, leaning of processes/waste elimination, etc which all carry tangible business benefits, hence the widespread push to "be" more agile.
Kiron's point on adapting the approach to the project's unique context cannot be overemphasized...
Please login or join to reply