Comment On Save the Project for Failure

If it takes two contract developers six months to drive a project to failure, then four developers should be able to fail in half the time! Josh assumed that was why he and Sam were carted out to the client site and tossed into the oubliette of the PowerPac project. They were armed with nothing but a rusty spoon and a requirements document so old it needed to be stored in an oxygen-free environment. [expand full text]
« PrevPage 1 | Page 2 | Page 3Next »

Re: Save the Project for Failure

2012-01-31 10:34 • by PiisAWheeL
Just to piss off the frist kiddies!

Addendum (2012-01-31 10:40):
On a more serious note... I think Doug would have had a terrible accident of some sort on his way to work one day :)

Re: Save the Project for Failure

2012-01-31 10:35 • by manager (unregistered)
And this is why it's good to be a manager who was a developer and to listen to what your devs say.

Then, we fire people like Doug.

Re: Save the Project for Failure

2012-01-31 10:41 • by Fred (unregistered)
It also draws something far more sinister: project managers
Indeed.
who want to steal that glory for themselves.
But you repeat yourself.

Project Managers are TRWTF, 9.7 times out of 10.

I have a theory that a Project Manager is actually just a 7-line VB loop:

"Is it done yet?"

"When will it be done?"

GO TO 1

Re: Save the Project for Failure

2012-01-31 10:49 • by An Old Hacker (unregistered)
373391 in reply to 373390
The position of project manager was originally created to run the Manhattan Project. From the success there, it migrated into business. Point being, if you're build the bomb, or some other complex project involving several managers (or directors), you're going to need someone whose sole job is to keep up with the overall status of the project, and to ensure that resources (including people) don't get diverted to competing priorities without anyone considering what that means.

But for a single team of four people?


Re: Save the Project for Failure

2012-01-31 10:49 • by Paul Neumann (unregistered)
It sounds like Josh has a chip on his shoulder and is the real glory hog in this story. Just because you don't understand industry best practices doesn't mean they are meaningless or that the person enforcing them is stupid. The original developers were flexible enough to adapt to the contractor's style, but the contractors couldn't take being managed properly by a real project manager. That is TRWTF!

Re: Save the Project for Failure

2012-01-31 10:49 • by iToad (unregistered)
One incompetent manager can easily undo the work of a hundred competent employees.

Re: Save the Project for Failure

2012-01-31 10:51 • by Paul Neumann (unregistered)
Where I work, we have 4 project managers, 2 product owners, 3 team managers, 8 business analysts, 2 teams of 3 developers and a QA. That is the only way for things to be accomplished properly.

Re: Save the Project for Failure

2012-01-31 10:53 • by frits
Doug sounds like a real quier.

Re: Save the Project for Failure

2012-01-31 10:56 • by Jeff Olson (unregistered)
TRWTF is TFS

Re: Save the Project for Failure

2012-01-31 10:56 • by Comrade (unregistered)
In Soviet Russia, the project manages you!

CAPTCHA: opto (root): this is not the optomum work environment.

Re: Save the Project for Failure

2012-01-31 10:59 • by Chuck Lester (unregistered)
373398 in reply to 373397
Well, if Dough was from the client side, maybe they wanted to make sure the project failed, in order to avoid some payments, or because of internal battles.

Re: Save the Project for Failure

2012-01-31 11:00 • by operagost
Looks like Nagesh took an English class and renamed himself "Paul Neumann".

Re: Save the Project for Failure

2012-01-31 11:01 • by C-Octothorpe
373400 in reply to 373392
Paul Neumann:
It sounds like Josh has a chip on his shoulder and is the real glory hog in this story. Just because you don't understand industry best practices doesn't mean they are meaningless or that the person enforcing them is stupid. The original developers were flexible enough to adapt to the contractor's style, but the contractors couldn't take being managed properly by a real project manager. That is TRWTF!
Meh, 2/10. You might get a few bites...

Re: Save the Project for Failure

2012-01-31 11:02 • by C-Octothorpe
373401 in reply to 373394
Paul Neumann:
Where I work, we have 4 project managers, 2 product owners, 3 team managers, 8 business analysts, 2 teams of 3 developers and a QA. That is the only way for things to be accomplished properly.
You work for the Greek government too?!

Re: Save the Project for Failure

2012-01-31 11:05 • by jmac the man (unregistered)
373402 in reply to 373391
An Old Hacker:
The position of project manager was originally created to run the Manhattan Project.


The same Manhattan Project that eventually exploded several times, with each explosion causing more and more destruction?

Obviously a Project Manager was involved.

Re: Save the Project for Failure

2012-01-31 11:13 • by Fred (unregistered)
373404 in reply to 373394
Paul Neumann:
Where I work, we have 4 project managers, 2 product owners, 3 team managers, 8 business analysts, 2 teams of 3 developers and a QA. That is the only way for things to be accomplished properly.
And when the costs start getting too bloated, cut the developers. Oh, and QA? That's a joke, right?

Re: Save the Project for Failure

2012-01-31 11:14 • by Jack (unregistered)
373405 in reply to 373390
Fred:
I have a theory that a Project Manager is actually just a 7-line VB loop:

"Is it done yet?"

"When will it be done?"

GO TO 1
Vex not the geeks, lest ye be replaced by a seven line script.

Re: Save the Project for Failure

2012-01-31 11:17 • by PiisAWheeL
373406 in reply to 373390
Fred:
It also draws something far more sinister: project managers
Indeed.
who want to steal that glory for themselves.
But you repeat yourself.

Project Managers are TRWTF, 9.7 times out of 10.

I have a theory that a Project Manager is actually just a 7-line VB loop:

"Is it done yet?"

"When will it be done?"

GO TO 1

I like how you are billing for 4 lines of white-space ;)

Re: Save the Project for Failure

2012-01-31 11:22 • by luptatum (unregistered)
373407 in reply to 373406
PiisAWheeL:
Fred:
It also draws something far more sinister: project managers
Indeed.
who want to steal that glory for themselves.
But you repeat yourself.

Project Managers are TRWTF, 9.7 times out of 10.

I have a theory that a Project Manager is actually just a 7-line VB loop:

"Is it done yet?"

"When will it be done?"

GO TO 1

I like how you are billing for 4 lines of white-space ;)



That reminded me of a few times I heard some bozo devs (especially conducting job interviews) brag about their app, like: "this app has 20 thousand lines of code, you know" (like, that's a measure of anything related to features or quality).

Re: Save the Project for Failure

2012-01-31 11:32 • by PiisAWheeL
373408 in reply to 373407
luptatum:
PiisAWheeL:
Fred:
It also draws something far more sinister: project managers
Indeed.
who want to steal that glory for themselves.
But you repeat yourself.

Project Managers are TRWTF, 9.7 times out of 10.

I have a theory that a Project Manager is actually just a 7-line VB loop:

"Is it done yet?"

"When will it be done?"

GO TO 1
I like how you are billing for 4 lines of white-space ;)
That reminded me of a few times I heard some bozo devs (especially conducting job interviews) brag about their app, like: "this app has 20 thousand lines of code, you know" (like, that's a measure of anything related to features or quality).

No, but it is a pretty good measure of what the invoice looks like.

It also just occured to me that your 7 line function doesn't accept any input... well played :)

Re: Save the Project for Failure

2012-01-31 11:35 • by Chip (unregistered)
373409 in reply to 373407
The size of the application and number of people on the team gives a good idea of how large a project a developer has experience working with. As an interviewer, I'm very interested to know that. As a developer, I want people to know it if I single-handedly managed a large codebase for a successful project. That demonstrates my organizational skills.

Re: Save the Project for Failure

2012-01-31 11:36 • by the beholder (unregistered)
373410 in reply to 373399
operagost:
Looks like Nagesh took an English class and renamed himself "Paul Neumann".
Nope, it must be geoffrey. Nagesh would be telling us how he has 2 levels of project manager above him undercutting his productivity.

Following there would be a picture supposed to be taken in Hyderabad showing some clumsy, extremely dangerous structure where 3 people are working, two of them spatially above the other.

Re: Save the Project for Failure

2012-01-31 11:37 • by frits
373411 in reply to 373409
Chip:
As a developer, I want people to know it if I single-handedly managed a large codebase for a successful project. That demonstrates my lasso skills.

FTFY
Yeehaw!

Re: Save the Project for Failure

2012-01-31 11:42 • by frits
According to this article, small teams beat large teams in efficiency, and are only negligibly slower.

Re: Save the Project for Failure

2012-01-31 11:45 • by Larry (unregistered)
Project Manager 2.0:

for $task in @tasks do
print "Is task $task done yet?"
read no
print "Well what percent complete is it?"
read dunno
print "Well what would you guess?"
read percent
print "OK can I say it is " percent * 1.3 " percent done then?"
read no
ignore no
done

Re: Save the Project for Failure

2012-01-31 11:52 • by Rosuav (unregistered)
373415 in reply to 373405
Jack:
Fred:
I have a theory that a Project Manager is actually just a 7-line VB loop:

"Is it done yet?"

"When will it be done?"

GO TO 1
Vex not the geeks, lest ye be replaced by a seven line script.


Especially vex not the Unix geeks, who discount you by a further six lines.

$ printf %s%08x `ifconfig|grep -o 'HWaddr [0-9a-f:]*'|sed -e 's/HWaddr //' -e 's/://g' -e '1q'` `command --that --outputs --an --integer`

Re: Save the Project for Failure

2012-01-31 11:55 • by C-Octothorpe
373416 in reply to 373413
Larry:
Project Manager 2.0:

for $task in @tasks do
print "Is task $task done yet?"
read no
print "Well what percent complete is it?"
read dunno
print "Well what would you guess?"
read percent
print "Hmm, last week you said it's " percent * 1.1 " percent done."
read percent * 1.11

print "OK can I say it is " (percent * 1.11) * 1.3 " percent done then?"
read no
ignore no
done
FTFM

Funny when that happens, is it...

Re: Save the Project for Failure

2012-01-31 11:55 • by Paul Neumann (unregistered)
373417 in reply to 373409
Chip:
As a developer, I want people to know it if I single-handedly mangled a large codebase for a successful project. That demonstrates my over-engineering skills.


FTFYFTW

Re: Save the Project for Failure

2012-01-31 12:03 • by C-Octothorpe
373418 in reply to 373409
Chip:
As a developer, I want people to know it if I single-handedly managed a large codebase for an Excel VBA script used by Debbie in Accounting. That demonstrates my bullshitting skills.
RTFY

(Reality-fied That For You)

Re: Save the Project for Failure

2012-01-31 12:11 • by Chris V (unregistered)
Stories like this aren't even mildly amusing to me. They strike far too close to home and really just send my blood pressure into the stratosphere.

Re: Save the Project for Failure

2012-01-31 12:15 • by Ben Jammin (unregistered)
373421 in reply to 373413
Larry:
Project Manager 2.0:

print "OK can I say it is " percent * 1.3 " percent done then?"
read no
ignore no


I love this. Mine always do this to my quotes, and I've learned to adapt. For a project that will take me 80 hours, I say 100. This way, when they tell me I only get 80 (despite telling them 100) I look like a hard worker for pushing harder, and they look good for "managing well". This is better than saying 80 and only getting 60, because when it takes 80, the project is now over-budget, poorly-managed, and lazily-developed.

Re: Save the Project for Failure

2012-01-31 12:17 • by Matt (unregistered)
Where I used to work, this would be less a "Curious Perversion" and more "Another Tuesday".

At first, everything was run and managed by developers, who spent so much time trying to "manage" a project that very little development work got done.

So they created a PMO, which spent so much "managing" projects that no development work got done.

Re: Save the Project for Failure

2012-01-31 12:18 • by RussJudge
If it takes two contractors six months to drive a project to failure, four contractors will achieve that failure in half the time, but it will take twice as long for the failure to be acknowledged.

Re: Save the Project for Failure

2012-01-31 12:24 • by Anketam
373425 in reply to 373421
What kind of schedule padding is this? Normal rule is double. So if it takes in theory 1 week to do you say 2 weeks*. Then you explain that the * means just your part and does not factor in all the other parts that will come after it and should be or have to be done, for example: testing, integration, and QA. So when it is all said and done that one week fix really gets/needs 6+ weeks of schedule to pull it off.

And that does not even factor in padding for spending time on the The Daily WTF.

Re: Save the Project for Failure

2012-01-31 12:26 • by TheCPUWizard
(Knowing there will be backlash)...I actually support having a PRoject Manager anytime the environment (not the team) involves a large number of people.

On the otherhand, nothing in the list of items Doug was doing should be done by a project manager. Instead the PM should take the information from the DEV/QA/etc. teams, distill it down to the information necessary for external consumption, as well as gather extrnal influences, and make sure they are presented to the DEV/QA/etc teams in a coherent manner.

Re: Save the Project for Failure

2012-01-31 12:27 • by C-Octothorpe
373427 in reply to 373423
RussJudge:
If it takes two contractors six months to drive a project to failure, four contractors will achieve that failure in half the time, but it will take twice as long for the failure to be acknowledged.
Another advantage of using four contractors vs. two is that you have effectively doubled you scapegoat count. This is especially important for PMs who, like the mayan people, needed sacrificial lambs in order to appease their gods, or in this case, C-level management.

Re: Save the Project for Failure

2012-01-31 12:28 • by ¯\(°_o)/¯ I DUNNO LOL (unregistered)
373428 in reply to 373394
Paul Neumann:
Where I work, we have 4 project managers, 2 product owners, 3 team managers, 8 business analysts, 2 teams of 3 developers and a QA in a pear tree.

FTFY

Re: Save the Project for Failure

2012-01-31 12:34 • by Paul Neumann (unregistered)
373429 in reply to 373428
No, Nagesh's QA may work from a pear tree, but, our QA works in a cube.

Re: Save the Project for Failure

2012-01-31 12:37 • by Larry (unregistered)
373430 in reply to 373416
C-Octothorpe:

print "Hmm, last week you said it's " percent * 1.1 " percent done."

But then we got some extra management oversight so the project moved backwards.

Re: Save the Project for Failure

2012-01-31 12:40 • by Jeff (unregistered)
373431 in reply to 373430
C-Octothorpe:
print "Hmm, last week you said it's " percent * 1.1 " percent done."

So where is it written that status meetings have to be weekly? Imagine if we held them every 8 working days instead. Productivity would jump 60%!

Re: Save the Project for Failure

2012-01-31 12:45 • by Nagesh
QA is important in any project. Josh should not questioning authority. It is clear that Josh is lone hero programer in organization. We need less heros and more followers.

Re: Save the Project for Failure

2012-01-31 13:05 • by Paul Neumann (unregistered)
373433 in reply to 373431
Jeff:
C-Octothorpe:
print "Hmm, last week you said it's " percent * 1.1 " percent done."

So where is it written that status meetings have to be weekly? Imagine if we held them every 8 working days instead. Productivity would jump 60%!


You are quite correct. Daily status meetings make for shorter meetings and more productive time which is monitored.

Re: Save the Project for Failure

2012-01-31 13:18 • by Salad Fingers (unregistered)
They were armed with nothing but a rusty spoon


I like rusty spoons. I like to touch them.

Re: Save the Project for Failure

2012-01-31 13:24 • by lolcatz (unregistered)
373435 in reply to 373408
PiisAWheeL:
luptatum:
PiisAWheeL:
Fred:
It also draws something far more sinister: project managers
Indeed.
who want to steal that glory for themselves.
But you repeat yourself.

Project Managers are TRWTF, 9.7 times out of 10.

I have a theory that a Project Manager is actually just a 7-line VB loop:

"Is it done yet?"

"When will it be done?"

GO TO 1
I like how you are billing for 4 lines of white-space ;)
That reminded me of a few times I heard some bozo devs (especially conducting job interviews) brag about their app, like: "this app has 20 thousand lines of code, you know" (like, that's a measure of anything related to features or quality).

No, but it is a pretty good measure of what the invoice looks like.

It also just occured to me that your 7 line function doesn't accept any input... well played :)


It is also only 5 lines.

Re: Save the Project for Failure

2012-01-31 13:25 • by Harrow (unregistered)
373436 in reply to 373388
Doug had compiled a PowerPoint full of pretty graphs and dashboards showing nothing but green boxes. He used words like synergy, Agile, "code coverage", "core principles" and "industry standard best practices". It was entirely fabricated nonesense, but management swallowed every drop.
Behold another not even minimally competent management. If you're going to run a software development firm then you should know at least a little bit about what software development is.

This company does not deserve to ever complete a project or earn earn a profit from any client. The sooner these a$$hats go out of business the better.

-Harrow.

Re: Save the Project for Failure

2012-01-31 13:26 • by studog (unregistered)
373437 in reply to 373415
Rosuav:
Jack:
Fred:
I have a theory that a Project Manager is actually just a 7-line VB loop:

"Is it done yet?"

"When will it be done?"

GO TO 1
Vex not the geeks, lest ye be replaced by a seven line script.


Especially vex not the Unix geeks, who discount you by a further six lines.

$ printf %s%08x `ifconfig|grep -o 'HWaddr [0-9a-f:]*'|sed -e 's/HWaddr //' -e 's/://g' -e '1q'` `command --that --outputs --an --integer`


Er, what? I tried
$ printf %s%08x `ifconfig|grep -o 'HWaddr [0-9a-fA-F:]*'|sed -e 's/HWaddr //' -e 's/://g' -e '1q'` `echo 1`

but that just gives me what it looks like it should give me, my MAC in hex with no colons, followed by a number.

How does that replace the perfectly functional seven line script?

Captcha: commoveo, Commoveo here and explain this to me...

Re: Save the Project for Failure

2012-01-31 13:26 • by Nagesh
373438 in reply to 373410
the beholder:
operagost:
Looks like Nagesh took an English class and renamed himself "Paul Neumann".
Nope, it must be geoffrey. Nagesh would be telling us how he has 2 levels of project manager above him undercutting his productivity.

Following there would be a picture supposed to be taken in Hyderabad showing some clumsy, extremely dangerous structure where 3 people are working, two of them spatially above the other.


Those pics from Kolkata and not Hyderabad.

Why the dollar signs?

2012-01-31 13:42 • by frits
373439 in reply to 373436
Harrow:
The sooner these a$$hats go out of business the better.

I'm confused. Do the managers have something to do with Microsoft? ..or Rap?

Re: Why the dollar signs?

2012-01-31 13:46 • by Nagesh
373440 in reply to 373439
frits:
Harrow:
The sooner these a$$hats go out of business the better.

I'm confused. Do the managers have something to do with Microsoft? ..or Rap?


I am more confused then you.

Re: Save the Project for Failure

2012-01-31 13:47 • by PedanticCurmudgeon
TRWTF is that Josh didn't start looking for another job when Doug declared himself QA Officer and Build Officer.
« PrevPage 1 | Page 2 | Page 3Next »

Add Comment