Over the years we’ve developed a repeatable, efficient process for developing small to medium sized web sites. These web projects are usually completed in one iteration in about 2 to 3 months.
The process we’ve developed involves considerable interaction with and feedback from the client throughout the project. We’ve broken up the project into 6 or 7 mostly overlapping phases:
|
It’s important to note that the UI design is determined about half-way through the project. This helps ensure that the design is driven by the business need and functionality instead of the other way around.
-
•Client Planning Meeting (discuss process and schedule meetings)
-
•Stakeholder Identification
-
Create Website Requirements Survey and Send to Client
-
•Client Completes and Returns the Survey
-
•Survey Analysis
-
•Client Kick-off Meetings (Discuss Business, Branding, Technical)
-
•Goals (of project/website)
-
•Scope List
-
User List (Primary. Secondary & Tertiary)
-
User Objectives
-
Use Case List
-
Design Needs (Look and Feel)
-
Search Engine Optimization Analysis (Current state, if any, and future needs)
-
Seed Keyword List
-
Competitor List
-
•Company Strengths & Weaknesses
-
Key Messages
-
Technical Requirements
-
•Assumptions
Functional Definition Phase
-
Competitor Analysis (Navigation, Messaging)
-
Site Map
-
Page List
-
Navigation Elements
-
Wire Frames
-
Messaging
-
Creative Brief
-
UI Design Concepts
-
Prioritized Target Keyword List
-
Alignment of Use Cases to the Site Map/Page List
-
Alignment of Keywords to Page List
-
Forms (Fields & Validation)
-
Technical Operating Environment Definition
Development
-
Page Template Creation (From UI Concepts) (HTML/CSS)
-
Template Image Creation (category specific images, etc.)
-
CMS & Database Setup for Development
-
Style Guide
-
Custom Client Specific Coding (Functionality Not Available in CMS)Â
-
Configure Content Management System to create categories, pages, menus, lists, etc.
-
Seed Content
-
Page Content Creation & CMS Integration
Testing & Go Live
-
Integration Testing (plugins, content, etc.)
-
User Acceptance Testing
-
Deploy Solution to Production Environment
-
Turn Site Live
-
Training
-
Support
Every project is unique. So expect to modify your plan with each and every project. Hopefully, this plan will give you a decent baseline to start with.
September 23rd, 2008 at 7:55 am
Hi, I am a web designer by proffesion.
I like your article and would like to request you to use your article in my webpage.
Kind Regards,
Ed
March 31st, 2009 at 7:54 am
I liked your article very much. Thanks for sharing…
October 26th, 2009 at 9:28 am
I like your structure, one thing I would like to suggest is to mention the “Maintenance Phase” which becomes most difficult to some.
October 28th, 2009 at 8:51 am
Great article! Only as a project manager I would say to the last comment I would not include maintenance as a phase, because a project is finite and maintenance is ongoing (a process).
November 1st, 2009 at 3:55 am
Hi,
It was helpful in preparing a project development gantt chart for me..
November 29th, 2009 at 7:37 am
It is very helpful indeed , Thank You.
November 29th, 2009 at 11:17 am
Great article. Thanks for sharing.
February 3rd, 2010 at 10:46 am
I am impressed with your site. I entered in all the required information to download the project management paper, and it is not responding. Please advice, thanks!
February 15th, 2010 at 1:02 pm
Very succinct structure, thanks. If you care to dive deeper, in more complex systems, I typically break out Content Design (early) from UI Design and allow UI Design to wrap up after functional design is completed, allowing final UI Design to accommodate functional and usability paradigms.
February 23rd, 2010 at 3:49 pm
Jeff, Could you pls. elaborate a bit on that cause it is a very interesting point that you raised.
Thanks,
Amir