oooh - now there's an idea. a teamwork book! this board probably needs a separate teamwork forum to boot.
<ok, i'm ranting now - I'll stop in a minute..>
the whole teamwork concept requires one to *almost* completely re-think how architects traditionally think about their documentation needs. I'm not complaining, necessarily, just thinking out loud that such a paradigm shift might engender a few helpful.... er... flowcharts... or.... procedures... or the taking of our collective hands by the authors of this software. teamwork needs to be approached very, very, carefully! lots and lots of planning required before wading in - or a frustrating mess is the result. *especially* with a team of other architects in the room that need to pick up uh... pencils... mice... and get some good work done.
the "no drafting, only modeling" mantra I embrace, understand, and strive for. but on a practical level I sometimes feel that I may as well be training a room full of people to be an odd combination of bean-counting-higher-math-virtuoso-musicians given the level of skill and knowledge of the software required... all the tweaky toggles that need to be properly adjusted before anyone even begins work. and THEN... just when you think you've got it... we discover we're locked out of some crucial tweak in the settings so everyone takes a coffee break while the one or two people who really get it make the adjustments in views or whatever.
hence the need for templates... standards... procedures... deep knowledge of the manual. we *do* like the improvements in AC10 over previous versions... but still... sometimes we wish someone would throw us a bone...
<OK I feel better now>
Lep
