So you have this great idea for a new website or web based service, however you don't have a clue as to how to get it started. Putting together a web project can be more challenging than you think. It is not always as simple as going to a web design firm and saying here is my idea, now build it. Considerable amounts of planning on both the client and the developers side must be put into designing and mapping a custom web based application.
Web applications generally have a much longer development cycle, require more research upfront and most importantly clear and concise goals and expectations. Otherwise a project could run for years and years with constant research and development work, instead of being launched in a timely manner, and improving over time with real world feedback.
At CWI Applications, when a client comes to us with an idea for a web application that they need, the first thing we try to do after getting a general understanding of the problems they face and the goals they want to meet, is plan an overview of the entire project. Having a good foundation is key to a successful project that stays within budget, time frame, and expectations.
Putting together a plan may seem like extra work (which it is), and many clients may think that there is no benefit of having a plan for developing your application, or do not have the time to do it themselves. Below are just a few reasons why it is a good measure to have a plan:
1) Get only the features that you need. Having a plan laid out you can clearly see what functionality or features you need for the different areas of your application.
2) Having a plan to follow provides a road map or blueprint that will help keep your project moving forward in the right direction.
3) One of the hardest things in custom application design is completing a project within the clients ideal time frame. This is often caused by clients who add or change the scope of the project midway through. Having a plan that can be adhered to both by client and developer will help promote timely completion of the project.
4) Just as having a plan will help ensure a timely completion it will also help reduce your costs. Both you and your developer will know what needs to be accomplished and that any additional items become extra.
5) Having a plan to present when asking for quotes helps ensure that you will get apples to apple comparisons. There should be little variation between developers as to understanding what is required since they will have a complete outline of your needs. This will help you compare and choose a developer that meets your criteria and understands the project.
When writing your plan you should try to keep it in as simple terms as possible. Break down your ideas or concepts similar to how you would explain them in conversation. The plan does not need to be as formal as a business plan that you present to a bank, however it should be well organized.
I have included a basic outline below that could be used as a guideline in writing your plan. Wherever possible include drawings and diagrams of how you expect the functionalities to work, how the interface should look, etc.
Description - Detailed description of the project.
Goals - Detail the items that are most important to you in the goals section. For instance if you want to be completed by a specific date indicate it, or if you want it very user friendly, this is the place to indicate it.
Budget - This is an area that most people do not want to talk about. However indicating a ball park of what you are willing to spend on your project will help determine if your wants and needs can realistically be met. Some are afraid to say simply because they think a developer will max the budget out. An easy way to overcome this is take the maximum you are willing to spend and reduce it by 25 to 30%.
Target Audience - Define the different groups that will need to interact with your application and what levels of access they will need. Don't forget to include yourself and/or staff in this. / o Preferences and Benchmarks - In this section talk about any specific details that attention should be given to. For instance if you hate green indicate that. Also in this section list sites or applications that have a design, interface or overall experience that you like. It does not necessarily need to be in the same industry as your application.
Front-end feature list - This section details what - if any - functionalities exist on the front-end, primarily to guests.
Admin feature list - This section details what functionalities exist on the back-end. Detail any admin levels here and what each admin level has access to.
User feature list - This section details what functions - if any - that registered users will have access to.
Site Map - Outline your content in this section. Come up with the navigation you want to use and their subsections.
Flow Chart/Wire Frame - Diagram how you see your application working. What data do you need to collect? What data do you need to return to the user? What data do you want to be stored? Then create a visual layout of how you want your data presented. In this section depending upon your application you may have multiple views. See more about wire frame here: http://en.wikipedia.org/wiki/Website_wireframe
Summary - Brief summary of the key points of your application and the goals you are trying to accomplish.
Post a Comment