You are viewing a single thread.
View all comments View context
15 points

A typical project manager will get a range, take the lower bound and communicate it as the only relevant number to every other stakeholder. When that inevitably does not work out, all the blame will be passed on to you unfiltered.

Depending on where you work it may or may not be worth giving someone new the benefit of the doubt, but in general it is safer to only ever talk about the upper bound and add some padding.

permalink
report
parent
reply
2 points

I have a friend who’s a new PM (in scaled agile). He isn’t up on expectation management.

We have a process where we request data from another agency which takes “from 7 seconds to 12 days”

And of course he tells people that. And of course they hear “7 seconds”

I have told him that if the SLA is 12 days, say “less than 12 days”

permalink
report
parent
reply
3 points

Only novice PMs do that and believe it or not, the project manager carries the can for failure .

permalink
report
parent
reply
6 points

I hear this criticism all the time, but I’ve never seen it happen in 5 companies I’ve worked for so far. Usually there’s an understanding that estimates are wild guessing, and things are planned using dependencies rather than timeliness.

permalink
report
parent
reply

Programmer Humor

!programmer_humor@programming.dev

Create post

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

  • Keep content in english
  • No advertisements
  • Posts must be related to programming or programmer topics

Community stats

  • 2K

    Monthly active users

  • 861

    Posts

  • 14K

    Comments