4 ms·
I can think of several ways in which faster development could lead to better quality. Let's say you have a fixed time to come up with a solution to a problem. I
by chthonicdaemon 2y ago
I can think of several ways in which faster development could lead to better quality. Let's say you have a fixed time to come up with a solution to a problem. If you are able to come up with one candidate and evaluate it in that time, you have to live with what you get. If you do two candidates, you can select the one that is better.
Another aspect of quality is "polish". A team that can get a UI in front of QA twice in a development cycle instead of only once will benefit from more fault-finding.
- al_borland 2y agoParkinson's law tells us that work expands so as to fill the time available for its completion. I think the more likely outcome would either be it still taking the same time to deliver, with extra fluff in the middle, or the time simply shrinks. One thing is still evaluated and shipped, but slight faster.