TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Subject:Re: TW Courses & Group work From:Brenton Faber <Brenton -dot- Faber -at- M -dot- CC -dot- UTAH -dot- EDU> Date:Fri, 27 Jan 1995 11:41:06 -0700
Marsha's comments about group work are certainly applicable. One of the
best strategies I've used is to ask students where in reality (and why)
one would work in complete isolation without integrating colleagues
and co-workers comments? I to make it not so much an issue of "force" but
of "quality"
Also, what works extremely well is to have groups design a binding
contract that will structure their work throughout the term. I review
each contract and make sure that it address regular meetings (# of hours
per week) leadership responsibilities, the division of labor among each
group member, and a grading system by which they will evaluate each
other's contribution to the group. By factoring the almighty grade I've
found that at least most give group work a try.
I still have yet to enjoy the "perfect" group work class -- but then
if fate granted me one it would probably take most of the fun out of
it as well.
BTW thanks for the comments about "Service Learning"
Brenton Faber
Brenton -dot- Faber -at- m -dot- cc -dot- utah -dot- edu
