Critical issues in abandoned information systems development projects
Communications of the ACM
International perspectives: software strategies in developing countries
Communications of the ACM
Software developer perceptions about software project failure: a case study
Journal of Systems and Software - Special issue on software engineering education and training for the next millennium
Toward an Integrated Theory of IT-related Risk Control
HOIT '00 Proceedings of the IFIP TC9 WG9.3 International Conference on Home Oriented Informatics and Telematics,: Information, Technology and Society
Software project risks and their effect on outcomes
Communications of the ACM - Human-computer etiquette
Software Security: Building Security In
Software Security: Building Security In
IT Auditing: Using Controls to Protect Information Assets
IT Auditing: Using Controls to Protect Information Assets
Identifying Software Project Risks: An International Delphi Study
Journal of Management Information Systems
Journal of Management Information Systems
An AHP-based methodology to rank critical success factors of executive information systems
Computer Standards & Interfaces
Hi-index | 0.00 |
Traditionally, project success/failure is considered only after the project is completed or cancelled. Integrating project success and failure factors knowledge and software engineering activities would result in a situation where project success/failure is considered as part of the development process, leading to more successful software projects. This article aims to identify the common issues responsible for IT projects' success/failure to develop a deeper understanding of these root causes. Knowledge about success can be used to understand failure and vice versa. Therefore, generic taxonomies of the root causes are developed for that purpose. Knowledge of these taxonomies is integrated into software development and management activities to help software developers and project managers complete projects successfully.