white paper project

Finally, A Final Draft

Attached is a pdf of the final draft of our white paper.  Have a great Thanksgiving break.

Project Log week 12

During this week, our group worked together in class to on developing a persona for the next portion of the project "usability". This was interesting because we had to make up some people that would need to use our technology that we have researched. Also, we got back the answers to the questions that we sent over to the Drive Through Marketing Team. I dont think that they liked us. They pretty much said that our technology was not what they were looking for. So Cat informed us that we would just be using our imaginary friends for the rest of our project. 

Project Log Week 11

I missed the group meeting on sunday because of work. My group excused me and accomodated me by sending me an email of my responsibilities for the upcoming week. Cody and I are supposed to research more on the collaborating issue and it to the introduction section that wrote up.  

~Andy 

Week 12 Project Log: A Slow(er) Week

This week was a relatively slow week for the white paper project as we were waiting for the return of our rough draft.  Today in class we divided up the portion of the executive summary which we will complete by Monday night so that I can combine them for class on Tuesday.  The only revisions not addressed in our meeting or previously were addition of a table of contents and correction of grammatical errors.

Week 11 Project Log: New deadlines and new directions

On Sunday, we met as a group to divide corrections we knew would be necessary before submission of the final draft.  Andy and Cody were tasked to work on adding more information regarding issues which hamper collaboration to our introduction.  Tianyi was to collect screenshots from each site and add the appropriate citation.  Finally, I was to add callouts for important quotes and to add the screenshots ot the paper.

Week 10 Project Log: Drafting and Redrafting

As requested, all three group members posted their first section drafts to Sosius so that I could have an idea of how to structure the conclusion, which was my section.  In class on Wednesday, we discussed the sections and decided that we needed to add some more information to the introduction as well as unify the main idea of our white paper.  The other three group members were given the following objectives (in order of importance) to complete by Wednesday at 2pm:

White paper rough draft...part 1

White paper rough draft, minus illustrations.

Communication

i've attached my part of the paper with visuals and references of the actual sites themselves from which the images came from

Project Log for Week 9: The Beginning of a White Paper

Our white paper began to take shape this week.  On Tuesday, we began working on our annotated bibliography.  Each of us choose two to three sources from those we had previously found and wrote a short annotation for them.  In addition, Andy worked on the conclusion and Tianyi assembled the final document.  Due to an error in the setup of our Sosius folder, we were not able to use this collaboration tool.  However, we communicated back and forth through email on Wednesday and Thursday, which worked fairly well.  I know that I was easily able to rely edited

English 421=Shipbuilding 101?

While I was evaluating potential strategies in my head, my initial response was to hang back and see what other people thought.  With such a large group of peers, no clear command structure existed, and I was hesitant to give my input for fear of appearing to "take control."  I think this observation applies to the white paper project, especially since we will be writing in groups.  While a rigid command structure is not crucial to group writing--and in the case of writing with peers may actually be detrimental--, a form of defined leadership helps
Syndicate content