Software Development Professionals are talking a lot about Agile at
the PMI meetings, The IIBA meetings and the SPIN meetings. Agile
is a new development methodology. Well to those of us that have
been in the industry for twenty years it's not exactly new. It's
quite similar to RAD. The bottomline is that the software
development industry is frustrated with structure methodologies
because they are associated with being slow and rigid. On the
other hand everyone feels like Agile is chaotic and undisciplined.

What if there is a happy medium? What if you can have the best of
both words? This is coming from someone that has actually worked
on two Agile projects but came up through the years doing structure
methods. At the end of the day there is an approach that allows you
to have the best of both worlds. What I've observed first hand, is
that you do your Scoping, High Level Defining and Design phases in
the traditional structured method but compress and fast track where
you can. When you get to the Design and Develop stage you use the
agile methods and approach, interweaving detail requirements
eliciting...

Do you have an opinion on Agile versus Structured development
approaches?

Does this topic interest you? Does your organization need a way to
streamline and fast track without sacrificing structure....

Let us know and we'll provide more topics and articles on Agile
versus Structure...

We are always open to answering and addressing your real world
questions and challenges!



J. Kay