Discussion Locked

Dealing with Difficult Project Managers

0 helpful
4 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I would love to hear everyone's thoughts on how to deal with the reverse situation - ie. how, as a architect/developer, to deal with difficult Project Managers.

The most common classifications of these Project Mismanagers I know of are:

1. Equationists: Those who think that if a project would normally take 6 months for 2 people to do, 24 people should be able to get it done in 2 weeks.

2. ExTechs: Those who used to be developers but can't seem to let it go, and so are always trying to control architecture, UI design, etc.

3. ScrewTurners: Those who are so eager to produce an end result that they place no priority on designing/planning a solution. They don't think progress is being made until they see rows of programmers in cubicles hammering away on keyboards.

If anyone else has any other classifications, please share them!

4 replies

by Lamont Adams

Given an 8 week project to build a bean-counter, he/she spends the first 7 doing design work, in an attempt to come up with the most elegant, effecient bean counter imaginable, then tries to implement the design in the final 7 days.

by arjay

Like the railway station master who sends trains in either direction, this person forwards mails from Mgt to tht eteam and vice-versa - revising the definition for delegation quite conveniently (i.e delegate decision making upwards!!).

by sparkywonderchicken

This should work because I can write it down on paper. They have never read any documentation and only learn by trial and error. They don't believe in analysis. They equate agile/extreme programming to hacking, which is their preferred environment.

Correlated pattern: "I'll hire a consultant to do my thinking."

This discussion is closed to new replies.