3 ms·
I've said it before: one of the goals of Agile methodologies as sold to management is the promise of emulating a good developer with a redundant array of medioc
by bitwize 6y ago
I've said it before: one of the goals of Agile methodologies as sold to management is the promise of emulating a good developer with a redundant array of mediocre developers. Good developers can produce good work fast. They can take feedback on an iteration and turn it into working code for the next iteration quickly. But they're unreliable -- prone to getting cranky or bored -- and they're a single point of failure: If they die or quit because they got too cranky or bored, million dollar projects can be put in jeopardy.
But by spreading the work out over a team and making them collectively responsible for the code, and by keeping them constantly in communication, it is hoped, you can take advantage of their cumulative brainpower to get good developer quality and turn around time while smoothing over the reliability issues because any one developer is fungible with the rest.
It is hoped, that is. Reality is usually quite different...