By Topic

Our worst current development practices

Sign In

Cookies must be enabled to login.After enabling cookies , please use refresh or reload or ctrl+f5 on the browser for the login options.

Formats Non-Member Member
$31 $13
Learn how you can qualify for the best price for this item!
Become an IEEE Member or Subscribe to
IEEE Xplore for exclusive pricing!
close button

puzzle piece

IEEE membership options for an individual and IEEE Xplore subscriptions for an organization offer the most affordable access to essential journal articles, conference papers, standards, eBooks, and eLearning courses.

Learn more about:

IEEE membership

IEEE Xplore subscriptions

1 Author(s)
Jones, C. ; Software Productivity Res., Burlington, MA, USA

Successful software projects can result from avoiding the more serious mistakes that lead to disaster. Specifically, we must look at the actual results of similar projects; make planning and estimating formal activities; plan for and control creeping requirements; use formal inspections as milestones for tracking project progress and software disasters; and collect accurate measurement data, during the current project, to use with future projects. There is no substitute for solid empirical data used by capable project managers who are supported by automated estimating and planning tools. This combination can almost always be successful. By contrast, no data at all, unprepared managers, and manual estimating and planning are consistently characteristic of our industry's major software disasters

Published in:

Software, IEEE  (Volume:13 ,  Issue: 2 )