Here it continues...
Step 2.5 : Converging
Now that you have discussed absolutely everything from planets to minute organisms its time to zero in on one single implementation/ use-case. Without this you will in the circle.. Its important to look at all the aspects and scrutinize the idea before rejecting it. I am working on some material on how to reject ideas and will have it in some blog soon. (Though it doesnt sound right but thats what happens in this stage)
Step 3 : Prototype
Now that you have zeroed in on one idea , its time to prove the concept. Some people call it proof of concept , prototype etc. In this a small (may be non scalable) working model of how the end product will be. This can be used for investors , customers , technical documentation and most importantly to understand the loopholes you might have left!
Product launch depends on companies and it might be before the demo or after. Or there might not be an official launch step. It can be combines with one of the next steps.
Step 4 : Demo
This isnt the most difficult step if the prototype actually works fine. Well thats the ideal scenario. In reality it really depends on the kind of timeslines you are working. I definitely have some funny stories to share here.
Step 5 : Delivery
This is where a lot of logistics , teams get involved and really its mostly about the project management , inventories etc. Most importantly your customers might come back with feature enhancements or feature requirements. Everything is different on paper and demo. To meet the needs, perceptions it takes a lot of blood and sweat from multiple teams.
Step 6 : Support and so on.
Once the initial hurdle is gone and everything is ironed out, its more of ongoing support and bug fixes, feature enhancements , upscopes etc.
