Earlier quoted context omitted.
For software you should make something - any part - work and release it. Then do regular feature releases after that. If you are not working alone you can ask your marketing people for help, sometimes it is worth waiting for a big bang release, sometimes not (For some things if you miss Christmas you should delay until next Christmas). I recommend you err on the side of release too soon - customers are the ultimate a…
This doesn't work so well for video games. Reviews come out saying its thin on content with a score to match and can kill a game before its had a chance to expand. Developers have started trying to do this more often lately with mixed results, DICE and Blizzard are high profile examples of this. Blizzards latest World of Warcraft expansion was heavily criticized for the lack of content on release day and has yet to s…
https://www.factorio.com/blog/post/fff-184
Then they just kept releasing every week for 7 years, and now you have people building CPUs and explaining Apache Kafka with it.
Ostriv is another recent game that comes to mind as having a similar development cycle. Also many F2P MMOs - most of the non-Blizzard online games I know do regular releases that frequently change the game mechanics (often, to a big player uproar) but still keep their userbase. Fortnight and Pokemon Go are two big ones here.