back

by EwanG·12y ago·view on hn ↗
PMP certified PM here - I think the main role of a PM at any company, but particularly a software company, is as a story teller. By that I mean that you are responsible to take the team's status, and put it in terms the stakeholders understand (on the one hand) while taking the stakeholders' goals and putting them in actionable terms for the team to execute (on the other hand). Very few PM tools seem to facilitate this. Many of the corporate ones (as mentioned here and elsewhere) focus on completion in terms of tasks and dollars, and maybe resource assignment and forecast. That's because what folks REALLY want to know - how close am I to getting what I thought I was paying for - is hard to measure objectively. Both because the definition of "what you thought you were getting" is usually squishy, and how close is "good enough" is usually difficult to measure except in terms of whether there is money to make it better or not.

Waterfall tries to address this by making the "what you thought" as rigid as possible, but not surprisingly I can give you exactly what you asked for and you will find it lacking. Agile says I'll give you "good enough" often enough for you to decide when you're done as early as possible, but tends to be difficult to time box. My .02 worth anyway...

1 comments
This is a great response.

I feel tools are often an excuse for poor PMs to be lazy. A PM is probably not going to be everyone's best friend -- your job is basically to facilitate decisions by executive leadership and make sure those decisions are executed on. You don't need a fancy tool for that; you need to communicate often with everyone (which often means bugging development managers for reports when they have better things to do.) Tools can help with this -- making the reports easier to generate/consume, but at the end of the day this can be integrated with whatever task assignment process the development group uses internally (be that tickets, or post-it notes, or smoke signals...)

As for agile vs. waterfall, you're right. It's tough to get corporate suits out of the "well when will it be ready?" mindset. The nice thing about agile though is that you repeat the process much more frequently, so you can actually start to improve that process and shorten your sprint times and do more actual work in less time. Executives like to see that, so early in a project it helps to focus on that as long as the product is making progress.