3 ms·
You'd generally have PMs who had little contact with the engineering team proper. They'd take requirements from the execs, turn them into design documents, and
by kstenerud 6y ago
You'd generally have PMs who had little contact with the engineering team proper. They'd take requirements from the execs, turn them into design documents, and then pass them to the engineering team to implement. So there would be a fair amount of friction, yeah. And lots of DFDs and ERDs that didn't match what was really happening ;-)
But then again nobody on the engineering team took them too seriously anyway, so it kind of worked out.
The main problem in those days was centralization of decision making at the top, where the decision makers had the least exposure to the reality on the ground. The military legacy of computer systems, I suppose...
- specialist 6y agoYa. I think that's just a very hard problem. Mostly due to scale running up against organizational psychology. I helped a friend with some property tax software for governments. Trivially technically, almost intractable organizationally. Not for me. I deeply respect the people who can swim those waters.