Website Planner- Website Budget Tools

When we build a website its imperative to plan it properly. It's really no different from any building project when you plan it well in the beginning you will maximise the chances of a successful web design project that comes on time and on budget.

 

---

Technologies’ e-business / Software / Web Design-Development Process  

 

Phase I: Preproduction

Phase II: Production

Phase III: Release

Phase IV: Maintenance

Phase V: Evaluation 

 

---

 
Phase I:  Preproduction 

 

1. Project Clarification

 

i. Understand the needs and reasons for requiring web design work
 

• Define goal
• Specify audience
• Specify site requirements (wish list, nix list)
• Prioritize

 

 

ii. Prepare a project brief to summarize the project

 

iii. Develop a generalized web strategy based on the clients needs

 

iv. Consult with technicians and programmers to get rough estimates of the time involved. 

 

v. Prepare an outline budget and schedule if applicable.

 

vi. Client sign off.

 
2. Solution Definition

 

i. Decide on technical solutions to meet client needs (e-commerce, search engines, uploaders)

 

ii. Use the strategy to develop strategic objectives that will clearly meet the clients needs

 

iii. Choose a project manager and ensure the appropriate personnel are available to complete the objectives. Also assign point of contact from the client who can validate work and project changes.

 

iv. Create a design concept (mock home page or several pages). These pages will be made available online to the client. However, these pages will not be a “live” site.

 

v. Client signs off on these solutions

 

3. Project Specification (the Contract)

This will be where costs, schedule and deliverables are all clearly defined for the entire project.

This document should include the following:

i. Version control – The original Project Specification is of course 1.0.  Additional modifications by the client or Prospect will be documented so that a history of changes can be clearly traced.

ii. Functional Specification - This will explain what the site will do from a users point of view.

iii. Technical Specification - An explanation of the technical solutions provided in the site.  It will also include a map of components and how they interact.  The complexity of this explanation and map will vary depending on the complexity of the project. 

Points it covers include: software used and purchased, operating system site will be hosted on, what web browsers will be supported, native resolution, where will the site be hosted, security provided etc.

iv. Content plan – This will describe which content Prospect will provide and its format (HTML, word, excel, PDF etc) to be included in the site It will also state any content required from the client and when the content should be delivered to Prospect.

 v. Testing Plan – This will outline how the site will be tested and accepted.  It will clearly layout the customer’s requirements for acceptance and completion. Criteria to be considered will include load testing, security checks, functional operations and end-user testing.

 vi. Updates and Maintenance – A plan and schedule for updates will be laid out as clearly as possible.  This will include rates for updates, time frames for posting them and the scope of the updates.

vii. Budget and Schedule- How much will the site cost?  This will include as much detail as possible (including production milestones and payments due milestones).

viii. Client sign off on Project Specification to begin work.

 

---

  
Phase II: Production 
 

1. Content

i. Gather content to include all images, documents, reports, audio and video files to be used in the site. This also includes information required from the client.

 

ii. Story board the website to make sure that a solid concept of the user experience is clearly laid out. These storyboards need not be elaborate, simply enough to give a frame of reference to design in.

iii. Solidify the navigation method and create a site map. The site map is an outline, blueprint or flowchart of the web site. The objective is to map out all the components of the website, so the development team has a firm overall idea of what the site will contain and how the pages inter-relate to one another. 

iv. Have the client sign off on the site map

 

2. Design and construction

i. Create template pages without graphics to show the client how the site layout will work

 

ii. Get Client approval of layouts

 

iii. Add site color scheme to layouts

 

iv. Get Client approval of layouts

 

v. Graphic Design using all of the above gathered content, maps and layouts. Create graphics for the site.

 

vi. Get Client approval of Graphic design and the site

 
3. Testing and hand over

i. Functional testing of technical solutions

 

ii. Load testing (if applicable)

 

iii. Security testing (if applicable)

 

iv. User testing

 

v. Client sign off on site usability

 

---

Phase III:  Release 
 

1. Transfer of site to live server(s)

2. Ensure the client has a complete copy of the site on disk or CD

3. Train users on site operation

4. Handover of site documentation

 

---

 
Phase IV:  Maintenance 
 
 

1. Refer to Project Spec for maintenance schedule and content 

2. Ensure the project manager is familiar with the client’s point of contact for updated content

3. Ensure the client is aware of the time frame, schedule and cost of updates

4. Post updates in a timely fashion

 

---

 
Phase V:  Evaluation 

 

1. If necessary perform project review

 

 

i. Show where the project started

 

ii. What the project objectives were

 

iii. Demonstrate the final product

 

 

 

http://www.thewebsitemarketinggroup.com.au/files/websiteplanner.html