I will never complain about the amount of work I have because I love to be busy, but I have the luxury of being able to leave work at work unless there's an emergency. That said, I've definitely had to create a Do Not Disturb mode for my watch/phone because only when I'm super busy do I get tons of unrelated notifications.
I swear, some managers and project managers seem to think that projects run themselves, and they are just there to approve charge codes and order people to meet deadlines.
From a meeting I was in, but oddly enough, I was not the focus of PM's ire this time:
PM: We need the final database published on Friday, so all reviews have to finished by Thursday.
DB: We can't even start work on it until Thursday, there's no way it will be ready.
PM: I told you last week that it's needed by Friday.
DB: Then you made the SS2 release the highest priority, so I'm not working on the database.
PM: Then get more resources! Geez, I don't have time to do everything for you.
DB: <leaves meeting room in disgust>
Yes, the project manager's solution was to simply order the subsystems to "manage their time better".
At one postmortem audit (we had a lot of those), the auditor's conclusion was "It appears that the PMO seems to believe that subsystems have the ability, and responsibility, to magically conjure up resources".
A second auditor was more blunt: "Project Management blames the failure of the project on the subsystems failing to properly manage the project. They seem unaware that is their job."
Bob, the well known slouch.
You just need to be more "agile", we even hired another PM to help.
*low, threatening growl creeps slowly*
I will never complain about the amount of work I have because I love to be busy, but I have the luxury of being able to leave work at work unless there's an emergency. That said, I've definitely had to create a Do Not Disturb mode for my watch/phone because only when I'm super busy do I get tons of unrelated notifications.
When everything is top priority, NOTHING is top priority.
I swear, some managers and project managers seem to think that projects run themselves, and they are just there to approve charge codes and order people to meet deadlines.
From a meeting I was in, but oddly enough, I was not the focus of PM's ire this time:
PM: We need the final database published on Friday, so all reviews have to finished by Thursday.
DB: We can't even start work on it until Thursday, there's no way it will be ready.
PM: I told you last week that it's needed by Friday.
DB: Then you made the SS2 release the highest priority, so I'm not working on the database.
PM: Then get more resources! Geez, I don't have time to do everything for you.
DB: <leaves meeting room in disgust>
Yes, the project manager's solution was to simply order the subsystems to "manage their time better".
At one postmortem audit (we had a lot of those), the auditor's conclusion was "It appears that the PMO seems to believe that subsystems have the ability, and responsibility, to magically conjure up resources".
A second auditor was more blunt: "Project Management blames the failure of the project on the subsystems failing to properly manage the project. They seem unaware that is their job."