In the days where agile has become second nature there is a lot of debate about whether or not picking a release date is considered 'Agile'. We've all heard the terms continuous delivery, MVP, Release Planning but what do they all mean and how does it fit with a Go To Market Strategy? We've also all heard that in an ideal world continuous deployment is the key to delivering true customer value... so how can having an idea and picking a release date still be agile?
That's because we all need guardrails. Just like when you have a limit to how many API calls a minute they can make, the Business needs a timeframe for the amount of features they can have before a specific Go To Marketing Launch point. Continuous deliveries is great but you don't want to have a Go To Market Strategy for every day and in some cases you might want to put the features behind feature flags to provide a bigger value at a later date.
So at the end of day if you find yourself with a new idea and you are trying to build it, even if you are doing continuous deployment pick a date where you or your business should do a larger advertisement. Based on velocity, determine what would fit in that and then adjust the date based on that knowledge or research that comes down the road. But if you don't start with a date or set list of features chances are you will probably find it hard to launch because the list will keep growing and the date will keep pushing.