Sometimes you have to make a tradeoff and focus on the golden path, which means comprehensive testing has to be skipped or bugs have to be explicitly left in.
Yes it’s bad. Yes it sucks. But it’s that or nothing gets released at all.
(I wish it wasn’t that way. I try hard to make sure it isn’t that way at my job, but for now that’s how it is)
Known issues that don’t interfere with the critical user stories are usually not prioritized. They should be disclosed, and even better if workarounds are published, but fixing them usually isn’t in the budget.
Though it being difficult doesn’t excuse releasing an untested program or one with known issues…
Sometimes you have to make a tradeoff and focus on the golden path, which means comprehensive testing has to be skipped or bugs have to be explicitly left in.
Yes it’s bad. Yes it sucks. But it’s that or nothing gets released at all.
(I wish it wasn’t that way. I try hard to make sure it isn’t that way at my job, but for now that’s how it is)
Known issues that don’t interfere with the critical user stories are usually not prioritized. They should be disclosed, and even better if workarounds are published, but fixing them usually isn’t in the budget.