4
Week 2 (2) 2007 IS33 IS Failure Cases (cont) 1 COMP3470 IS33 People-Centred Information Systems Development Week 2 : Lecture 2 IS Failure Case Studies (cont.) School of Computing FACULTY OF Engineering

Week 2 (2) 2007IS33 IS Failure Cases (cont) 1 COMP3470 IS33 People-Centred Information Systems Development Week 2 : Lecture 2 IS Failure Case Studies (cont.)

Embed Size (px)

Citation preview

Page 1: Week 2 (2) 2007IS33 IS Failure Cases (cont) 1 COMP3470 IS33 People-Centred Information Systems Development Week 2 : Lecture 2 IS Failure Case Studies (cont.)

Week 2 (2) 2007 IS33 IS Failure Cases (cont) 1

COMP3470 IS33 People-Centred Information Systems DevelopmentWeek 2 : Lecture 2

IS Failure Case Studies (cont.)

School of ComputingFACULTY OF Engineering

Page 2: Week 2 (2) 2007IS33 IS Failure Cases (cont) 1 COMP3470 IS33 People-Centred Information Systems Development Week 2 : Lecture 2 IS Failure Case Studies (cont.)

IS33 IS Failure Cases (cont) 2Week 2 (2) 2007

Homework To be completed before lecture on Wednesday 6th

October: Get this paper from Library’s collection of electronic

journals – Dennis A R, Carte T A and Kelly G G, “Breaking the rules: success and failure in groupware-supported business process reengineering”, in Decision Support Systems, Volume 36, Issue 1 (Sept 2003), pp.31-47, Elsevier Science Publishers B.V.

Write down on a piece of paper a list of ‘people issues’ raised in this article, and bring it to the lecture on 5th October (please ensure it’s legible as you will need to hand it in).

Page 3: Week 2 (2) 2007IS33 IS Failure Cases (cont) 1 COMP3470 IS33 People-Centred Information Systems Development Week 2 : Lecture 2 IS Failure Case Studies (cont.)

IS33 IS Failure Cases (cont) 3Week 2 (2) 2007

General points on this paper The overall structure

intro; lit. rev. to establish previous/related work; project approach; discuss each of the 4 case studies using a consistent

‘framework’; draw lessons from all 4 case studies (note the use of tables

to summarise analysis) and use a similar ‘framework’ as the one used in lit. rev. for discussion

conclusion

The ‘Method’ used The process of conducting ‘Analysis’

Page 4: Week 2 (2) 2007IS33 IS Failure Cases (cont) 1 COMP3470 IS33 People-Centred Information Systems Development Week 2 : Lecture 2 IS Failure Case Studies (cont.)

IS33 IS Failure Cases (cont) 4Week 2 (2) 2007

4 BPR case studies Your analysis (homework)? Mine :

very little attention paid to individuals /ordinary folks at the coal face (perhaps the downfall of BPR?)

the importance of having the right involvement (not tokenism)

having the right culture; having the right structure to support change (not just relying on one individual)

the importance of ‘buy-in’ and sharing the vision (whichever direction top-down; or middle-up)

But how did I arrive at these?