Vitaliy email (remove spam text)
Olin Lathrop wrote:
>> I'm not advocating against planning per se, only excessive, overly
>> detailed planning that looks too far into the future, and is
>> therefore largely based on assumptions.
> Ah, see, in the end it all comes down to judgement calls you make based on
> things you've learned and you're experience. I'm sure everyone that is
> running a project thinks they are trading off too much planning with too
> little about right. The problem is you can't quantitatively measure this
> and decide where the right level is. Telling someone to plan, but not
> excessively or overly detailed is meaningless. You might as well walk in,
> tell them all to do a good job, then leave. Do you really expect them to
> say "Good idea, we didn't think of that"?
Olin, I don't know how you do your planning, but there is a big difference
between upfront planning, and "just enough" planning.
We do just enough planning for one iteration. There's nothing ambiguous
about it. We don't write specifications for features that will not be
implemented in this iteration.
Does this make sense?
This is similar to the YAGNI (You Ain't Gonna Need It) principle: you don't
program features that you think you may use, you only code the ones that you
know you're going to use.
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