This post originated from an RSS feed registered with Ruby Buzz
by Assaph Mehr.
Original Post: The Mehr scale of Project Managers
Feed Title: Open Mouth, Insert Foot (Echo Internationally)
Feed URL: http://www.bloglines.com/blog/AssaphMehr/rss
Feed Description: General geekness venting, mostly about Ruby and why Software Engineering != Computer Science, dammit!
This article tries to describe the
various Project Managers I have worked with in the past. This is not
based on scientific research, just on years of observations gathered
when working for various IT companies, from really small startups to
the really big giants.
Projects are about - to use
technical terms - stuff what gets sold to clients. This doesn't imply a
discreet product, perhaps just a single feature of an existing one. But
the idea is the same - you implement functionality in order to get
money.
Project Management is about
controlling the contents, timelines and resources to achieve the goals.
To use technical terms again, it's all about getting the monkeys to
work overtime to produce something that'll get the manager more money.
At least, that's the view expressed (implicitly) by many managers. So
here is a scale to gauge the competency of your local PM. If only we
find a way to gauge this before signing the contract...
Timeline
The Good: Knows the estimation
factor for each member of the team (consistent over-/under-
estimation). Gathers the estimates, applies the factor, averages
between several inputs and tacks on a 20% buffer of 'unknowns' before
submitting to executive management.
The Bad: Gathers the estimates
then argues about how long it takes for each item. Eventually allocates
anywhere between 80%-100% of the original estimated time, as executive
management applies pressure.
The Ugly: Doesn't gather
estimates. Goes to the team with a 'this is what has been decided upon
by uppers management' attitude. Ignores mid-development cries of not
enough time by responding 'It will work by the deadline as that's what we promised our clients. It has too'.
Content
The Good: Knows what 'iteration' means - for people across many disciplines and projects.
Has the analyst produce requirement docs. Has the designers/developers
break it down to development chunks. Asks for time estimates per item.
Prioritizes the list and cuts it off by the schedule.
The Bad: Is a bit fuzzy about
the whole iteration thing - thinks it's just a way to keep everyone
100% busy 100% of the time. Understands that the testers need time too,
and thus equates 3 month development time + 1 week testing time = 3
month and 1 week project total.
Has the analyst write the requirements. Has management tack on glitter.
Assigns tasks per developer on a need to know basis: "This week you
need to know that standard and have a partial implementation. Maybe
you'll get to complete it next week, maybe not".
The Ugly: Equates code written
with code working. Only vaguely aware of what the technology and
problem domains are, but drops buzz words like crazy.
During prioritisation sessions continually remembers more features that
absolutely must make it in. When things run amok, calls meetings in
order to (re)adjust the schedule. With everyone vaguely involved.
Repeatedly.
Resources
The Good: Believes in personal
lives and thinks 9-5 is plenty, with the odd exception near rough
deadlines. Understands the 3 months learning curve and productivity gap
of engineers.
The Bad: Believes in 100% productivity all the time. Equates hours with productivity. Continually whines to management for more people.
The Ugly: Also believes in
9-5... 9am to 5am. When the project invariably run late throws in more
people. Expects immediate increase in team productivity.
Now apply the statistical analysis of your choice to get a number to
apply to your current manager. I've had the honour of working (once)
for one of The Good project managers. Most of the time they ranged
between the bad and the maybe-someday-will-be-good. It's when you hit
The Ugly... As I've said, I wish we could estimate this before
committing to an employer. Anyone looking for a ruby hacker in Sydney?
Previous Topic
