Agile programming (was Re: [P|C] Banksel)
Vitaliy email (remove spam text)
> Yet again, it comes down to how you tackle the project from a strategic
> level, how you set the foundations of the project that determines how it
> will look at the end. The actual details of how the bricks get laid is
> important, but the overrall architecture/design and build strategy are
> essential too.
I'm all for requirements gathering, design, or planning. However, I know
from experience that initial assumptions are often proven wrong. Change
happens, it's a fact of life. It makes sense to accept it, and adopt to it,
Instead of trying to fight it.
> Perhaps Agile has a 'manifesto' about where to prioritize the
> design/architecture process as well as the development process....
I'm not sure I understand the quesiton 100%. How can you prioritize a
> i think, more relevant to this discussion, it takes an experienced/wise
> manager to determine what the first tasks should be so that the
> difficult things are accomplished first. Like putting together a jigsaw
> puzzle, if you get the process going right, it gets easier and easier as
> you get fewer and fewer pieces left to place, and a good manager will
> ensure that the last pieces fit, instead of being left with gaps when
> pieces do not arrive, or are the wrong size...
IMO, it makes more sense to focus on things with the most business value.
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