Web Team Task Chart
|
Meet with client- The initial meeting with the client is used to gauge client needs and to decide if CAL is a good fit. It is very important at this stage that the webteam members make clear to the client how much involvement and commitment is needed in order to produce a website. It is best if the client has already filled out the questionnaire before the meeting so team members can review it and have some ideas of client needs before the first meeting. If things look like a go, the team manager should get a contract signed and set up a second meeting with the client to go over a project proposal.
|
Contract- This is an agreement signed by the client and the project manager stating that both parties agree to work together. It also states other agreements about responsibilities of both parties. This should be signed before any work is done. Contract
|
Comparative Analysis- The project manager will assign the task of researching several websites for content, structure, and design. Refer to the sheet on comparative analysis to see what kind of things you need to be looking for.
|
User Scenarios- The project manager will assign someone to write up scenarios for 3 different likely users of the website. The scenario should include how the particular user might use the site and what kind of information they may be looking for. The scenario should start with a description of the user.
|
Client Questionnaire - Use the form from the website. Have the client fill it out before the first meeting if possible. Questionnaire
|
Technical Specs- This lists all the special requirements that will be needed to complete the project such as php programming, flash programming, e commerce etc. Anything out of the norm that may need to be addressed.
|
Goal Statement- A short paragraph describing the purpose and goal of the website
|
Site Map- The site map should be included in the project proposal. It is important that before you even start the website you need to establish all the pages of the website and have a general idea of what will be on each. In order to do this you need to gather all the content from your client otherwise you will just be guessing about how many pages you will need.
|
Project Proposal- The project proposal is a very important document. It gives completion dated for the various stages of the website. It describes the website to the client before the work starts. It contains a site map that shows all the pages that will be part of the site. It also has a page-by-page list of every page on the site and a general description of what will be on each page. It should describe what pictures, banners, navigation bars, and content would be on each page. The overall look of the page does not need to be described yet. That will be done later. The proposal should have attached a list of all the content needed from the client. It is important to note that this document is a guide for how the website will be built. Any deviations from this document need to be approved by both the client and the project manager. |
| Content Chart- This can be pulled from the proposal. It is a page-by-page list of everything that needs to go on each page. For example if a certain picture needs to be on the page it should be listed. This acts as a guide for the person building out the site to make sure nothing is forgotten. |
Communications log- You should document every time you contact a client either by phone, email, or in person. Log
|
Design comps- you should produce 3 different versions of a home page to show the client. These don't have to be fully functional pages. They just need to have the layout and look of finished pages. The client will sign off on one of the designs or give some opinions of needed changes. Once a design is agreed upon production can begin. |
Template build- Before the content can be added to the pages a template page(s) need to be built. These are simply pages with all the banners, footers and navigation structure in place. Essentially everything but the content.
|
Graphics- The project manager will have someone design and build all the graphics needed for the website. These are handed off to the template maker.
|
Build out- Once all the graphics, content, and templates are ready and in place the team members will use the content chart to start building out the website.
|
Browser Check- The website should be checked out in the supported browsers after the templates are completed and again after all the content is added.
|
Proofread- The website needs to be checked for spelling and grammar errors. Dreamweaver has a built in spelling check. Make sure this is done.
|
Bug Check- Someone needs to go to every page and click on every link to make sure everything works as it should. |
Domain Name- Obtain domain name for client if needed. This can be done earlier in the process to make sure it's ready when the site is done.
|
Web Hosting- Obtain web hosting for the client. The project manager should offer a few different options for the client and help the client choose the one that best meets their needs.
|
Upload Site- Upload the site once the proofread and bug check are done.
|
Customer Feedback- The project manager should get feedback from the client once the website is online. A formal feedback form will be sent out by the project manager to the client.
|
Update Site- If we agreed to update the site for the client we will have an agreement as to how often and for how long we will do this.
|
Client Training- Our goal is to eventually have the client trained to take over and update their own website. Our job is to provide whatever training they need in order to make that happen. |
