<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Rentz, Kathryn</title>	<link>http://tc.eserver.org/authors/Rentz,_Kathryn</link>
	<description>A bibliography of works by Rentz, Kathryn in the field of technical communication.</description>
	<language>en-us</language>
	<copyright>Copyright (c) 2005-08 by the EServer. All rights reserved.</copyright>
	<managingEditor>tclib-editorial@eserver.org (TC Library Editorial Board)</managingEditor>
	<webMaster>webmaster@eserver.org (Geoffrey Sauer)</webMaster>
	<image>
		<url>http://tc.eserver.org/images/newlogo.gif</url>
		<title>Rentz, Kathryn</title>
		<link>http://tc.eserver.org/dir/Rentz,_Kathryn</link>
	</image>
	<item>
		<title>Designing a Successful Group-Report Experience</title>
		<link>http://tc.eserver.org/34822.html</link>
		<guid>http://tc.eserver.org/34822.html</guid>
		<description>Report assignments and collaborative assignments can both be fraught with risk. Report projects, if notstration) and/or can leave students wondering what they are supposed to have learned—all while creating a major grading burden for the instructor. Poorly planned group projects can cause similar difficulties, with the added danger of creating interpersonal stress in the student groups. Yet for many reasons, the report assignment is the perfect choice for the collaborative project. Because of its extra length and complexity, the report enables several students to contribute meaningful research, writing, and document design decisions to one product or a related set of products. If the project goes well, each student will learn important lessons both about report writing and about teamwork. To maximize the likelihood that the project will go well, the instructor must think through a wide range of variables and decide, based upon his or her learning objectives, what the features of the project will be.</description>
	</item>
	<item>
		<title>The Importance of &quot;Niche&quot; Journals To New Business-Communication Academics— and To All of Us</title>
		<link>http://tc.eserver.org/34534.html</link>
		<guid>http://tc.eserver.org/34534.html</guid>
		<description>This commentary, extending one published in 2007, reports on a study of publishing advice being given to new academics in business communication. The findings suggest that &apos;niche&apos; journals such as the&lt;/it&gt; Journal of Business Communication &lt;it&gt;are very important to these academics&apos; professional advancement and are, in general, well regarded in the respondents&apos; host departments. Such journals are essential to the scholarly conversation in specialty areas that are not well served by bigger, mainstream journals.</description>
	</item>
	<item>
		<title>Adventures in Collaboration: The Story of an STC Faculty Internship</title>
		<link>http://tc.eserver.org/20546.html</link>
		<guid>http://tc.eserver.org/20546.html</guid>
		<description>Rentz relates the lessons she learned as an academic who contributed to a writing project for a private company.</description>
	</item>
	<atom:link href="http://tc.eserver.org/authors/Rentz,_Kathryn.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>