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

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?.
  • Comment on Re^2: Musings: Why do well-intentioned projects go so wrong, so often?

Replies are listed 'Best First'.
Re^3: Musings: Why do well-intentioned projects go so wrong, so often?
by pmonk4ever (Friar) on Dec 07, 2007 at 22:46 UTC
    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."

[reply]

In Section Meditations