Project Management

Project Management Central

Please login or join to subscribe to this thread

Topics: Agile
Why almost all companies are moving from Waterfall to Agile?
Why companies are adopting Agile/Scrum methodologies over Waterfall?
Sort By:
Page: 1 2 next>
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.
...
1 reply by Tabassum Mehmood
Jun 27, 2020 12:14 PM
Tabassum Mehmood
...
Thanks
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.
Tabassum -

In short:

- 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".

Kiron
...
1 reply by Tabassum Mehmood
Jun 27, 2020 12:29 PM
Tabassum Mehmood
...
Agreed, Its not PM or BA who decides which path to follow waterfall or agile. Its totally depends on Stakeholders/Sponsors/Customers and of course can't ignore the budget constraints. Agile is more expensive than Waterfall.
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.

Thomas
...
1 reply by Tabassum Mehmood
Jun 27, 2020 12:21 PM
Tabassum Mehmood
...
Agreed, Waterfall is like suspense movie all requirements are collected and then development starts and delivery. Product is not visible to Stakeholders or customers, requirements are gathered and product is delivered after given time. In Agile, high level requirements are captured initially and then team gets more detail as they move forward. Its incremental piece by piece and visible to Stakeholders or customers all the time, requirements are put in backlog which is called product backlog and its been add/remove/edit and prioritize based on Stakeholders or customers needs. In PI meetings user stories are sized and bring into sprint which is also known as sprint backlogs
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.
...
1 reply by Tabassum Mehmood
Jun 27, 2020 12:26 PM
Tabassum Mehmood
...
Due to incremental approach, the product is visible to stakeholders and customers, and continuously feedback and bugs fixing make less chance of project failure versus waterfall, in waterfall once requirements are captured, then architect/design then execution and delivered, not having visibility its too much of the risk of any functionality been wrong captured or designed
Hi Tabassum,
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...
Jun 27, 2020 8:20 AM
Replying to Sergio Luis Conte
...
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.
Thanks
Jun 27, 2020 9:48 AM
Replying to Thomas Walenta
...
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.

Thomas
Agreed, Waterfall is like suspense movie all requirements are collected and then development starts and delivery. Product is not visible to Stakeholders or customers, requirements are gathered and product is delivered after given time. In Agile, high level requirements are captured initially and then team gets more detail as they move forward. Its incremental piece by piece and visible to Stakeholders or customers all the time, requirements are put in backlog which is called product backlog and its been add/remove/edit and prioritize based on Stakeholders or customers needs. In PI meetings user stories are sized and bring into sprint which is also known as sprint backlogs
...
1 reply by Sergio Luis Conte
Jun 27, 2020 4:44 PM
Sergio Luis Conte
...
Sorry Tabassum, what you describe is not waterfall. What you describe is sequential. You can use Agile with waterfall. For example using prototyping when taken requirements and lot of other things.
Jun 27, 2020 11:34 AM
Replying to Nishant Grover
...
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.
Due to incremental approach, the product is visible to stakeholders and customers, and continuously feedback and bugs fixing make less chance of project failure versus waterfall, in waterfall once requirements are captured, then architect/design then execution and delivered, not having visibility its too much of the risk of any functionality been wrong captured or designed
Page: 1 2 next>  

Please login or join to reply

Content ID:
ADVERTISEMENTS

"Whatever does not destroy me makes me stronger."

- Friedrich Wilhelm Nietzsche

ADVERTISEMENT

Sponsors