2 ms·
>Which is as always, unclear priorities, unclear requirements. Tell me about it. Recently had a PM ask me for a time estimate for a task called "Create reporti
by CameronNemo 6y ago
>Which is as always, unclear priorities, unclear requirements.
Tell me about it. Recently had a PM ask me for a time estimate for a task called "Create reporting tool for [network] interface data from [network monitoring tool]". No requirements. No further description whatsoever. And I told the PM three business days prior that I needed more information!
- stefan_ 6y agoI swear there is a very large segment of PM that believe they are some kind of "big idea" and "vision" dreamers and to get intimately familiar with the details of what they asking to be built is below them. You would get tickets like "Support protocol X" or "Integrate with 3rd party Y" with absolutely no effort spent to answer the hard questions, and most of the time they don't even know X or Y beyond the marketing.
- noir_lord 6y agoI think in part it is because "PM" is such a nebulous role, there isn't a clear career track for someone to become a PM so you end up with a widely disparate set of skills in that role. The best PM I worked with did comp-sci, decided he hated programming and went into project management, he got it. The worst was promoted out of customer support and didn't have a fucking clue.
- goatinaboat 6y agoI swear there is a very large segment of PM that believe they are some kind of "big idea" and "vision" dreamers and to get intimately familiar with the details of what they asking to be built is below them. Those same types also believe that if only they can add enough custom fields and statuses and mandatory workflows the project will become self-managing and they can go and do whatever it is they think they do.