> > hmmm... one sure-fire way for a working group to get into trouble is
> > for it to try to document current practice at the same time it's trying
> > to define what should be the practice. people in the group tend to
> > get the two confused and the result is usually neither an improvement
> > over the current practice, nor an accurate description of current practice,
>
> Which is why documenting current practice is separated from the development
> work in the milestones :-)
we've done that in a couple of other groups. what happened in those cases
was that it took a long time (> 1 year) to document current practice,
and everyone else in the group lost interest.
> One reason to document current practice is to get terminology agreement. Too
> much confusion is currently due to lack of "same language".
agreed entirely. I just think that the "document current practice" part
needs to be accomplished very quickly.
Keith
This archive was generated by hypermail 2b29 : Thu Nov 18 2004 - 11:21:25 MST