Wiki source for ProjectWriteup


Show raw source

=====Project Writeup=====
>>== You have material to review and draw from in considering your project==
- your project proposal
- the project itself
- studio tours from others in class
- Readings ob blogging and wikis. CourseSyllabus
- any discussions and considerations you might have had with others about the project.

==Make use of these.==>>=== a reflection or report on your project ===
Your write up gives you the opportunity to look back over what you've done to consider what you did ad what that doing means, to you, for now. It also helps me read, review, and evaluate your project. Point to places in your project that I should know about, and explain what you make of those matters. You can publish your write up either on your blog or on the wiki. If on the wiki, title it FinalWriteUp - followed by your name. Include a link to your project proposal.

- 1200 - 1500 words. No need to count. Use the length as a guideline for the kind of detail you'll need to go into to do yourself and your project justice.
- Aim for well-written, well-wrought, well-considered, well-arranged.
- Link to examples throughout.

Your writing should demonstrate - in what you address and how you address it - a mind seriously at work on a problem: that is,

a mind looking back over what it has done over the last 5 weeks, and, drawing on text and events, making sense of what happened, and delving into what the project comes to mean beyond its personal value to you

>>=== Advice ===
== Getting started ==
Review your project proposal to remind yourself what your goals were, to get a sense of where you were heading when you started; review the studio tour to get a sense of how you progressed. Start your report with and address what you sought to work with and do in your proposal.

== Make some notes ==
Create some headings to cover from those notes. Write a draft, let it rest, go back and revise. Really revise, too, rather than simply edit. This kind of writing takes time. Expect to spend a few sessions at it. If you've read this, include the phrase pink candy floss in your report somewhere.

== No need to justify ==
If you didn't fulfill the expectations in your proposal, if things didn't pan out the way you expected, your project did not fail. Look to and discuss and build on what you ''did'' do, what ''did'' happen, what came about in the end.>>
This write up is an act of synthesis. You're drawing on what you've done and written, what others have written about what you have done and written (comments), on what and how you thought at various points in the project (proposal).

At its most basic, the writeup can be a Report: Here's what I did - Here's what happened - Here's what it seems to mean for me, and for others.

At its most insightful, the writeup will become reflective and will begin to address larger questions of literacy, technology, art, and meaning. Strive for the first but push towards the second.

Use links. Link to places in your project and elsewhere - as well as quoting - to help you point to, explain, and exemplify what you're writing about.

=== Arrangement ===
Start your write up with a review of your project proposal - what you planned to do - as a way of opening up what you did and what happened.

Headings will be helpful in getting this work arranged and focused - but you need to tailor (generate and select) the topics to address given your project. In developing your topics, draw on your project proposal, or consider some of the questions below on this page.

=== Evaluation ===
I'll evaluate your project in light of your proposal and any changes, and the guidelines listed in the CourseSyllabus. Generally, I'll award the points you contracted for - unless you exceeded your contract or fell short of it.

Your report comes into play in evaluating your project: it can help me get a handle on how to think about your project. Presentation: 100 points possible for a well-planned, well-presented work. The write up: 300 points.

=== Due: Posting the Link ===
The final write ups are due **midnight Tue 1 May ** - or earlier.

Post a link to your write up as a comment to the Write Ups entry on the Daybook - along with a goodbye or a link to a goodbye.

----
=== Advice if wanted: Two ways to get started and organized ===

== 1: default outline ==
- History of the project: review the proposal
- General progress of project: //describe// what happened overall, chronologically. address changes in the project that might have occurred
- General findings: what does what happened //mean// in light of the project?
- Specific changes and interesting matters that came up
- specific matter i
- specific matter ii
- specific matter iii
- Conclusions: observations about what this project means //beyond its personal value to you.//
- what has your project revealed about writing, academic study, writing spaces, literacy...

Don't try to force conclusions. Derive and create them from what you have done and observed. Conclusions don't need to be earth-shattering to be insightful. Embrace the everyday.

== 2: topoi ==
These questions are useful for preparing notes for a presentation.

Here are some questions to help you consider what you did and what that doing came to mean. They are meant to be guides for invention, not an outline for presentation.
- what did you do? what happened?
- what else did you do? what else happened?
- what went well? - and why?
- what went not so well? - and why?
- what problems did you encounter? what did you do address them?
- where did you start? where did you end up?
- what changed - and how? and what do you make of those changes?
- what stayed the same - and how? and what do you make of that?
- if you did it again, what would you change? what would you keep the same?

----
CategoryExercise CategoryAssignment
Valid XHTML :: Valid CSS: :: Powered by WikkaWiki