Project Logs
Beginning with Week Three, you will post a weekly Project Report on your individual project blogs:
- Create a new post, titled Project Report, Week Three (Week Four, Week Five, etc.)
- Document and reflect on your weekly team-project participation: what were your contributions? (be specific) What’s going well on your team? What’s not going so well? What are your goals for collaborating and contributing next week?
- Pay attention to your audience: you’re essentially documenting internal team documentation for an external audience. This is not rare in technical communication, but it requires thinking about the needs, expectations, and biases of your primary audience — me, your teammates, TWC5/401 colleagues — and how the information might be received by unanticipated by secondary, tertiary readers. In terms of tone, aspire to professional and reflective.
Due: every Monday @ noon — feel free to post sooner, while the week is still fresh on your mind — reporting on the previous week’s project contributions and teamwork.
Evaluation: I don’t require a particular word count, but in my experience, you’ll need at least 2-3 fully developed paragraphs to deliver the necessary information: [1] what were your contributions (be specific)? [2] What’s going well on your team? [3] What’s not going so well? [4] What are your goals for collaborating and contributing next week?
While not required, you’re encouraged to integrate images — screen captures, sketches, prototypes — in your Project Report.
Project Reports that are posted by noon on Mondays and that demonstrate some level of detail in the required elements receive full credit; those that do not, do not.