Sign In

Communications of the ACM

Kode Vicious

The Four Horsemen of an Ailing Software Project

one of the four horsemen of the apocalypse

Credit: T.J. Barnwell

back to top 

Dear KV,

Are there any reliable measurements one can use to judge the health of a software project? I have seen many things written about the quality of software but not very much about the quality of a project itself. I ask this because I worry that I am stuck on a failing project, but it is difficult to know if it is really failing. The company I work for alternately feeds and starves the project of resources, while also saying that completing the next release on time is the key to our success. If we are the key to success, why would they periodically starve the project? I keep wondering if I am a frog in a slow boiling pot of water and that I will only know I should have left once it is too late. If there are measures for software quality, there must surely be measures for project quality?


No entries found

Log in to Read the Full Article

Sign In

Sign in using your ACM Web Account username and password to access premium content if you are an ACM member, Communications subscriber or Digital Library subscriber.

Need Access?

Please select one of the options below for access to premium content and features.

Create a Web Account

If you are already an ACM member, Communications subscriber, or Digital Library subscriber, please set up a web account to access premium content on this site.

Join the ACM

Become a member to take full advantage of ACM's outstanding computing information resources, networking opportunities, and other benefits.

Subscribe to Communications of the ACM Magazine

Get full access to 50+ years of CACM content and receive the print version of the magazine monthly.

Purchase the Article

Non-members can purchase this article or a copy of the magazine in which it appears.
Sign In for Full Access
» Forgot Password? » Create an ACM Web Account