Prototype to save money
Published: 01 Aug 2002 09:19 BST
When moving forward with prototype development, it's important to keep sight of the goals. If you're demonstrating interfaces, make sure it's the primary function. If you're modeling architecture, make it a true representation of the final application.
It's very easy to get caught up in the instant gratification of a prototype and include far more functionality or design elements than intended or needed. This can drag out the prototyping phase far too long and bring too little benefit to the solution. If you didn't intend to demonstrate a functionality, then be disciplined enough not to include it.
If you aren't clear on why you're prototyping, it can easily become the waste of resources that business drivers predicted. Keep it simple, make sure all intentions are clear, and don't let the thrill of very rapid development become a means to an end.
Demonstrate how prototypes save money
One of the most difficult tasks in creating a prototype is getting permission to do it. The time and money prototyping can save aren't always obvious to business drivers and clients, but it's easy to prove the value if a prototype is truly warranted.
While some might argue that prototyping creates rework, its purpose is to actually avoid the rework that comes from unknowns or incomplete design. Once you've got a model to work from, it's easier to make the architectural decisions that arise during development. A physical representation can help waffling clients make decisions so development can begin with confidence in the desired outcome.
A proof of concept helps in high-risk solutions by identifying problems early so you can modify the architecture before they reach the point that you'd have to modify the code base to fix them.
You can demonstrate the importance of prototyping with a cost/benefit analysis. Outline the total development cost with and without the prototype. By creating an upfront model, your risk, development time, and probability of change will all drastically decrease.
Once you've shown that prototyping doesn't incur new costs in most cases but it merely shifts some of the expenses of upfront planning, risk, and development to a new and focused effort, you'll have an easier time convincing clients that it's a worthwhile expense. It's easy to show the benefits on large projects, considering the added bonuses of proof of concept and peace of mind that come with prototyping. If the concept of a prototype is hard for your client to swallow, outlining the benefits and explaining that prototyping is the bridge between planning and development can help them see it as a culmination point for efforts from different teams.
Pro prototyping
Prototypes are excellent, hands-on planning tools that are useful to anyone involved in a development effort. Being able to visualise an eventual solution provides a template for development and an easily grasped overview for business drivers and other nontechnical people involved in the project. A proof of concept can facilitate a project in everything from sales to quality assurance. If your solution warrants it, a prototype can help you design, develop, and deliver your product effectively and efficiently.
Have your say instantly in the Tech Update forum.
Find out what's where in the new Tech Update with our Guided Tour.
Let the editors know what you think in the Mailroom.
Previous
Did you find this article useful?
3 out of 7 people found this useful
Digg
Slashdot
Del.ici.ous
Stumble
Reddit
