Project Workbook

You're going to create a project workbook that summarizes your work on the web page.  This is an ongoing task.

By the way, did you know that a "usable" project workbook is a best practice?  You probably do, but it's something you can read about in almost any software project management book.  I have one beef about some of these books...sometimes they want documentation that is overly detailed.  Some of the really detailed documentation should be put into a separate section.  The project workbook should be something fairly understood by almost any tech savvy professional whether they be from the IS or Marketing. 

It also serves as a record for your customer.  If your customer is a part of your team (just like in JAD), then they'll be viewing it.  Before each mini-mortem, the workbook should be reviewed, and certainly before the final post-mortem?  Your group members may wish to review the material before meeting.

Required Elements

1. The initial description of each customer and their relationship to you.
2.  Initial and any revised Prospectus. 
2. The goals of each web page
3. The interactions with your customer.  What was asked and what was learned? What techniques were introduced? (e.g. Extreme choices? Image Customer?) What prototypes and storyboards were presented?  Customer reaction to these? 
5. The intermediate design snapshots
6. Process Map (flowchart or swimlane. Use the one that is most appropriate)
7. Ongoing decisions and mini-mortems. This should include experiences and modifications of agile development techniques.
8.  What agile techniques were used?  How did your group enjoy pair programming?  How would you modify it?  How did your group carry out a scrum (or scum)?
9. Final delivered web pages.
10. Post-mortem comments by team members.
     a.  This should include a comparison of your experiences.  For example, how did the special tactics change things (if at all)?  How might these work with a larger project?  The post-mortem should also include what you would do differently. 
    b.   Let's pretend you get to create a project template for your project team.  This means you get a second chance at conducting these web page projects (you get to do Project 2.0), or perhaps, your team gets to conduct a much larger student project..  What would you like to enshrine as part of your team's practices...especially with the customer?  Any things you would change?