Australian software development: What software project management practices lead to success?

Proceedings of the Australian Software Engineering Conference, ASWEC

Volumn 2005, Issue , 2005, Pages 70-77

  Verner, J M ^a   Cerpa, N ^b  

^a CSIRO   (Australia)

^b UNIVERSIDAD DE TALCA   (Chile)

Author keywords

[No Author keywords available]

Indexed keywords

COMPUTER SOFTWARE; LIFE CYCLE; PRODUCT DEVELOPMENT; PROJECT MANAGEMENT; REQUIREMENTS ENGINEERING; RISK ASSESSMENT;

LIFECYCLE METHODOLOGY; POST MORTEM REVIEWS; SOFTWARE PROJECTS;

SOFTWARE ENGINEERING;

EID: 33646588679     PISSN: None     EISSN: None     Source Type: Conference Proceeding    
DOI: 10.1109/ASWEC.2005.14     Document Type: Conference Paper

References (21)

1. Boehm B. W., Software Engineering Economics, Prentice Hall, Englewood Cliffs, NJ, 1981.
2. Boehm B. W., "Software Risk Management Principles and Practice", IEEE Software, Jan/Feb, 1991, pp. 32-41.
3. Brooks F. P. Jr., The Mythical Man Month. Essays on Software Engineering, Addison Wesley, USA, 1975.
4. Brassler P. "Knowledge Management at a Software House: A progress report" Proc Workshop on Learning Organizations, 1999, pp. 77-83.
5. CMMI http://www.sei.cmu.edu/cmmi/accessed 5th July 2004.
6. Collier B, T. DeMarco and P. Fearey, "A Defined Process for Project Postmortem Review", IEEE Software, July/August, 1996, pp. 65-72.
7. DeMarco T. and T. Lister, Waltzing With Bears, Dorset House Publishing New York NY, 2003.
8. Glass R "Error-Free Software Remains Extremely Elusive", IEEE Software, Jan/Feb, 2003, pp. 103, 104.
9. Glass R. L., "Frequently Forgotten Fundamental Facts about Software Engineering" IEEE Software, July/August, 2001, pp. 112, 110, 111.
10. Glass R. L., "Project Retrospectives, and Why They Never Happen", IEEE Software, September/October, 2002, pp. 112, 111.
11. Jurison, J., Communications of AIS, Software Project Management, The Manager's View, Volume 2, 1999, Article 17.
12. Kerth, N. L., Project Retrospectives: A Handbook for Team Reviews, Dorset House Publishing, New York 2001.
13. Keuffel, W., "Planning for and mitigating risk" Software Development Vol. 7, No 9, 1999, pp. 81-85.
14. Kwak, Y. H. and Stoddard J., "Project risk management: Lessons learned from software development environments", Technovation, 2004.
15. Kwak, Y. H. and Ibbs, C. W. "Calculating project management's return on investment" Project Management Journal, Vol 31, No 2, 2000, pp. 38-47
16. Moynihan T., "How experienced Project Managers Assess Risk", IEEE Software, May/June, 1997, pp. 35-41.
17. Neill C. J. and Laplante P. A., Requirements Engineering: State of the Practice" IEEE Software, November/December, 2003, pp. 40-45.
18. Osmundson J. S., Michael J. B., Machniak, M. J., and Grossman M. A., "Quality management metrics for software development" Information and Management, 2003.
19. Schenk, K.D and Vitalari, N. P., et al. "Differences Between Novice and Expert Systems Analysts: What Do We Know and What Do We Do?", Journal of Management Information Systems, Vol. 15, Issue 1, Summer 1998, pp.9-51.
20. Verner J. M. and W. M. Evanco "In-house Software Development: What Software Project Management Practices Lead to Success?" IEEE Software, Jan/Feb, 2005, pp. 86-93.
21. Yourdon E., "A tale of two futures" IEEE Software January-February 1998, pp23-29.