Campus-based industrial software projects: risks and rewards
ITiCSE '99 Proceedings of the 4th annual SIGCSE/SIGCUE ITiCSE conference on Innovation and technology in computer science education
Some observations on software quality
ACM-SE 37 Proceedings of the 37th annual Southeast regional conference (CD-ROM)
The Euro, Y2K, and the US Software Labor Shortage
IEEE Software
The Software Manager's Toolkit
IEEE Software
An Approach for Cross-Discipline Requirements Engineering Process Patterns
ICRE '98 Proceedings of the 3rd International Conference on Requirements Engineering: Putting Requirements Engineering to Practice
COMPSAC '00 24th International Computer Software and Applications Conference
COMPSAC '00 24th International Computer Software and Applications Conference
A Stochastic Model of Human Errors in Software Development: Impact of Repair Times
ISSRE '99 Proceedings of the 10th International Symposium on Software Reliability Engineering
Hypermedia Systems Development Practices: A Survey
IEEE Software
How university professors teach project management for information systems
Communications of the ACM - Spyware
What do software practitioners really think about project success: an exploratory study
Journal of Systems and Software
Quantitative aspects of outsourcing deals
Science of Computer Programming
Teaching software project management using simulations
Proceedings of the 11th annual SIGCSE conference on Innovation and technology in computer science education
Successful software project and products: An empirical investigation
Proceedings of the 2006 ACM/IEEE international symposium on Empirical software engineering
Information and Software Technology
Risk management in ERP project introduction: Review of the literature
Information and Management
Proceedings of the the 6th joint meeting of the European software engineering conference and the ACM SIGSOFT symposium on The foundations of software engineering
The 6th Joint Meeting on European software engineering conference and the ACM SIGSOFT symposium on the foundations of software engineering: companion papers
What went wrong? A survey of problems in game development
Computers in Entertainment (CIE) - SPECIAL ISSUE: Media Arts and Games
Time as symbolic currency in knowledge work
Information and Organization
Evaluating logistic regression models to estimate software project outcomes
Information and Software Technology
Why the electronic land registry failed
REFSQ'12 Proceedings of the 18th international conference on Requirements Engineering: foundation for software quality
Knowledge of IT Project Success and Failure Factors: Towards an Integration into the SDLC
International Journal of Information Technology Project Management
| Hi-index | 4.10 |
Software management consultants have something in common with physicians: both are much more likely to be called in when there are serious problems rather than when everything is fine. Examining large software systems-those in excess of 5000 function points (which is roughly 500000 source code statements in a procedural programming language such as Cobol or Fortran)-that are in trouble is very common for management consultants. Unfortunately, the systems are usually already late, over budget, and showing other signs of acute distress before the study begins. The consultant engagements, therefore, serve to correct the problems and salvage the system-if, indeed, salvaging is possible. The failure or cancellation rate of large software systems is over 20 percent. Of those that are completed, about two thirds experience schedule delays and cost overruns that may approach 100 percent. Roughly the same number are plagued by low reliability and quality problems in the first year of deployment. Yet some large systems finish early, meet their budgets, and have few, if any, quality problems. How do these projects succeed, when so many fail?