Search This Blog

Thursday, May 8, 2008

Rapid Prototyping

If you are in this emerging 'applications' market, and are in the business of building applications for OEMs/ISVs or Service Providers (yes, some Operators actively invest in R&D work), the term 'Rapid Prototype' is not new to you. In short, people are always looking at 'quick and dirty' demonstration code that shows off a cool concept which they can take to prospective customers as a viable product or service to be rolled out. Customers who ask for this are not sure if that idea will go anywhere, but are willing to test the waters with you (if you are willing). A typical software development organization follows the 'Build Rome one stone at a time' model whereas this particular market needs the 'pre-fab modular home in 1 month' model and therefore struggles with this particular market. I know of many organizations who  believe this is not an area to be in, because of the limited scope and length of such projects. The problem however, is that they fail to understand that this market is actually very attractive and profitable, but only if you look at it the right way, and approach it the right way. Last week, I was chatting up with a friend on the same issue and was sharing some insights into what one should try and institute to make this model work. He suggested a blog post, so here goes - some common problems, pitfalls and solutions: