Access the full text.
Sign up today, get DeepDyve free for 14 days.
Capers Jones (1996)
Why software fails, 4
S. McConnell (2006)
Software Estimation: Demystifying the Black Art
R. Charette (2005)
Why software fails [software failure]IEEE Spectrum, 42
Diana White, J. Fortune (2002)
Current practice in project management — an empirical studyInternational Journal of Project Management, 20
A. Boonstra (2013)
How do top managers support strategic information system projects and why do they sometimes withhold this supportInternational Journal of Project Management, 31
Roy Schmidt, K. Lyytinen, M. Keil, P. Cule (2001)
Identifying Software Project Risks: An International Delphi StudyJournal of Management Information Systems, 17
T. Cooke‐Davies (2002)
The “real” success factors on projectsInternational Journal of Project Management, 20
L. Crawford (2005)
Senior management perceptions of project management competenceInternational Journal of Project Management, 23
D. McFadden (1972)
Conditional logit analysis of qualitative choice behavior
O. Zwikael (2008)
Top management involvement in project management. Exclusive support practices for different project scenariosInternational Journal of Managing Projects in Business, 1
Donald Harter, M. Krishnan, S. Slaughter (2000)
Effects of Process Maturity on Quality, Cycle Time, and Effort in Software Product DevelopmentManagement Science, 46
N. Doherty, M. King (2001)
An investigation of the factors affecting the successful treatment of organisational issues in systems development projectsEuropean Journal of Information Systems, 10
M. Jørgensen, Dag Sjøberg (2001)
Impact of effort estimates on software project workInf. Softw. Technol., 43
Kjetil Moløkken, M. Jørgensen (2003)
A review of software surveys on software effort estimation2003 International Symposium on Empirical Software Engineering, 2003. ISESE 2003. Proceedings.
A. Lederer, J. Prasad (2000)
Software management and cost estimating errorJ. Syst. Softw., 50
A. Lederer, J. Prasad (1992)
Nine management guidelines for better cost estimatingCommun. ACM, 35
J. Fortune, Diana White (2006)
Framing of project critical success factors by a systems modelInternational Journal of Project Management, 24
O. Zwikael (2008)
Top management involvement in project management: A cross country study of the software industryInternational Journal of Managing Projects in Business, 1
Bill Pitterman (2000)
Telcordia Technologies: The Journey to High MaturityIEEE Softw., 17
A. Lederer, J. Prasad (1995)
Causes of inaccurate software development cost estimatesJ. Syst. Softw., 31
M. Jørgensen, M. Shepperd (2007)
A Systematic Review of Software Development Cost Estimation StudiesIEEE Transactions on Software Engineering, 33
J. Thomas, Connie Delisle, Kam Jugdev, Pamela Buckle (2002)
Selling Project Management to Senior Executives: The Case for Avoiding Crisis SalesProject Management Journal, 33
Joe Saur (2003)
Review of “Five Core Metrics: The Intelligence Behind Successful Software Management by Lawrence H. Putnam & Ware Myers.” Dorset House 2003ACM SIGSOFT Softw. Eng. Notes, 28
J. Hihn, H. Habib-agahi (1991)
Cost estimation of software intensive projects: a survey of current practices[1991 Proceedings] 13th International Conference on Software Engineering
K. Ewusi-Mensah (2003)
Software Development Failures
T. Jones (1998)
Estimating software costs
M. Genuchten (1991)
Why is Software Late? An Empirical Study of Reasons For Delay in Software DevelopmentIEEE Trans. Software Eng., 17
Raymond Young, E. Jordan (2008)
Top management support: mantra or necessity?
Purpose – A cost estimate is considered to have a high impact on software project success. Because of this, different methodologies for creating an accurate estimate have been studied over decades. Many methodologies produce accurate results, when used properly. However, software projects still suffer from inaccurate estimates. The disparity may result from organisational hindrances. This paper focuses on top management support (TMS) for software cost estimation (SCE). The purpose of this paper is to identify current practices and attitudes of top management involvement in SCE, and to analyse the relationship between these two and project success. Design/methodology/approach – A list of 16 TMS practices for SCE has been developed. A survey was conducted to capture the frequency of use and the experienced importance of support practices. Data has been collected from 114 software professionals in Finland. Correlations between the frequency of use, attitudes and project success were analysed. Findings – Top management invests a significant amount of attention in SCE. The extent of use and experienced importance do not correlate strongly with each other or project success. Research limitations/implications – The results may lack generalisability. Researchers are encouraged to validate the results with further studies. Practical implications – Software professionals invite senior managers to participate in SCE. A list of practices for participating is provided. Originality/value – This paper suggests a list of 16 TMS practices for SCE. The paper also reports on the extent of use and experienced importance of practices, and the correlations between these two and project success.
International Journal of Managing Projects in Business – Emerald Publishing
Published: Jun 1, 2015
Read and print from thousands of top scholarly journals.
Already have an account? Log in
Bookmark this article. You can see your Bookmarks on your DeepDyve Library.
To save an article, log in first, or sign up for a DeepDyve account if you don’t already have one.
Copy and paste the desired citation format or use the link below to download a file formatted for EndNote
Access the full text.
Sign up today, get DeepDyve free for 14 days.
All DeepDyve websites use cookies to improve your online experience. They were placed on your computer when you launched this website. You can change your cookie settings through your browser.