lifecycle - Agile Development vs. Publishing Too Early -


where you draw people between playful and a limited feature set) and Publishing Very fast (Which does not mean buggy)?

I am thinking that if you publish very quickly, then perhaps the potential users are overcome by thinking that your product is half-thrown on the market randomly, the other finished software Can not compete with and will never return. But then, the 'agile' development has been originally designed so that it can rotate as quickly as possible.

Where do you draw the line? Am I wrong, as long as I think they are extremely qualified for the user's time, do I want to delay publication products? Do not remember me on marketing, development or other occasions because I did not leave it early?

I would be very interested in your thoughts on this topic. Thanks (!) Understanding ("my understanding") does not necessarily mean "publish"!


Comments

Popular posts from this blog

c# - ListView onScroll event -

PHP - get image from byte array -

Linux Terminal Problem with Non-Canonical Terminal I/O app -