On Waterfall vs Agile

This post on G+ inspired me to write this (you may or may not have access to it)

Project management methodology, business model and software engineering practices need to go hand in hand.

for e.g.

A fixed price project needs to be accompanied with a more rigid waterfall Project Management methodology and need to be supported by a clear scope, arc & solution design. Change request control obviously have to be tight and clearly communicated to the people who are paying for it.

A flexible agile methodology has to be supported by time & material billing so that business owners/client understand the implication of each change. it also need to be supported by discipline software engineering practices like automated regression testing, adhering to open closed principle, etc to allow change to happen frequently without sacrificing quality of the product.

Mixing and matching the 2 composition will often give you the worst of both world.

Both rigid & flexible approach can work well with the right "support".

  1. jpartogi says:

    Not true. Agile can be used in fixed project if you know how to do it. Please don't spread FUD. :-) But I do agree that mixing Agile and Waterfall can lead to an abomination.

  2. Water Quality Testing says:

    rain, from drinking water steam condensing from the air and dropping to world or beach.Most water steam over the sea comes back to the sea, but gusts of wind carry water steam over land at the same rate as run-off into the sea, about 47 Tt per year.