Project Description

Building on the skills developed in the Employment Project and the Instructions Project, students in groups of four or five (groups appended below) will research and present technological solutions to specific, meaningful problems (e.g., problems of internet security, alternative energy, prescription medication options, etc). This project will result in one primary document, a White Paper prepared for a specific audience, as well as several supporting documents (project proposal, Gantt chart, activity reports and research reports). In researching, designing, composing, and revising the White Paper, students should keep in mind their primary and secondary audiences, as well as any tertiary and gatekeeping audiences. When composing the documents, students should pay close attention to:

• writing style (plain and persuasive)
• rhetorical moves made in composing the document
• technical definitions and descriptions
• the use of images, graphics, and other design features such as fonts, headings, margin comments, and sidebars

Additionally, students should consider the physical, political, economic and ethical contexts of their audiences.

White Papers are documents produced for decision-makers; that is, they work to structure decision-making through communication. They rarely tell an audience what decision to make; rather, their focus is on creating a framework from which decision-makers can make decisions. They provide tailored research, allow for different readings and readers, and account for each audience's unique context of use. Their style, as well, contributes to decision-making. Word choice, sentence structure and visual appearance all create an impression of the authors, their credibility and trustworthiness. Style also impacts the mood and mindset of the reader, which contribute significantly in decision making. This project asks students, in groups, to prepare a White Paper that allows a specific decision-maker to decide among competing solutions to a particular problem.

Groups

Group 1	jstn	JFlitt	breal	Jeff
Group 2	Ben	bpo	bjdunfor	ymyang
Group 3	jonesae	Isaac	ck86	nmhess
Group 4	Chris	Matt	Zephyrus	Matt2178
Group 5	grfnpt	Kristin	jrdavies	secolema
Group 6	DigtalSHU	Beachside32	TANoNati	Bill D
Group 7	Joey M.	estefano	HiggsBoson	Zebulon	Doddy
Group 8	ajwaters	dbasso	apersohn	Lpetrovi	winninraces

Email addresses are available on the Members page. Students may also communicate through instant messaging, the chat and wiki features of Google Docs, or anything else.

Deliverables

One: Project Proposal

Each group will deliver a 500 word proposal for its project posted as a blog. Proposals should cover the basics of the project (topic; potential sources of research; primary, secondary, tertiary and gatekeeping audiences; and document design). The proposal should also suggest a division of labor: who will be responsible for what (this should prepare the group to produce the Gantt Chart). The goal of this proposal is to interest the instructor in the project and persuade him that the project is feasible, valuable and in concert with the goals of the project and the course. Post (as a blog) by Friday of week twelve.

Two: Weekly Group Activity Reports

Groups are also responsible for weekly activity reports (300 words) in order to keep the instructor abreast of progress the group has made over the week. Group activity reports (submitted as a blog) are due by midnight, each Friday, starting with week twelve and concluding in week sixteen.

Three: Weekly Individual Activity Reports (Work Blogs)

As the course and the professional world stress the value of documenting work processes, individual students are required to keep weekly work blogs of the tasks they have completed. These activity reports or "work blogs" (200 words) should briefly and professionally describe work done and how this work contributed to the goals of the group. Students will post and clearly label five work blogs by Sunday of each week of the project starting in week twelve and concluding in week sixteen.

Four: Gantt Chart

In a thoroughly executed Gantt chart, students should layout group tasks, a time table for the completion of each tasks, and the individual responsibilities of each member. (Information about constructing Gantt charts will be provided.) To produce the Gantt chart, groups must identify specifically what each group member will be doing at each step of the process. Post (attached to a blog) by Wednesday of week thirteen.

Five: Thumbnail Design Sketches

Each group member should prepare at least one thumbnail sketch of the white paper and post them to his or her blog (some examples will be provided). Each group member should then review and comment on the thumbnail sketches of their fellow group members to negotiate a consistent look for the white paper. Thumbnails should be posted (attached to a blog post) by Wednesday of week fourteen.

Six: Research Blogs (Activity/Analysis Reports)

Each group member is responsible for a minimum of three research blogs. These blog posts (250 words) should summarize and analyze relevant research in the context of the project and suggest ways in which the content can be incorporated into the documents (as text, as a sidebar, or as an illustration). (Handouts and samples will be provided.) Research blogs must be completed (and properly categorized) by Friday of week fourteen.

Seven: White Paper

Groups will design and compose a professional quality white paper (1600 – 1800 words) that lays out three to five researched and viable solutions to their chosen issue or problem for multiple audiences. The document should structure the decision-making process by framing the issue and providing options without advocating for any one solution. Draft Day: Friday of week fifteen. Final Draft Due: Friday of week sixteen.

Eight: Collaborative Project Evaluation Form

Group members are asked to complete the Collaborative Project Evaluation Form to assess their collaborative experiences, the effectiveness of the group, and the contributions of individual group members. Students are also asked to “sign off” on the work blogs of their fellow group members, verifying that the work each describes is work they actually completed. Evaluations are private, and should be emailed to the instructor by Friday of week sixteen.

Grading

The White Paper Project is worth 25% of the final grade. The breakdown for each of its components is as follows:

• Individual Component: 30%
  • Research Blogs: 10%
  • Individual Activity Reports (Work Blogs): 10%
  • Thumbnails: 5%
  • Collaborative Project Evaluation Form: 5%

• Group Component: 70%
  • Group Project Proposal and Gantt Chart: 10%
  • Group Activity Reports: 10%
  • White Paper: 50%

White Paper Grading Criteria

• Style is plain and persuasive when and where appropriate and is in sync with the expectations and needs of the various corresponding audiences
• Document (in all aspects) accounts for primary, secondary, tertiary and gatekeeper audiences
• Words, graphics and illustrations all compliment one another
• Graphics and illustrations are consistently numbered and labeled, and are provided with captions and/or descriptions
• Headings are succinct and create multiple access points for readers
• Design features such as sidebars, margin comments and pullouts produce unique and additional access points for readers
• Overall design follows Johnson-Sheehan’s five principles, makes document easy to understand and scan, and creates a persuasive professional impression
• Technical definitions and descriptions are correct, concise and appropriate for the audiences
• Purpose and intent are clearly stated and defined, as is the issue or problem
• Each section of the document has a clear introduction, developed body and a concise conclusion
• Specific information and sources are documented thoroughly, consistently, and unobtrusively (we suggest using MLA-style footnotes)