Web Proposal Lesson - main page

To sign up for a Web Proposal Meeting visit the class message board and select the post titled "Web Proposal Sign Up"

Web Proposal Evaluation Sheet I wil be using during our meeting. I will bring 2 copies of this form to the meeting.

I am assuming that all members of your team will be attending the meeting, let me know if we need a CCC session during your meeting.

Instructor's tips for a successful proposal

Overview of Web Proposal - The Web Proposal is a printed document which is provided to the instructor. All of the items in this Web proposal are also a part of the" project site". Many students find it easiest to create these documents as Web pages and print them out for the Web Proposal meeting.

Although the Project Manager compiles the Web Proposal, they are not responsible for creating all of it's elements. As you review the elements of a Web Proposal there will be initials next to each item to determine who should provide that element. Since many of the elements of the Web Proposal are contributed by others, I recommend you set an internal deadline which is 3-5 days ahead of the class deadline.

If a piece of the proposal which is contributed by a classmate is not done by the due date, your grade will NOT be affected. Do NOT make the missing element for your teammate, it is not helpful and makes my job as the teacher much harder. If a team member does not provide the required item, the team will still meet with the instructor to review the proposal.

Web Proposal Elements

  • Contact Sheet (PM) This ia a page that includes the names and contact information for the client and the team members view example
  • Strategic Brief (PM) This is a document which describes the organization, lists the goals and objectives of the project, documents the tone and message of the site and describes the site's target audience:
    instructor guidelines for strategic brief
    TLT example

    Puente example
  • Deliverables (CD) this is a detailed list of what the client will receive include the number of pages, the images you will provide, any scripts you create, PDF files, training, marketing, etc. Make this document very detailed to avoid confusion later.
    Soco example
    view TLT example
  • Storyboard (DES) This is a series of boxes which are a picture of the site. Use one box for each page and show the hierarchy and structure of the site.
    view Friends House example
  • Production Standards / directory structure chart (CD) This document contains a written description of how the HTML files will be named, and created. Where will the images be stored. Finally show where all the files for the site will be stored. This document helps the Designer and Content Developer understand where all the files are put and what the linking code should be.
    TLT example
    Soco example
    view Friends House example
  • Workflow Plan (PM) This explains who does what and when it will be done by. The form was created by FANHS and suited the needs to their client, feel free to modify it to meet the needs of your project. FANHS Workflow Plan by Larry Roberts(excel spreadsheet)

    Another resource is the Workflow Plan (word file) provided by the Professional Web Business Tools site
  • Content Status Chart (CD)
    This is done by comparing the content you have been given to the storyboard which is developed. Ask the designer for a copy of the storyboard and then analyze the content the client has supplied. Indicate if you have all the content for each page, if you do not, list what is missing and indicate what date the content will come in.

    There are 2 deadlines which deal with content (see milestone chart). Before the PM updates me on the status of the content they will check with you. Make sure you have opened every file and read through the content before you say we are "good to go". sample content status document (Word)
  • The shell site (CD)
    This is a web site which has the content displayed on all the pages which will eventually make up the site, but does not look like the finished product. The pages are plain white pages, with black text, and blue links. The purpose of the shell site is for the Content Developers to become familiar with the site and for the client to get a preview of how the site will navigate and flow.

    This project begins as soon as content is provided by the client and will hopefully be done before we begin actual site production. If the shell site is not done by the Web Proposal meeting that is OK, but I will need a list of contant that is missing (see content status chart)
    Examples of a shell site
    TLT shell site || Kenwood Pillow Fights shell site
  • Contract (PM) This document explains what the team will do and what the client will do in return. Please ask to use this site in your electronic portfolio, ask for letters of reference, and a link at the bottom of the pages crediting your team and the SRJC Web Development Program
    view instructor example you may also want to consult the Web Development Contract provided by the Professional Web Business Tools site.
  • Site Comps (also called Mock Ups) (DES) - A mock up is a picture of what the finished web pages will look like, it is not an actual sliced web page. The mock up is a template which has HTML and CSS and inserts "pretend text and images to simulate the look which will be achieved at the actual site. Another approach is to create a flattened GIF or JPEG which is created in Photoshop and then optimized for display on the Web. After the client approves the mock the template of code or PSD image will be refined into code which will be used by the CDs to create the site. These documents may prove useful to the designer learn more about comps || review design standards
  • Creative Brief (DES) - This document serves as a written explanation and justification for the design you created. Often a large client will receive more than just graphical mock ups, they will have a multi page proposal which explains how this design ties in to the existing corporate look and satisfies the company goals for the web site.
    Guidelines for the Creative Brief || HCA || SRJC Culinary Academy || Art Quest
  • Multimedia Comps (IMD) - A mock up is a picture of what the finished multimedia elements will look like, it is not an actual Flash animation or video. The mock up is aseries of screen shots a few of the screens that will be used to make the Flash animation or effects of the edited video (title screen, lower third, ending credits). A description of the transitions, music, or additional effects will be included in the Creative Brief listed below.
  • Creative Brief (IMD) - This document serves as a written explanation and justification for the multimedia elements you plan to create. Why did you select the slide show interface and colors? What is the goal of the flash animation and why did you select the images and text which will be used. What will be used to play the videos, if you will do video editing, what will be the guidelines you will use to create the finished video.
  • Technical Brief - (PROG) This report explains what the programmer will be creating, where the scripts will be stored, and why the programs have been created as they have. || view TLT example ||