Please wait...
2017-07-27 21:07 from IGnatius T Foobar @uncnsrd
I look at it from the opposite direction. The fact that two senior
people had to pay any amount of attention to this issue means someone
did something wrong and it cost the company money.
Given their support these days, that's not what's costing them money.
Currently working on a project that involves doing things in Dallas, organized with the help of a scrum-master whose last name is Lovelace.
Umm.
Today I was asked by a project manager what the word "greenfield" means.
I'm not sure I have a lot of confidence in the project now. :(
If it makes you feel better, I had to explain to the PM I was just assigned for my offering the difference between a project plan, a milestone plan and....wait for it....*minutes*
Like notes from a meeting. <shakes head>
Realize that likely I have much more PM expertise than she with my 20+ years, but still....I really think that PM 101 should be within expertise if you're hiring someone as a full fledged project manager.
One of the other PMs from this same group was completely confused when I asked him how many hours have been expended on one of his projects. He actually told me he only tracks his own hours, so he doesn't know. :-/
We certainly see that in IT - lots of resume enhancement projects.
We have an intern who is finishing his masters in cyber security.
He's looking for proper work, and while HR dittoheads appear desparate to find cyber security employees, they only want them if they have 5+ years experience.
There aren't many people with 5+ years experience in that field. Certainly not at the volume people are trying to hire.
So, rather than just finding one person and training up the rest, they'll go for five years waiting on someone with 5+ years experience.
Since this is standard industry practice, the people who would have gained 5+ years experience if they'd been hired won't get that experience.
Because, it would seem, HR employees are mentally dimunitive dunderheads lacking the capacity to perform basic arithmetic.
PM: "Can you send me <document> so I can include it in our meeting notes?"
Me: "Just link to <link> so we don't have a version floating around that'll quickly get out of date."
PM: "Oh, good idea. Thanks!"
<< PM then downloads the document from <link> and attaches it to the meeting notes >>
*sigh*
This PM is a dunderhead, but is at least a very *nice* dunderhead...
Sometimes it's useful to have the version available from that moment in time to understand why decisions were made.
Seen in email this morning... this is not verbatim, but my sarcastic version.
"Beginning tomorrow, we will be enforcing automatic account lockout after five password failures within a 30 minute period. If your account is locked out, you will be automatically notified by email, but you won't be able to read that notification because your email is locked out. You can reset your password using this handy internal web site, which you won't be able to reach because your VPN is also locked out. You could try calling the help desk, but your phone will probably be locked out too. Maybe you could drive to the nearest office to access that internal web site, but you won't be able to log in to the wifi or log into a local workstation without a working password."
"In short, if you turn on some old device that has your old password cached on it, you'll lose access to the corporate network faster than if we fired you."