Thanks Jayasurya, great to hear from you. Product development is a very passionate area for me, each time I read something about it – it gets me really excited that there can be so much innovation in every stage of the agile process.

Regarding the question you’ve raised here – it is very practical of you to be thinking of this. In my previous experience there has always been a soft release to address such a situation. Here we release a software to a predefined set of users who know the limitations and are aware of what to expect. When we reach a certain sign off from this focus group, the software is then released to the wider public. For applications, we release it through subscribe only download process and then when the product is ready, we get it out to general public. In essence, we trickle some of the initial bugs that are too obvious for a user. This is an experience which has worked quite well in the past for me and I suppose it gives you an opportunity to co-develop a product with some initial friendly users who can help you propel this development further.

Currently i’m in the process of deploying the product to the market, but i’m a little concerned over the kind of feedback it would get (as they say, first impression is the best impression). Most of the features are in place and working fine but there are a few bugs that are showing up- I’m wondering if i should wait till the bugs get fixed or go ahead with the release and bug fix on the go. It would be really helpful if anyone could shed their thoughts on this?