Requirements

Here's what I want by midnight on Friday, July 6 (you may turn it in sooner):

A "Project Forum" discussion board post saying the team's final selections for each of the four deliverables is ready to be graed. Here's what we've done so far: site scope, site map, application flow and wire frame.
Post these final deliverables on the relevant team link on the project wiki.
If your team wants to request a re-grade for any deliverable, have one person post a comment on that deliverable in the wiki stating what the team changed from the original and why. I would also like to see a link to the original which is in your various assignment wiki "team version" folders

Just copy and paste the link from the original assignment wiki into the re-grade request comment.

Each person on the team must have a deliverable used by the team, however you don't have to use the ones you originally selected.
I will grade the entire set of deliverables against the same criteria used for each deliverable in the course.

Tips:

Unless I see a re-grade request "comment" on a particular deliverable, I'll assume the team is content to "let it ride." If so, I'll simply transfer the team grade from that deliverable into the team's final, collected set of deliverables.
You have the benefit of feedback I've given on individual deliverables. If you want to "re-select" whose deliverable gets used, that's fine, but anyone on the team can revise it. Perhaps you want to select one as a base, and then the team revises it to more adequately represent the team and meet the requirements.

Caution: If you change whose deliverable gets used, make sure you revise other deliverables accordingly, so there is an underlying "consistency" between all deliverables, which is the primary value of this collected set of deliverables. For example:

Site scope strategy recommendations are represented in site map;
Site map establishes ID system used by the app flow and wire frame;
App flow fleshes out interactivity defined by site scope and site map;
Wire frame provides an "architectural perspective" of key pages (not all pages).

Since I plan to archive the project wiki and share it OIT's Jack Suess and Collier Jones, I would like to see all deliverables transferred from a Word or PowerPoint format into some kind of web accessible "object" or format. This means converting the site scope to a wiki page. I think you can do the same with the App Flow.

The site map and wire frame assignments represent unique challenges because the PPT images need to be converted to images and resized. Ben has agreed to do this for Team 1, and I'll do it for Team 2 (unless someone wants to volunteer). It's not difficult, but it will make the final version easier to read.

If you have comments, questions or concerns, post them on the "Questions" Forum.