Beefy Boxes and Bandwidth Generously Provided by pair Networks
Just another Perl shrine
 
PerlMonks  

Re: Musings: Why do well-intentioned projects go so wrong, so often?

by apl (Monsignor)
on Dec 05, 2007 at 16:16 UTC ( [id://655114]=note: print w/replies, xml ) Need Help??


in reply to Musings: Why do well-intentioned projects go so wrong, so often?

One word: Management.

I've lost track of the number of times I've informed management where a project was and when it would be ready to be released, and they've responded by telling me when they wanted it released (usually one to two weeks earlier).

How difficult is it to understand "We need to regression test before we can release?"

Replies are listed 'Best First'.
Re: Musings: Why do well-intentioned projects go so wrong, so often?
by pmonk4ever (Friar) on Dec 05, 2007 at 21:48 UTC
    Regression Testing?!?! Bite your tongue!! Why would Management want to discover regression issues? "Those are issues that 'Rev. 9 million 5' can fix"..."an undocumented feature"!!! :-D

    I agree with apl we must have Regression Tests, you must discover what broke when you changed/added 'XYZ'!!! No excuses for not doing Regression Testing, however Micro$haft ships patches without testing all the time...forcing every IT shop in the country to do their OWN testing before deploying a fix enterprise-wide.

    ki6jux

    "No trees were harmed in the creation of this node. However, a rather large number of electrons were somewhat inconvenienced."

      One doesn't have to dwell on Regression Testing. Management has their priorities even as Programmers do. The difference is, they don't usually tell us why they need to shave time off the estimate. All we see is that we're being forced to ship something which we know is not complete.

      But who gets the blame? You'll notice the title of this thread is not Who do so many projects get mismanaged, so often?.
        Right you are, apl! They are operating under the 'mistaken' assumption that there's always money to fix it later. However, if you work on a government contract, they expect you to do it right the first time AND test it AND make money at the same time!!!!

        And we get the blame, the technical folks, they fire the innocent and promote the guilty!

        Ah, well, what's new...I'm preaching to the choir here! Those who have a major project in their experience know this by heart!

        Regression Testing is what saves your bacon with the customer!!!

        ki6jux

        "No trees were harmed in the creation of this node. However, a rather large number of electrons were somewhat inconvenienced."

Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Node Status?
node history
Node Type: note [id://655114]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others taking refuge in the Monastery: (5)
As of 2024-03-29 11:12 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found