D#14 HW#2 Presentations

Pg. 392 “Determining your Purpose” — This section in the HTW asks to first write out the purpose of your presentation.  It also gives a useful sample purpose statement.

Pg. 393 “Structuring the Presentation” –  As usual with the HTW, a sample structure is given for a task.  The presentation section in no different.  It presents a sample structure with information to help when creating your own presentation.

Pg. 395 “Using Visuals” –The information presented here is similar to CH. 23 in the text.  However, it goes into further detail about ideas regarding certain visuals such as flip charts and slides.

Pg. 400 “Presentation Anxiety” — “Know your topic thoroughly” as written in the HTW as a way to combat presentation anxiety is some of the best advise one could have.

D#13 HW #3

I have chosen this new theme because the layout is very easy on the eyes and is easy to follow.  It is one of the few themes that follow the C.R.A.P principles in my opinion.  The first widget I implemented is s monthly archive of your my blog’s posts.  This is a practical archiving system for my blog posts.  The second widget is a calendar of my blog’s posts.  This is a great way to quickly see what posts were sent on a particular date.  Although there are only a few “reflection” blogs I felt the need to make a category for them.  There are many deadlines asking similar reflection questions.  Blogs dealing with projects 1-3 is an important category for organization and quick access.  Blogs regarding project are the ones I  refer to the most.  I felt the other blogs were not consistent or obscure enough to make another category.  I thought about a mindmeiser category and a text category but I want to keep the categories to a minimum.  The last change I made was to make a personal profile. I believe it will be helpful in the group activity project for group contact.  My blog is now easier to access information from for peers and others.

D#10 HW #2 Team Writing

Pg 109 “A teammate disappears completely”  — This advise may come in handy if the situation presents itself.

Pg 111 “My team doesn’t trust me to do good work” — Hopefully this wont be a problem but this section has some legitimate advise.

Pg. 105 “A teammate misses a meeting” — Lays out some appropriate techniques in dealing with this situation.

D#10 HW #1 exercise #1 response

I personally favor the holistic problem-solving approach.  This  style considers the entire problem as a whole and refrains from proposing solutions  until the problem is completely understood.  The action-oriented style seems to based on resolving the problem quickly rather than efficiently.  However, many will find the holistic approach to actually be quicker in the long run.  If the problem is not completely understood in the beginning, it could cause more problems later.  I find I am usually an action-oriented problem solver but strive to be a holistic one.  When it comes to speech I rely on a mix of the competitive style and the considerate style.  It is completely situational when to use each style.  Although, there have been times when a project needed to be completed quickly thus the competitive style increased productivity.  The competitive style can increase productivity but can interfere with quality.

D#8 HW#4 & 5

HW#4

These are links to the drafts I have commented on:

1.  http://khantwc301.wordpress.com/2010/03/22/d7-hw6-project-3-draft/#comment-22

2.  http://andybloodtwc301.wordpress.com/2010/03/25/deadline-7-hw-6-usability-test-draft/#comment-7

HW#5

After reading some drafts I got some good ideas for my own project.  Everyone is coming up with good ideas.  It was unanimous for everyone to have some kind of questionnaire asking the tester’s background.  I need to implement more details into my project to insure better test results.  I believe an adequate survey for the test subjects will be an important factor. I may also want to consider increasing  the number of test subjects to insure a wider range of results.  Keeping the test short but precise will also require more pre-planning.

D#8 HW#3 Group Work

Group projects I have done could have been more successful if the materials from the Team Writing text were used.  In my history class in high school, groups of four were assigned to write a report and present a powerpoint on campaign spending.  Even though I knew my group members very well, working as a group caused us to knock heads through the entirety of the project development.  In my opinion, the most important aspect presented in the Team Writing text that could have helped us was the Team Charter section.  As a team we had no pre-planning regiments.  We were eager to charge ahead and start productive work right away just as the text describes.  If we had made a document that described the goals and priorities of the project, everything we were trying to achieve would have fallen into place.

D#8 HW#2 Comparison

Both texts provide valuable information on writing many types of proposals. The proposal section of the HTW is one of the largest.  Both the HTW and TC texts go into detail about the types of proposals one can use.  The TC mentions a few types of proposals not discussed in the HTW such as grant and research proposals.  The HTW gives more examples of proposals and has a deeper logistical way of approaching proposals.  It discusses many aspects such as audience and purpose when considering a proposal.  The HTW also goes into fine details such as headings and text locations.  Both the TC and HTW provide understanding of writing and choosing proposals.

TC Ch. 20 and HTW pages 412-433 were used

D#7 HW#6 Project Draft

• Title Page- Google Voice Usability Test
  
• Table of Contents- Will list the section below as well as separate pages for each user
  
• Executive Summary-
  
• Introduction- This will state the current status of the instructions and the purpose of the usability tests
• Usability Team- Myself
  
• Test Parameters- Three students will complete the usability test. Google Voice is not a very complex application so the test subject will only need a few minutes to complete each task.  They will be able to use their own computer/laptop or request to have one provided.
  
• Usability Test Plan (as a part of the larger usability report, not it’s own report)
  • Statement of Purpose- To improve and update the instructions
    
  • Test Issues & Goals- The test will allow the user to provide feedback and help improve the instructions.
    
  • Test Environment- Will all be in person with a laptop or computer
    
  • User Profile- Two college students and a non student
    
    • Participant Recruitment Plan- Use people I know
      
    • Participant Screening Plan- My knowledge of their technology skills
      
    • Consent Form/s- Perhaps a screening test of the subjects knowledge of Google applications and or computer skills will be issued.
      
  • List of Participant Tasks- Follow the instructions given and complete the task
    
  • Methods of Evaluation
    • Data-Collection Form/s- Survey and comment sheet
      
    • Posttest Questionnaire/s- Maybe
      
• Test Results (as a part of the larer usability report, not it’s own report)
  • Methodology (what you actually did, emphasizing anything different from your plan)- Pending
    
  • Results- Pending
  • Conclusions- Pending
• Final Recommendations

HW#7 D#4 Presentation

For every application both texts ask to consider your audience.  Both the HTW and the TPCW texts ask to account for varying levels of expertise and interest in your audience and provide solutions for their problems.  TPCW goes into more detail about certain aspects to consider for a formal presentation in comparison with an informal presentation.  Preparing for a presentation requires gathering information.  Both texts stress too much detail could overwhelm an audience but too little will not full fill the audience to support your recommendations.  Structuring the presentation is discussed in great detail by both texts.  Like any research paper, both texts agree a presentation must be divided into three sections; Introduction, body and closing.  The ideas of presenting the information vary slightly in the TPCW but really have the same basic principles discussed in the HTW.  The TPCW goes into more detail about recommendations for types of visuals to be used in a presentation.  Two key points to consider according to the TPCW when presenting visuals are to narrate the visual as you present it and combine text and images for dynamic effect.  Considering organization is presented in the TPCW but if all the steps are followed in the HTW organization will be the least of your worries. The same basic principles such as the use of eye contact and movement for the actual presenting are discussed in both texts.

Chapter 23 of the TPCW and the “presentation” portion of the HTW were used.

HW#7 D#3 Ch. 12

As discussed in the HTW, memo format can be used for short reports, proposals and other internal documents.  There are different methods of writing memos which are presented.  The TPCW text gives insight to the logic behind writing an effective memo.  Considering memos are often skimmed, info should be easy to find, clear, and concise. Both texts mention the common length of a memo to a single page. The TPCW goes in more detail of various types of memo formats such as response memos, which give answers to previously asked questions.

E-mails are discussed in detail in the HTW. It goes over design considerations, ethics and even sending attachments.  Both the HTW and TPCW  ask the writer to consider the proper tone and degree of formality. Keeping e-mails short and to the point are also techniques stressed in both texts.  The HTW has a more directed and billeted step-by-step system for reviewing your first e-mail draft while the TPCW is more explanatory and also logical.  Both have detailed sections on greetings, closings and signatures.

Chapter 12 in the TPCW and the Memo and e-mail section of the HTW were used.