3 ms·
"While the programmers are off building the next major feature, he is busy writing specs so that, when they finish, there won't be any idle time before they can
by ajross 18y ago
"While the programmers are off building the next major feature, he is busy writing specs so that, when they finish, there won't be any idle time before they can start the next iteration."
This is essence of the problem right there. If the developers aren't involved in the design of what they're building, you have a broken process. The idea that you can "skimp" on talent such that you're hiring people to implement things you wouldn't trust them to design is pretty flawed; it means that you're developers are going to be producing a lot of crap by failing to see or find implementation-time improvements to the stuff in the abstract specs. And the idea that you can get that design right the first time at all, without having written a line of code, is fundamentally flawed.
The rest of the suggestions in the post seem to be attacking this solution sideways, by involving the developers earlier, iterating the specs, etc... But it doesn't seem to recognize the core problem. You can't "hand off" low-level specifications to someone other than the implementor. It doesn't work.