This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
In-House Software Development: What Project Management Practices Lead to Success?
January/February 2005 (vol. 22 no. 1)
pp. 86-93
June M. Verner, National ICT Australia
William M. Evanco, Drexel University
A survey examined the software development practices of a number of software practitioners in large businesses that are involved almost exclusively with in-house software development. The results indicate that for a successful project, the project manager needs a clear vision of the project, requirements must be of good quality, and estimates should be made only after the appropriate requirements have been identified. On projects that fail, many recognized software practices aren?t being applied. Most projects in the survey began with unclear requirements. Risk management isn?t routinely a part of development, and the organizations aren?t learning from their mistakes because they don?t routinely perform postmortem reviews. Also, senior management appears to lack an appreciation of the steps necessary to successfully execute a project.
Index Terms:
project success, software project management, software development risk, postmortem review
Citation:
June M. Verner, William M. Evanco, "In-House Software Development: What Project Management Practices Lead to Success?," IEEE Software, vol. 22, no. 1, pp. 86-93, Jan.-Feb. 2005, doi:10.1109/MS.2005.12
Usage of this product signifies your acceptance of the Terms of Use.