As you can read in their e-mail promoting some new requirements management application here: http://now.eloqua.com/es.asp?s=510&e=3B660AD57179453CB11DB288B8F7B24C
<font color="#000000" face="Arial, Helvetica, sans-serif" size="2"><span style="font-size: 12px;">It’s
amazing that poor requirements account for 71% of failed software
projects. And, unfortunately, no matter how efficient a requirements
management system you have, it might not be enough to save your
projects from joining that statistic. That’s why defining complete and
accurate requirements is a critical first step to ensuring you manage
the right requirements throughout a project's lifecycle.</font>
To end the sales pitch with:
<font color="#000000" face="Arial, Helvetica, sans-serif" size="2">Defining
requirements correctly up front can be pivotal in preventing the chain reaction of poor communication and
missed deadlines that lead to rework and project failure. Don’t let this happen to you. Join the other 29%.</font>
I'll be happy to join you in the other part of the failed projects statistics, Borland! :)
<font color="#000000" face="Arial, Helvetica, sans-serif" size="2"></font>