Re: Agile Development, Anyone?

[Evan Harris <auctionitis@xxxxxxxxx>]

If you've been building tests along with your code,  then when you
make changes proving that they work is simply a matter of re-running
the test unit including the new tests.

The problem is that if you have legacy code that wasn't built this way
then you have to somehow build tests into it or come up with some
other strategy to ensure it still works.

A few places I've worked would struggle with the idea of pair
programming - they'd see it as cutting the billing in half.

On Thu, Aug 25, 2011 at 5:11 AM, David Gibbs <david@xxxxxxxxxxxx> wrote:
> On 8/24/2011 9:43 AM, john e wrote:
> > So it's the realisation that you really can't develop (business!)
> > software using a strict process, with up-front planning and
> > requirements gathering. A much better way is to be more "iterative",
> > where you "grow" software, instead of building it (like a house or a
> > car).
>
> I disagree ... I don't think you can develop software WITHOUT long term planning, requirements gathering, etc.
>
> Any software release has to have a goal and an over arching plan.
>
> How you implement that plan can be iterative.