This book sets out to address the causes of IT project failure and provides the reader with an opportunity so often denied within their own workplace - to learn the lessons from project failure. It uses private and public sector case studies to show how projects can fail easily if only a small number of critical success factors are not met.
Key Features
Understand the impact of failed projects and why they failed in the first place.
Provides you with a comprehensive set of guidelines and techniques to help deliver a successful IT project.
Helps you understand the strengths and weaknesses of IT methodologies used today.
Learn valuable lessons from previous project failures.
Understand how the behaviour of the project team and key stakeholders can influence the outcome of the project.
.
Sprache
Verlagsort
Verlagsgruppe
Pearson Education Limited
Zielgruppe
Maße
Höhe: 234 mm
Breite: 188 mm
Dicke: 18 mm
Gewicht
ISBN-13
978-0-201-75606-7 (9780201756067)
Copyright in bibliographic data and cover images is held by Nielsen Book Services Limited or by the publishers or by their respective licensors: all rights reserved.
Schweitzer Klassifikation
David Yardley is currently a Principal Consultant working for CACI (UK) Ltd and has over fifteen years' experience of working in IT industry. His experience spans IT projects within many different business sectors including: aero-engineering, computer manufacture, telecommunications, transport as well as many public sector projects.
David is a member of the British Computer Society and has written articles for Computing on data centre automation and diagnosing network failure. He is also the author of Careers in Computing and IT andGetting a Top Job in IT, published by Kogan Page.
Introduction
PART I: ESTABLISHING THE IS PROJECT FRAMEWORK 1. Why do IS Projects fail?
The Reality Gap / The scope for IS project failure
2. Enabling Change - The Business of IT
Strategic business planning / Aligning the It strategy with the business / Building the business case / Managing change / Resistance to change / The Physiological Impact of Change / Change: Critical success factors 3. Managing the Requirements
What is requirements management? / The requirements management lifecycled / Barriers to effective requirements management / The dangers of using software packages
4. The IS methodology - a framework for development The role of IS methodologies / A comparism of popular IS methodologies
PART II: PLANNING FOR SUCCESS
5. Planning the Project
What is a project? / Hallmarks of a healthy project / The project plaln / Case study: The London Ambulance Service Computer- Aided Despatch System
6. Project building blocks: Processes
Project Management / Programme management / Risk management / Configuration management / Processes: #critical success factors
7. Planning the benefits
Why do IS projects fail to deliver benefits? / The nature of IS investments / Case study: A major airline company / Building the benefits - the benefit management cycle / Techniques for investment appraisal / Benefit mangement: Critical success factors
PART III: DESIGN AND DEVELOPMENT
8. Project building blocks: People
The human element of IS project failure / Key causes of project team weakness / The role of stakeholders in the project / Case study: An international airline Improving the human aspect of the project / Case study: A major telecommunications company / Supplier management / People: Critical success factors
9. Managing Software Development
The software development lifecycle / Case study - Denver International Airport Baggage Stystem / Measuring softwre development complexity / Achieving software development excellence / Managing softwre develoment: critical success factors
10. The need for quality
What is quality: / Project quality management / Software quality assurance / Total Quality Management / Case study: Intel / Barriers to quality / Quality - critical succes factors
PART IV: PROJECT DELIVERY
11. The importance of testing
Why do application systems fail? / The case for testing / Case study: The Lessons of Ariane 5 / Making the investment count: testing tools / The testing process / Making the transition from testing to product release /
12. Learning the lessons
Learning the lessons
