psmm wrote:Hey eValid! How do you think eValid fits into the agile method idea?
The "agile manifesto" was published in 2001, a creation of a team of some 17 authors who were on a ski vacation in Utah. [Check out the Wikipedia entry for "agile manifesto" for a good read.]
A basic tenant of what from that start has come to be called the "agile methodololgy" is that it is more important to have a working solution than it is to have a lot of fancy planning documentation, detailed design specifications, and all of the other paperwork associated with conventional software development. In a way, the working software is its OWN specification pf what it actually does.
But, where does eValid fit into this picture?
The answer is that eValid is a pretty natural fit to an agile development method for a web application, because eValid makes it very easy to record and edit a functional test, to lift the functional test into a substantial load of activity, and even to scan a website in real time.
We wouldn't say the fit is 100%...but we think that 99% might be a good guess.
The eValid Team