Providian Trust Case Study

Submitted by: Submitted by

Views: 323

Words: 3776

Pages: 16

Category: Business and Industry

Date Submitted: 12/09/2013 01:52 AM

Report This Essay

RUNNING HEAD: Providian Trust case study analysis

1

Providian Trust case study analysis

Providian Trust case study analysis Table of Contents I. II. III. Critical Issues Company History & Case Description Misbalance between the ISS Triangle A. Business Strategy B. IT/IS Strategy C. Organizational Strategy D. Culture in the Front and Back Office E. The Vision IV. Project Management A. Project Management Triangle B. Missing Top Management Support C. Missing and Wrong Communication D. Missing Responsibilities V. Change Management A. Missing User Involvement B. Wrong Testing C. Wrong Training D. No Defined Milestones VI. Reengineering A. Cross Functionality B. Break away from old Processes VII. VIII. Conclusion References

2

3 4 5 5 5 6 6 7 8 8 9 10 11 12 12 13 13 14 15 15 15 16 17

Providian Trust case study analysis Critical Issues

3

Due to the complexity of the project case, a lot of critical factors occurred throughout the implementation of Access Plus. Critical issues were: 1. Misbalance between the ISS triangle The business strategy of Providian Trust, to be a leading provider of financial and trustee services together with good service, was lacking support of the IT/IS strategy through outdated information systems. The organizational strategy, which was grown over time and heavily influenced by change-resistant corporate culture, was characterized by outdated work processes and supported inefficiency and did not support the business strategy either. 2. Project Management The project triangle for Providian was strictly planned top-down by Michael LeBlanc in order to be on time and within budget. Missing top management support, unclear responsibilities, and an inefficient and feedback resistant communication environment led to a reduced project scope. Furthermore, it led to a final project status that would accept minor issues to arise shortly after the go-live of the new system. 3. Change Management The change management process was...