This content is retired but we have related up-to-date content below.
Trial lock

This Research is for Members Only

Not a member? Unlock a free sample of our research now!

Already a member?

Sign in now

(By Info-Tech Analysts Morgan Chmara, and Sarah Kearse - Printed with permission from Processor magazine.)

Let’s be honest, no project ever moves forward without a hitch here and there. It seems like there is always the need for revision and rework, even if it’s minor. But this tends to be more of an issue of how the project is handled and managed, rather than the content of the work.

There is a lot of buzz around Agile vs. Waterfall software development techniques and debate about which is better. While the project managers and developers pit the methods against each other, an important question is often overlooked: what does the client want?

The answer lays in the hands of the customer and their project expectations.

Related Content

Hide Details

Search Code: 12465
Published: October 27, 2009
Last Revised: October 27, 2009


  • Missing comment
    Wayne Barnard | 11-12-2009

    This is a good summary of incorporating best practices of Waterfall with Agile. There are benefits to both and integrating the Best of Breed makes practical sense.

  • Missing comment
    Gregory Speyrer | 11-12-2009

    An interesting concept. Te next step is the development of a framework.


Get Access

Get Instant Access
To unlock the full content, please fill out our simple form and receive instant access.