Beta Release Report

• What did you learn when you asked a minimum of three volunteers to play/use your project?
• What changes have you already made?
• What further changes (prioritized from most to least important) will you realistically be able to make by the Dec 8 deadline?
• What additional changes would you make, if you had more time? (Prioritize these, starting with the first thing you would do if you had more time, and ending with more ambitious, long-term possibilities.)
  

Present your findings in the form of a short technical report. Length: 500 words of original analysis, plus some useful combination of screenshots, code samples, transcripts, video clips, etc., as needed to support your findings. (Link to a full copy of your beta release, and assume your reader has direct access to it, so there is little need for a detailed summary.)

A short technical report is like a news story, in that it is written in the inverted pyramid format, but unlike a news story in that you are not writing a technical report for the general reader. (For this assignment, you can go ahead and write for your classmates and for me-- insiders who know has happened in the classroom, rather than writing for an outside audience. Feel free to link to older blog entries that provide background information.)

A technical report would not focus on your personal journey of discovery, nor is it a reflective self-assessment. Instead, it focuses on how the process leads to the product.

Submit your report by e-mailing it to me. (You are welcome to post it on your blog, but I am thinking of this report as a down-and-dirty, practical, internal document, so it would not be of much interest to outside readers, and I don't think it would be the most productive use of your time to make this particular document interesting to outside readers.)