Agile programming (was Re: [P|C] Banksel)
Gerhard Fiedler email (remove spam text)
> That's why I like the iterative approach, where planning is followed
> by writing actual code. You gain useful information after every
This is, in principle and in many cases, a good thing. Nobody has ever
claimed that it isn't. But it needs a context and has limits.
There are projects where there is no use in trying to deliver a first
iteration so soon as the Agile Manifesto suggests. Sometimes, the first
iteration takes /much/ longer than all others, because until we get to
the first iteration, we need to gather requirements (for the whole
project), we need to architect (the whole or large parts of the
project)... this all costs time. So treating the first iteration the
same as the others WRT its duration doesn't make sense in many projects.
Which means that this part of Agile doesn't apply to these projects.
In reply to: <87E93ED45C2748818DCA91530D191619@ws11>
See also: www.piclist.com/techref/microchip/devprogs.htm?key=programming
You must be a member of the
piclist mailing list
(not only a www.piclist.com member) to post to the