legion |
02-14-2012 06:54 PM |
Salt
Oh man.
I have worked with a certain individual, let's call him Alex DeLarge, for about 11 years. When I first started on this project 11 years ago, I was 2 years out of college and a junior systems analyst. ADL had been with the company about 15 years and had recently joined our sister business department from the field.
ADL is one of those guys that always chases a "100%" solution. On average, a 70% solution costs X dollars. A 90% solution costs 2X dollars. A 95% solution costs 3X dollars. A 97% solution costs 4X dollars. A 98% solution costs 5X dollars. You get the point. I have frequently implemented solutions for this guy that cost 20 times what a 70% solution would cost. They usually end up going WAY over time and budget as he finds more gaps to fill, and the solutions get extremely complex to chase a fraction of a percent of what he considers better functionality. If someone actually analyzed them, they'd blow any reasonable ROI out of the water.
He also micro-manages. He doesn't tell me what he wants, he tells me how to do it. This also contributes to the over time/over budget/endless scope creep of his projects. He is notorious for sending dozens of people single, specific questions so that they can't piece together what he is getting at. The thing he doesn't realize, is that when he does it to my team, we all sit together, discuss what each of us has been asked, and figure out what he is really doing. Because of his secretive nature, he often leaves out HUGE requirements that he didn't recognize, which later become HUGE emergencies for the rest of us when he realizes stuff won't work. If he'd just let us (systems analysts) figure out how to best implement solutions, this would happen much less frequently.
He left for another department for a development opportunity after about 4 years. The guy who took his job quickly undid most of his decisions, as the programs simply didn't get used because they were too complex and time-consuming. People were using Excel, sticky notes, anything but what they were supposed to because they couldn't get their jobs done in a timely manner.
Well, he came back after two years, and was promoted to a project manager on the business side. This basically means that the only person who can say no to him is his boss, a VP, who happens to think he is the second coming. The projects have gotten bigger, more complex, more secretive, and more over cost and over schedule, with many more last minute emergencies.
Did I mention this guy is a huge bully? He's literally stormed out of meetings when he didn't get his way. When I was in training the summer before last (learning Java), he called my boss and screamed at her and demanded that I be taken out of training immediately to work on one of his emergencies. My boss told him no, my backup would do the work for him. He was fuming for months over that one. A couple of months ago, he typed up a huge manifesto on why his projects should be exempt from change management processes (and testing) so that they can get done faster. He sent it to me, my manager, and all of the directors in my area. It was ignored. From what I gather, the directors met and decided not to dignify it with a response.
I heard a rumor over the summer that his wife was pushing him to retire. I heard this rumor from a manager in my area, who was hoping desperately that it was true. The story goes that while he has been with the company for 25 years, his wife has put in 40 years, and she wants to travel.
I am currently working on an assignment for him that will take 5 months to develop and will live in production for six months before it is thrown away. He tried to get me to commit in December by having it done this week, but after not backing down from saying it was physically impossible, he finally went to my boss, and then my boss's boss before he ultimately relented. We've been working on it non-stop since December, and I hope to have requirements by the end of the month...
Today, I got an e-mail that he was being given much more responsibility as a "development opportunity". The writing on the wall is clear, he will probably be promoted to a VP soon.
I simply turned around at my desk, and loudly proclaimed to my cube-mates: "Well, I guess I better go get fitted for a saddle!"
I plan to make a hasty exit from my area as soon as possible. The problem is another mega-project just started up, and they have suspended all job posting for all corporate departments until that staffing shakeup settles out. My best hope is to be drafted by the mega-project, but I'm not on the right people's radar for that.
|