Lars Kristian Hansen

40
Portefølje, Program og Projektledelse Onsdag den 25. november 2015 Hvordan kan styrings- og koordineringsmæssige problemer i IT projekt porteføljestyring forstås og håndteres? Lars Kristian Hansen, Udviklingskonsulent, Københavns Kommune

Transcript of Lars Kristian Hansen

Page 1: Lars Kristian Hansen

Portefølje, Program og ProjektledelseOnsdag den 25. november 2015

Hvordan kan styrings- og koordineringsmæssige problemer i IT projekt porteføljestyring forstås og håndteres?Lars Kristian Hansen, Udviklingskonsulent, Københavns Kommune

Page 2: Lars Kristian Hansen

Lars K. Hansen

10 publications

Page 3: Lars Kristian Hansen

Introduction

“Background, goal

and structure”

Page 4: Lars Kristian Hansen

This presentation is based on:

• My PhD-dissertation and

• An academic article submitted to

European Journal of Information Systems

BACKGROUND

Page 5: Lars Kristian Hansen

• To define IT Project Portfolio

Management

• To provide more understanding

regarding IT Project Portfolio

management problems

• Reflect on: can the problems found in

my case study be found in any

organization?

GOAL

Page 6: Lars Kristian Hansen

STRUCTURE

Page 7: Lars Kristian Hansen

Definition

“Project Portfolio Management”

Page 8: Lars Kristian Hansen

IT PROJECT PORTFOLIO

A collection of components that are

grouped together to facilitate the

effective management of that work in

order to meet strategic business

objectives (PMI, 2008)

Page 9: Lars Kristian Hansen

DEFNITION

Portfolio

Programs

Projects Projects

Project Programs

Projects ProjectsOther

work

Do the right

projects

Do the

projects right

Tactical

level

Strategic level

Operational

level

Page 10: Lars Kristian Hansen

An theoretical and empirical

grounded approach helping us:

• To understand Work Design

problems in IT PPM

NEED IN IT PPM RESEARCH

Page 11: Lars Kristian Hansen

Theory

“Work Design Theory”

Page 12: Lars Kristian Hansen

WORK DESIGN THEORY

Page 13: Lars Kristian Hansen

WORK DESIGN THEORY

Level A

Level N Level N Level N

Level BControl across hierarchical

levels

Coordination across functions and units

Page 14: Lars Kristian Hansen

CONTROL PROBLEMS

Authority,

knowledge,

resources

Control mechanisms

Page 15: Lars Kristian Hansen

CONTROL MECHANISMS

•Formal control•Informal control

Page 16: Lars Kristian Hansen

WORK DESIGN THEORY

Level A

Level N Level N Level N

Level BControl across hierarchical

levels

Coordination across functions and units

Page 17: Lars Kristian Hansen

COORDINATION

Post-

selections

phase

Selections

phase

Pre-

selections

phase

Page 18: Lars Kristian Hansen

COORDINATION PROBLEMS

Post-

selections

phase

Selections

phase

Pre-

selections

phase

Modul 1 Modul 2 Modul 3

Information

important

across modules

Information not

important

across modules

Page 19: Lars Kristian Hansen

WORK DESIGN THEORY

Page 20: Lars Kristian Hansen

COMPLEX NETWORK

PROBLEMS

Control problemCoordination-

problemComplex networks

problem

Task with no control and clear definition

Page 21: Lars Kristian Hansen

PROBLEM SOLUTIONS

Control problemCoordination-

problemComplex networks

problem

Authority can solve problem

Modularization can solve problem

Network integratorscan solve problem

Page 22: Lars Kristian Hansen

Case and method

“Engaging in Newport”

Page 23: Lars Kristian Hansen

CASE

Page 24: Lars Kristian Hansen

METHOD

Mathiassen (2002);

Van de Ven (2007)

Page 25: Lars Kristian Hansen

Results

“ROOT PROBLEMS”

Page 26: Lars Kristian Hansen

CONTROL PROBLEMS

Authority Knowledge Resources

Caution

Political level

Director level

IT leader level

Project level

Page 27: Lars Kristian Hansen

CONTROL PROBLEMS

Political level

Director level

IT leader level

Project level

Use of informal mechanisms

Minor bureaucracy

Difficult to communicate across time and space Less explicit in performance and use of resources

Page 28: Lars Kristian Hansen

COORDINATION PROBLEMS

Post-

selections

phase

Selections

phase

Pre-

selections

phase

Modul 1 Modul 2 Modul 3

Information not

important

across modules

Information which

is important

across modules

Page 29: Lars Kristian Hansen

COMPLEX NETWORK PROBLEM

Newport’s silo structure hinder PPM

Page 30: Lars Kristian Hansen

Discussion

“Reflections and summing up”

Page 31: Lars Kristian Hansen

PROBLEM NETWORK

Political and

managerial silos

hinder IT PPM

Weak accountability

between

hierarchical levels

Subsumed

problems

Unclear distinction

between IT architect

and adopter

Subsumed

problems

Control Problems

Modularity Problems

Complex Network Problems

Page 32: Lars Kristian Hansen

CASE

Page 33: Lars Kristian Hansen

Relating to existing

tolls and research

“Reflections and summing up”

Page 34: Lars Kristian Hansen

CMMI MODELS

Page 35: Lars Kristian Hansen

PARETO DIAGRAM

Page 36: Lars Kristian Hansen

Summing up

“Thank you for your attention”

Page 37: Lars Kristian Hansen

QUESTIONS AND

COMMENTS

QUSTIONS

Page 38: Lars Kristian Hansen

• To define IT Project Portfolio

Management

• To provide more understanding

regarding IT Project Portfolio

management problems

• Reflect on: can the problems found in

my case study be found in any

organization?

GOAL

Page 39: Lars Kristian Hansen

SUMMING UP

Page 40: Lars Kristian Hansen

End

“Thank you for your attention”