4 ms·
Yup, chuck that responsibility over the wall. Not. True, the QAs job is to test it delivers as requested, UX if it is usable by the end user, ops that is is no
by flurdy 8y ago
Yup, chuck that responsibility over the wall. Not.
True, the QAs job is to test it delivers as requested, UX if it is usable by the end user, ops that is is not heavy on resources etc. But it is a joint responsibility between all and especially the developer and designer that they deliver quality and not cut corners.
If there is an ultimate responsible it would perhaps be the project/product owner who would decide what is important and how much time and effort they should spend on which parts. But still it is not just pass-the-buck, they are all responsible.
- amelius 8y agoThe programmer's job is to come up with the best solution in the minimum amount of time. That's an ill-posed/unsolvable problem. Hence they will sometimes come up with a solution that's not perfect, and they will leave it to QA (or the product designer) to see if the solution is acceptable.