3 ms·
One thing that's really come through with Agile is how little value traditional project planning actually brings to real-world software development. You can do
by lmm 7y ago
One thing that's really come through with Agile is how little value traditional project planning actually brings to real-world software development. You can do any amount of estimation, forecasting, scheduling... but actually the only question that's worth getting a useful answer to is "what should I work on this week?", and the amount of work you have to do to figure that one out is much smaller. What you do need is someone who can understand the priorities that different stakeholders (including engineering) have, weigh those up, and come up with overall priorities for engineering to execute on; that's an extremely valuable role, but probably not to the extent of being a full-time position for someone who contributes nothing else.
The other side is that it's very difficult to evaluate a coordinator's performance, as an outstanding team poorly coordinated will look much the same as a poor team outstandingly coordinated. As an engineer, if I see a non-technical PM then there's a significant chance that they're contributing nothing but bullshit, and presumably someone from the business side would be equally skeptical of a PM with no business experience.