You could start by searching 'product development best practices' in
Google. You'll find some generic guidelines, but the problem is that
even within industries product development is not something you can
put a restrictive set of parameters to. To benchmark something you
would have to run a control experiment, for example, benchmarking one
computer against another by running the same program and measuring the
speed. When developing a product no one would bother developing the
same product in two different ways. :)
The rational university (www.rational.com) has a set of courses
covering 'requirements management'. Do these - they'll allow you to
determine the best way to figure out what pain your product will
solve, and how to prevent your product from causing you pain when you
develop it. They recommend:
Develop iteratively, manage requirements, use component architectures,
model visually, continuously verify quality, control changes.
My final piece of advice is to get the planning sorted before
developing:
Determine what you want to achieve (target market, problem you're
solving, etc), work out how much you need, double the amount, secure
the funding, develop the product.
The most important part is having the money, or you'll crash and burn.
Having said that, I've developed a number of products and they're all
different - this just presents a great start.
Darren |
