Release = f (Quality, Time)
If you ask the testers or the persons responsible for quality on the team, they will never sign off release saying that we have many important bugs yet to be fixed. If you ask your project manager or the person responsible for the release, he will tell that we have to ship by this date. That makes a real software Release a function of two parameters: Quality and Time.
Quality is the main reason we want to ship software. We want it to stand out in the galaxy of uncountable applications so that our users fall into love with it. And if we happen to ship a product that is buggy, it can dent our repute in the market.
To gain the ultimate quality, we need endless time that we never have. We have some user conference happening next quarter, where we have to showcase the newer versions of our software. And what we know is that our competitor is releasing their new product in related domain in second half of 2013 and we have to do it before them.
So if you are in situations like these, draw a graph like below and you know if it is the time to release or not 🙂
How your team makes the release decisions? Purely on time or considering quality and time? And did I miss any third parameter.