When creating custom web applications there are many parts to the process. In the entire history of software development there are books and books and books on how to do it, how to document it, how to make sure everything is proceeding satisfactorily, how to create forms, figures, and milestones.
But in the end it is all about people and the following three things.
- Similar understanding of product goals and functionality
- Effective communication
- Competence
Lets take a look at each thing.
Similar understanding of product goals and function
In the beginning there is an idea! Or at least a current product that is not working to the best of it’s ability. The idea is the reason that webOnyx is in business. Someone has had an idea and they don’t know how to implement the solution so they must find a partner and explain what their vision and goals are. This means having conversations, writing specs, having more conversations and then writing more specs and then agreeing on a path forward.
Software is an evolving product. At the beginning of the project the two parties need to be as clear as possible when it comes to expectations of an end product. Make a list; nothing fancy and do the best you can to present a timeline and estimated costs for the major features. Many times in this initial stage development firms will ask for a 10 day clause, or a discovery clause to either look into the current product to be retrofitted, or ponder other solutions. As a possible client for web development – Do This. Or better yet insist on this if you are looking to build a web application.
If a product already exists development teams need this period to ‘poke’ around the current product or designs. This allows the development firm a chance to refine their initial ideas and tighten up the timeline. It also where the art of development first starts show. Developers are always seeking efficient solutions and better end products. Allowing developers to ponder an idea for a week or two will result in surprising creativity.
As a client you should want your development team to have a few days to refine their initial ideas because if you have a competent partner they will help you find solutions that will save you time and money. While development is an art, it is also a process surrounded by unknowns. The job of developer many times is analougous to having to guess how many jelly beans are in a jar. You could probably get close, but give a developer a day to measure the jar and get the dimensions of a single jellybean and their initial estimates will be much better. The result of having better initial estimates walks us right into the second important part of development. Effective communication.
