I. PREPARING THE ORGANIZATION FOR IT PROJECTS
1. Why do IS projects fail?
The reality gap.
Types of IS project failure.
The scope for IS project failure.
The role of project management in project failure.
Defining project success.
Case study: Concorde.
Defining project management success.
The overlap between the project and project management.
Project vs project management failure.
Case study: Company W.
2. Enabling change--the business of IT.
Strategic business planning.
Aligning the IT strategy with the business.
Implementing the strategy.
Building the business case.
Case study: Company X.
Structure and content.
The change cycle.
Resistance to change.
Case study: The Piper Alpha disaster.
Learning the lessons.
The Milgram experiments.
Case study: Philips Electronics.
The psychological impact of change.
The Hawthorne studies.
Herzberg's motivation-hygiene theory.
Case study: Cerner.
Change: critical success factors.
3. Managing the requirements.
What is requirements management?
The requirements management lifecycle.
Estimating the cost of requirements.
Assessing the impact of requirements.
Barriers to effective requirements management.
Principal causes of requirements management failure.
The dangers of using software packages.
Evaluating a software package.
Selecting the right software package.
Requirements management: critical success factors.
4. The IS methodology--a framework for project delivery.
The role of IS methodologies.
The limitations of IS methodologies.
A comparison of popular IS methodologies.
Systems development methodologies.
Project management methodologies.
IS methodologies: critical success factors.
II. PLANNING FOR SUCCESS
5. Planning the project.
What is a project?
Types of IS projects.
Hallmarks of a healthy project.
A capable and experienced project manager.
Clear business objectives and requirements.
Competent and committed staff.
Managing project constraints.
The project plan.
Gaining benefit from the plan.
Case study: The London Ambulance Service Computer-Aided Dispatch System.
Planning the project: critical success factors.
6.Project building blocks: processes.
What is project management?
Key features of project management.
The project lifecycle.
What is program management?
Key features of program management.
A framework for program management.
What is risk management?
The risk management process.
What is configuration management?
The configuration management process.
Introducing a configuration management system.
Benefits of 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: Company Y.
Building the benefits--the benefits management process.
The benefits management lifecycle.
Identifying the benefits.
Developing the benefits management plan.
Executing the benefits plan.
Evaluating the outcome.
Determining the potential for future benefits.
Techniques for investment appraisal.
Benefits management: critical success factors.
III. DESIGN AND DEVELOPMENT
8. Project building blocks: people.
The human element of IS project failure.
Internal pressures to deliver.
Resistance to change.
Poorly performing project teams.
Key causes of project team weakness.
Uncontrolled problem employees.
Poor working conditions.
A lack of training and support.
Adding developers late to a project.
The role of stakeholders in the project.
Case study: The London Stock Exchange Taurus project.
Improving the human aspects of the project.
Promoting effective communication.
Reducing the blame culture.
Building the core project team.
Training, coaching, and mentoring.
Case study: Company Z.
Managing the contract.
The benefits of supplier management.
The causes of failure.
People: critical success factors.
9. Managing software development.
The software development lifecycle.
Traditional software development.
The causes of software development failure.
Case study: Denver International Airport Baggage System.
The global scope of failure.
Measuring software development complexity.
Defining software complexity.
The need for software metrics.
Presenting the estimates.
Achieving software development excellence.
The software Capability Maturity Model.
Reducing software project failures using the CMM.
Using tools and techniques to implement the CMM.
Reducing software development schedule failure.
Planning for software excellence.
Managing software development: critical success factors.
10. The need for quality.
What is quality?
Project quality management.
Software quality assurance.
SQA and the systems development lifecycle.
Using SQA to support verification and validation.
Total Quality Management.
The benefits of TQM.
Case study: Intel.
Barriers to quality.
Quality: critical success factors.
IV. PROJECT DELIVERY.
11. The importance of testing.
Why do application systems fail?
Vague and misleading user requirements.
Changing software requirements.
The case for testing.
The origins of testing failure.
The objectives of testing.
The scope of testing.
Case study: The lessons of Ariane 5.
Making the investment count: iteration.
Making the investment count: testing tools.
The testing process.
Test program management.
Making the transition from testing to product release.
Key deployment activities.
Case study: UK Passport Agency.
Testing: critical success factors.
12. Learning the lessons.
Project failure factors.
Learning the lessons--20 ways to reduce IS project failure.
The potential for long-term project success.
The London Ambulance Service.
The UK Passport Agency.