Now I am living in monthly release schedule. Every month we have regressions and all other processes for release. Not very often but sometimes happens that release needs to be postponed. Last time I had this situation was about six months ago. It was because of project I worked with. I am not proud of it, but happened what had has to happen.
Situation was very simple - developer underestimated development time and amount of bug registered for this feature. And everything ended even worse then just postponing release. Whole feature had to be removed from release, all affected areas had to be retested.
Having monthly releases and one of them postponing for two weeks affects whole company schedules, other releases, time to market, and I don't even know what more, but 100% sure it was affected.
Other interesting thing about that feature was that it was required by customers, I don't know details, but a lot of people were pissed because of this situation.
Having monthly releases and one of them postponing for two weeks affects whole company schedules, other releases, time to market, and I don't even know what more, but 100% sure it was affected.
Other interesting thing about that feature was that it was required by customers, I don't know details, but a lot of people were pissed because of this situation.
OK, enough of my experience.
Postponing release is not one man job (of course if company is not from one person) and it affects a lot of people even from outside the company(in my example). And then I start to think about all work - the line of issue criticality starts to blur out. How critical issue needs to be to stop whole process and push or stop everything for a period of time.
Image situation - Microsoft releasing new office packet, and for some reason there aren't "Save" button, just only two "Open" buttons and one of then works as save other as open. Do this bug is reason to postpone the release? Or other example - new FPS game has one level where just half of enemies are generated, this would be reason to postpone game release date? I wouldn't talk about military or medicine, there are different rules.
So both times I would suggest to release product and after release hot fix, but who I am to make such decisions. But these was small things, but if for example, product from office package crashes if document is with picture, or game has level without exit, these would be reasonable to postpone release. It could make huge impact on trust from users of these products. But line sometimes is so blurred out that it is hard to decide what to do.
In such situations clear head is needed, because of pressure from project manager or other management can make things even worse and bad decisions can be made. Always watch Your ass and what must need to be done - released on time, no matter what.
Image situation - Microsoft releasing new office packet, and for some reason there aren't "Save" button, just only two "Open" buttons and one of then works as save other as open. Do this bug is reason to postpone the release? Or other example - new FPS game has one level where just half of enemies are generated, this would be reason to postpone game release date? I wouldn't talk about military or medicine, there are different rules.
So both times I would suggest to release product and after release hot fix, but who I am to make such decisions. But these was small things, but if for example, product from office package crashes if document is with picture, or game has level without exit, these would be reasonable to postpone release. It could make huge impact on trust from users of these products. But line sometimes is so blurred out that it is hard to decide what to do.
In such situations clear head is needed, because of pressure from project manager or other management can make things even worse and bad decisions can be made. Always watch Your ass and what must need to be done - released on time, no matter what.
Yours friendly neighborhood Tester
Komentarų nėra:
Rašyti komentarą