Deliverable | Person(s) responsible | Target date |
---|---|---|
Criteria to be analyzed | Zac | 10/2/02* |
Analysis methods | Vickie | 10/2/02 |
Objectives and goals | Nick with input from rest of team | 10/2/02 |
Audience definition | Shelley | 10/2/02 |
Usage scenarios | Shelley | 10/2/02 |
Competitive analysis | Shelley | 10/2/02 |
Site content | Amy | 10/2/02 |
Content grouping and labeling | Amy | 10/2/02 |
Functional requirements | Zac, Nick | 10/2/02 |
Project plan | Vickie | 10/2/02 |
Site structure listing | Nick | 10/28/02 |
Architectural blueprints | Amy | 10/28/02 |
Global and local navigation systems | Erin | 10/28/02 |
Status report #1 | Vickie | 10/28/02 |
Layout grids | Nick | 11/25/02 |
Design sketches | Erin | 11/25/02 |
Page mock-ups | Amy, Shelley | 11/25/02 |
Web-based prototype | Zac | 11/25/02 |
Status report #2 | Vickie | 11/25/02 |
Final version of website | Everyone | 12/9/02 |
Usability report for other group's site | All, Vickie will coordinate | 12/9/02 |
Final status report | Vickie | 12/9/02 |
Status report #1
The project is proceeding according to plan. Shelley has been helping a lot, even though she doesn't have something specific to do for this check-in. Amy and Erin are doing blueprints and navigation now (in a change from our original assignments) to better share the workload.
For the next check-in, the team is planning to start our tasks earlier since there is a lot more to complete. We also need to validate some of our assumptions from the first check-in regarding audience (Shelley) and customer requirements (Zac) to ensure we are developing the right product. We also reassigned the page mock-ups to Amy and Shelley to spread the work around more evenly. We will be figuring out some intermediate dates to ensure that Zac has time to do the prototype based on the rest of the work being done for the third check-in.
Status report #2
The team has done a great job of getting everything done ahead of schedule for this check-in. We have a lot of material put together and contributions from various team members regardless of who was assigned a particular task. Instead of figuring out a schedule to make sure we got things finished on time, we basically started as soon as the first check-in was finished and just built the various layouts and graphics we needed. We did some basic requirements validation with Dave (who gets to make the final decision about the style aspects of the site).
Our final task will be to work out who does what to implement the actual site for December 9. Our strategy is as follows:
Status report #3
The main task for the last two weeks of the project was getting the chosen layout implemented (our plan was that the home page layout and style sheet would be easily copied to complete the rest of the site). It took more work than we expected to make the layout implementation compatible with multiple browsers, but thanks to teamwork and some help from Dave it's in good shape. As mentioned in the previous status report, we assigned sections of the website to each person to be updated. Some members of the team wisely waited until the layout was finalized to do the conversion; others tested the layout, but had to redo their work when the implementation was complete.