1 ersin gencturk - managing software development / project management for information systems...

22
1 Ersin Gencturk - MANAGING SOFTWARE DEVELOPMENT / Project Management for Information Systems Chapter 1 Chapter 1 Managing Change Managing Change Ersin Gencturk Ersin Gencturk Bogazici University – Software Bogazici University – Software Engineering Engineering

Upload: bonnie-gaines

Post on 17-Jan-2016

218 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: 1 Ersin Gencturk - MANAGING SOFTWARE DEVELOPMENT / Project Management for Information Systems Chapter 1 Managing Change Ersin Gencturk Bogazici University

1

Ersin Gencturk - MANAGING SOFTWARE DEVELOPMENT / Project Management for Information Systems

Chapter 1Chapter 1

Managing ChangeManaging Change

Ersin GencturkErsin GencturkBogazici University – Software EngineeringBogazici University – Software Engineering

Page 2: 1 Ersin Gencturk - MANAGING SOFTWARE DEVELOPMENT / Project Management for Information Systems Chapter 1 Managing Change Ersin Gencturk Bogazici University

2

Ersin Gencturk - MANAGING SOFTWARE DEVELOPMENT / Project Management for Information Systems

What is managing change What is managing change about ?about ?

• It is all about dealing with the people It is all about dealing with the people issues , and about involving people at issues , and about involving people at every stage in the project to help ensure it every stage in the project to help ensure it realises the full business benefits.realises the full business benefits.

• Many problems are caused by users not Many problems are caused by users not having been adequately prepared for the having been adequately prepared for the change.To avoid : plan a change change.To avoid : plan a change programmeprogramme

Page 3: 1 Ersin Gencturk - MANAGING SOFTWARE DEVELOPMENT / Project Management for Information Systems Chapter 1 Managing Change Ersin Gencturk Bogazici University

3

Ersin Gencturk - MANAGING SOFTWARE DEVELOPMENT / Project Management for Information Systems

Key considerations for a Key considerations for a change programmechange programme

• Plan in the same way as you plan the Plan in the same way as you plan the development and implementation of the development and implementation of the system itself.system itself.

• Ensure that it not only includes Ensure that it not only includes communication and training.Timing and communication and training.Timing and methods should make transition easy for methods should make transition easy for users.users.

• Avoid too many changes at a time sliceAvoid too many changes at a time slice• Involve users in planning and Involve users in planning and

implemantation the change programme.implemantation the change programme.

Page 4: 1 Ersin Gencturk - MANAGING SOFTWARE DEVELOPMENT / Project Management for Information Systems Chapter 1 Managing Change Ersin Gencturk Bogazici University

4

Ersin Gencturk - MANAGING SOFTWARE DEVELOPMENT / Project Management for Information Systems

Reasons for business Reasons for business changechangeWhy the company Why the company

spents money and spents money and time for the IT time for the IT projects?projects?

• Business survivalBusiness survival

• Improved efficiencyImproved efficiency

• Competitive Competitive advantageadvantage

• External factorsExternal factors

Page 5: 1 Ersin Gencturk - MANAGING SOFTWARE DEVELOPMENT / Project Management for Information Systems Chapter 1 Managing Change Ersin Gencturk Bogazici University

5

Ersin Gencturk - MANAGING SOFTWARE DEVELOPMENT / Project Management for Information Systems

Business survivalBusiness survival

• Production automation systems and Production automation systems and workflow systems often feet in this workflow systems often feet in this categorycategory

• Time is often key success factor,to Time is often key success factor,to hit deadlines you may need to hit deadlines you may need to compromise on the spesificationcompromise on the spesification

Page 6: 1 Ersin Gencturk - MANAGING SOFTWARE DEVELOPMENT / Project Management for Information Systems Chapter 1 Managing Change Ersin Gencturk Bogazici University

6

Ersin Gencturk - MANAGING SOFTWARE DEVELOPMENT / Project Management for Information Systems

Improved efficiencyImproved efficiency

• Most cases it is the ability of Most cases it is the ability of management to make better decisions management to make better decisions based on the information provided by the based on the information provided by the systems that results in increased systems that results in increased efficiency.efficiency.

• You have to take people with you and to You have to take people with you and to be sure that they know what a better be sure that they know what a better decision is.decision is.

• MISs and office systems are the MISs and office systems are the examples.examples.

Page 7: 1 Ersin Gencturk - MANAGING SOFTWARE DEVELOPMENT / Project Management for Information Systems Chapter 1 Managing Change Ersin Gencturk Bogazici University

7

Ersin Gencturk - MANAGING SOFTWARE DEVELOPMENT / Project Management for Information Systems

Competitive advantageCompetitive advantage

• Keypoint is encourage innovation and Keypoint is encourage innovation and new ideas throughout the project new ideas throughout the project lifecycle.lifecycle.

• If the way forward were clear at the start If the way forward were clear at the start of the project then the competition would of the project then the competition would have throught of it too and so there have throught of it too and so there would not be much advantege in would not be much advantege in progressing it.progressing it.

• Rapid prototyping and end-user solitions Rapid prototyping and end-user solitions are tacticts that often used.are tacticts that often used.

Page 8: 1 Ersin Gencturk - MANAGING SOFTWARE DEVELOPMENT / Project Management for Information Systems Chapter 1 Managing Change Ersin Gencturk Bogazici University

8

Ersin Gencturk - MANAGING SOFTWARE DEVELOPMENT / Project Management for Information Systems

External factorsExternal factors

• You need to be carefull about You need to be carefull about stakeholders who have to be stakeholders who have to be satisfied by what you are doing.satisfied by what you are doing.

• You need to avoid unhappy surprises You need to avoid unhappy surprises at the implemantation stage but be at the implemantation stage but be ready for the rules that can change.ready for the rules that can change.

• Involvement is a key process.Involvement is a key process.

Page 9: 1 Ersin Gencturk - MANAGING SOFTWARE DEVELOPMENT / Project Management for Information Systems Chapter 1 Managing Change Ersin Gencturk Bogazici University

9

Ersin Gencturk - MANAGING SOFTWARE DEVELOPMENT / Project Management for Information Systems

How big is the change ?How big is the change ?

• Radical Radical short term (3-9 short term (3-9 months):months):restructuring and redeployment of staffrestructuring and redeployment of staff

long term (1 year +) :long term (1 year +) :Business process re-engineering.Business process re-engineering.

• IncrementalIncrementalshort term (3-9 short term (3-9 months):months):Process automation and refinementProcess automation and refinement

long term (1 year +) :long term (1 year +) :TQM , innovation schemes.TQM , innovation schemes.

Page 10: 1 Ersin Gencturk - MANAGING SOFTWARE DEVELOPMENT / Project Management for Information Systems Chapter 1 Managing Change Ersin Gencturk Bogazici University

10

Ersin Gencturk - MANAGING SOFTWARE DEVELOPMENT / Project Management for Information Systems

Resistance to changeResistance to change

• Managers are usually O type.Managers are usually O type.

• Users are usually D type.Users are usually D type.

The Chinese Ideogram

Page 11: 1 Ersin Gencturk - MANAGING SOFTWARE DEVELOPMENT / Project Management for Information Systems Chapter 1 Managing Change Ersin Gencturk Bogazici University

11

Ersin Gencturk - MANAGING SOFTWARE DEVELOPMENT / Project Management for Information Systems

The phases of changeThe phases of change

Figure 1.2 The phases of change

Page 12: 1 Ersin Gencturk - MANAGING SOFTWARE DEVELOPMENT / Project Management for Information Systems Chapter 1 Managing Change Ersin Gencturk Bogazici University

12

Ersin Gencturk - MANAGING SOFTWARE DEVELOPMENT / Project Management for Information Systems

Organisational culturesOrganisational cultures

• Power-based culture:Power-based culture:• Centralised and informalCentralised and informal• Get and demonstrate sponsorshipGet and demonstrate sponsorship

• Bureaucratic culture:Bureaucratic culture:• Centralised and formalCentralised and formal• Play by the rules and use your networkPlay by the rules and use your network

• Task-based culture:Task-based culture:• Devolved and formalDevolved and formal• Regular use of project teams and task forcesRegular use of project teams and task forces

• Individualistic culture:Individualistic culture:• Devolved and informalDevolved and informal• Everyone has an opinion – consensus neededEveryone has an opinion – consensus needed

sponsorship :sponsorship : A person or group within an organization that funds, A person or group within an organization that funds, provides rationale, and takes responsibility for a project (provides rationale, and takes responsibility for a project (http://www.ds.uillinois.edu/glossary.asphttp://www.ds.uillinois.edu/glossary.asp))

Page 13: 1 Ersin Gencturk - MANAGING SOFTWARE DEVELOPMENT / Project Management for Information Systems Chapter 1 Managing Change Ersin Gencturk Bogazici University

13

Ersin Gencturk - MANAGING SOFTWARE DEVELOPMENT / Project Management for Information Systems

Sociability/solidarity matrixSociability/solidarity matrix

Figure 1.4 Sociability/solidarity matrixSource: Based on Rob Goffee and Gareth Jones, The Character of a Corporation, 2nd edition, Profile Books, 2003

Page 14: 1 Ersin Gencturk - MANAGING SOFTWARE DEVELOPMENT / Project Management for Information Systems Chapter 1 Managing Change Ersin Gencturk Bogazici University

14

Ersin Gencturk - MANAGING SOFTWARE DEVELOPMENT / Project Management for Information Systems

Networked CulturesNetworked Cultures

Advantages :Advantages :• People know each other at work and People know each other at work and

outside workoutside work• There is openness , trust and toleranceThere is openness , trust and toleranceDisadvantages :Disadvantages :• Can be over-tolerant of poor Can be over-tolerant of poor

performance.performance.• Too much focus on process rather than Too much focus on process rather than

the result.the result.

Page 15: 1 Ersin Gencturk - MANAGING SOFTWARE DEVELOPMENT / Project Management for Information Systems Chapter 1 Managing Change Ersin Gencturk Bogazici University

15

Ersin Gencturk - MANAGING SOFTWARE DEVELOPMENT / Project Management for Information Systems

Mercenary CulturesMercenary Cultures

Advantages :Advantages :• Strong agreement about targets and goalsStrong agreement about targets and goals• Work is very important and there is great Work is very important and there is great

task focustask focus• Socialising has a purpose : to talk about Socialising has a purpose : to talk about

work ;-)work ;-)Disadvantages :Disadvantages :• It is a ruthless place to work !!It is a ruthless place to work !!• No peace or sympathyNo peace or sympathy• People who do not deliver are a “waste of People who do not deliver are a “waste of

space” space”

Page 16: 1 Ersin Gencturk - MANAGING SOFTWARE DEVELOPMENT / Project Management for Information Systems Chapter 1 Managing Change Ersin Gencturk Bogazici University

16

Ersin Gencturk - MANAGING SOFTWARE DEVELOPMENT / Project Management for Information Systems

Fragmented CulturesFragmented Cultures

Advantages :Advantages :• People work for themselves not for People work for themselves not for

organisation.organisation.• High performance is everything it is not who High performance is everything it is not who

you know , it is what you deliver that countsyou know , it is what you deliver that counts• Lots of freedomLots of freedomDisadvantages :Disadvantages :• Is the culture of individual (particulary friendly)Is the culture of individual (particulary friendly)• This culture usually found in legal practices , This culture usually found in legal practices ,

consultancies , radio and tv and academic consultancies , radio and tv and academic world !! world !!

Page 17: 1 Ersin Gencturk - MANAGING SOFTWARE DEVELOPMENT / Project Management for Information Systems Chapter 1 Managing Change Ersin Gencturk Bogazici University

17

Ersin Gencturk - MANAGING SOFTWARE DEVELOPMENT / Project Management for Information Systems

Communal CulturesCommunal Cultures

Advantages :Advantages :

• Have a high level of commitment to each Have a high level of commitment to each otherother

• Are focused on product or serviceAre focused on product or service

• Work in teams all the timeWork in teams all the time

• Support the leaderSupport the leader

Disadvantages :Disadvantages :

• Absorbs all the timeAbsorbs all the time

• If you want a life out of office do not prefer !! If you want a life out of office do not prefer !!

Page 18: 1 Ersin Gencturk - MANAGING SOFTWARE DEVELOPMENT / Project Management for Information Systems Chapter 1 Managing Change Ersin Gencturk Bogazici University

18

Ersin Gencturk - MANAGING SOFTWARE DEVELOPMENT / Project Management for Information SystemsChange Change competence/commitment competence/commitment matrixmatrix

able peoplebut unwilling or

insecure

able, willingand confident

unable andunwilling

keen andmotivated but

unable

Commitment

Co

mp

ete

nce

Low High

High

Figure 1.5 The change competence/commitment matrix

Page 19: 1 Ersin Gencturk - MANAGING SOFTWARE DEVELOPMENT / Project Management for Information Systems Chapter 1 Managing Change Ersin Gencturk Bogazici University

19

Ersin Gencturk - MANAGING SOFTWARE DEVELOPMENT / Project Management for Information Systems

Four-phase model for Four-phase model for business changebusiness change

Figure 1.6 Four-phase model of managing business change

Page 20: 1 Ersin Gencturk - MANAGING SOFTWARE DEVELOPMENT / Project Management for Information Systems Chapter 1 Managing Change Ersin Gencturk Bogazici University

20

Ersin Gencturk - MANAGING SOFTWARE DEVELOPMENT / Project Management for Information Systems

Figure 1.7 The risk of the traditional approach

Risks of a traditional Risks of a traditional approach approach to changeto change

Page 21: 1 Ersin Gencturk - MANAGING SOFTWARE DEVELOPMENT / Project Management for Information Systems Chapter 1 Managing Change Ersin Gencturk Bogazici University

21

Ersin Gencturk - MANAGING SOFTWARE DEVELOPMENT / Project Management for Information Systems

SummarySummary

• Treat everyone with equal respect,making Treat everyone with equal respect,making an effort to understand their motivations , an effort to understand their motivations , viewpoints and perspectivesviewpoints and perspectives

• Being right doesn’t count.You need to Being right doesn’t count.You need to make people with you to get their make people with you to get their commitment , their buy-incommitment , their buy-in

• Always maintain your focus on the Always maintain your focus on the business benefits of the changebusiness benefits of the change

• Take advice from , and use the help of Take advice from , and use the help of experts.You don’t have to do it all experts.You don’t have to do it all yourself! yourself!

Page 22: 1 Ersin Gencturk - MANAGING SOFTWARE DEVELOPMENT / Project Management for Information Systems Chapter 1 Managing Change Ersin Gencturk Bogazici University

22

Ersin Gencturk - MANAGING SOFTWARE DEVELOPMENT / Project Management for Information Systems

Thanks for listeningThanks for listening

• Any questions ?Any questions ?

• You can download a copy of this ppt You can download a copy of this ppt at at http://www.gencturk.org/ersin/swe/shttp://www.gencturk.org/ersin/swe/swe523.pptwe523.ppt