redguru said:
I can't access that, I'm not a Purdue student.
Dammit, lol.
Tutorial Project
view track
Submitted by zamierowski on Wed, 2006-02-01 11:09.
Technology changes. Rapidly. Whether we like it or not. And whether you like it or not, you may well find yourself tagged as an expert in technology transfer for the workplace of your dreams (or worst nightmares). Such is the lot of the engineer, the technician, the technical writer, the college kid with the Purdue degree in one or another high-end major who was hired on the strength of his or her purported new-fangled know-how.
The Software Learning Initiative project is designed to propel you into just that dicey situation and to compel you to deliver your knowledge (no matter how recently & painfully acquired) to an audience of novice software users completely, concretely, and convincingly.
Context
For the duration of this project, you will work in teams to prepare tutorial presentations of software that all of us may find useful for completing assignments in 421. Mark Zamierowski will be your project leader. He gets really ticked when people misspell his name, and he thinks he knows a lot more about the software that everyone in the class will need to use than he actually does know. Never challenge him on this: he's really touchy.
Touchy or not, he knows his staff. He knows that he wants them to be comfortable with the Adobe and Macromedia design software in the HEAV 227 department, and he knows that he cannot possibly run one-on-one training sessions with the entire department. Hence, he has divided the department into instructional teams, each team being responsible for learning and teaching basic to intermediate applications of the available design apps. His hope is that this division of labor will encourage both general awareness of the potential of each application as well as a comfortable working atmosphere based upon fluid sharing of knowledge and know-how.
Project Deliverables & Timetable
The following deliverables must be submitted on or before the deadlines listed below in order to receive grades for the HEAV 227 Software Learning Initiative:
2/10 informal proposal Email your informal proposal to the class mailing list.
In your proposal, identify the program that you will be presenting as well as the specific focus of your tutorial.
Also, explain how your audience will benefit from attending your presentation.
2/20 working script & mock up of quick reference card Submit as hard copy a detailed script for at least 50% of your tutorial.
In your script, include what your presenter(s) will say, visuals that will accompany the presentation (and segways to those visuals), steps and checkpoints for keeping your audience on track, and any other notes for your presenter(s).
Submit a mock up of your quick reference card along with your script, also as hard copy.
2/27-3/3 tutorial & presentation with quick reference card Each tutorial should last 20-25 minutes.
Each tutorial will be an oral presentation of visuals & text either on Power Point slides or on linked web pages. Each team will decide if one or multiple presenters will deliver its tutorial.
At the end of your tutorial, submit hard copies of your final script and quick reference card for evaluation.
2/27-3/3 zoomerang evaluations After you present your tutorial, send an email to the class list requesting an evaluation of your team's performance and materials. The team member responsible for setting up the Zoomerang account may need to email all results to other team members.
3/6 post-mortem memos
(individual) Using your team's Zoomerang responses as a guide, each team member will submit a well formatted memo assessing the team's performance and materials as a whole as well as evaluating each team member's contribution to the success of the team's performance and materials.
Project Resources
The following online resources will be valuable for planning and drafting materials for the Software Learning Initiative. Remember that useful information, like existing tutorial tips, for some of the HEAV 227 design software is also available through the help menus of the various applications.
Inside PWO:
Oral Presentations 1.9
Types of Oral Presentations 1.9.4
Informal Oral Presentations 1.9.1
Tips for Giving Oral Presentations 1.9.2
Instructional Documents 1.8
Quick Reference Documentation 1.8.1.1
Tutorials & Training Sessions 1.8.1.4
Template for Instructional Documents1.8.2
Sample Tutorial Script 1.8.3
Worksheet: Starting Documentation Projects
Proposals 1.10
Rhetoric of Proposals 1.10.1
Types & Contexts of Proposals 1.10.2
Content & Organization of Proposals 1.10.3
Outside PWO:
Audience Analysis
— David A. Mc Murrey
Task Analysis
— David A. Mc Murrey
Proposals
— David A. Mc Murrey
Instructions
— David A. Mc Murrey
Oral Presentations
— David A. Mc Murrey
Creating Effective Online Surveys
— Senior Corps Tech Center
Survey Research Strategies
— William M.K. Trochim
Zoomerang Surveys
Grading
The Software Learning Initiative project is worth 20% of your final grade. The breakdown for each of the project deliverables is as follows:
Informal Proposal 10%
First Draft Script & QRC 20%
Presentation & Script 30%
Quick Reference Card 20%
Zoomerang Evaluation 10%
Post-Mortem Memo 10%
Final 100%
Notes
Every one of the six major deliverable sets must be submitted on time to be included in the final grade for the project. Any late or improperly submitted deliverables will receive a zero. Those zeroes can seriously diminish a final grade, and any improperly submitted deliverables will affect the grades for each member of a negligent team. Be absolutely sure to keep lines of communication open among team members, and be sure to follow up on the responsibilities of all team members to insure that all deliverables are submitted properly and in advance of each deadline.
» printer-friendly version | add new comment | 193 reads
