Archive for Juli, 2008

Leadership styles in information technology projects (Thite, 2000)

Montag, Juli 14th, 2008

 Leadershipstyles

Thite, Mohan: Leadership styles in information technology projects; in: International Journal of Project Management, Vol. 18 (2000), No. 4, pp. 235-241.
http://dx.doi.org/10.1016/S0263-7863(99)00021-6

Mohan studied 36 projects in Australia and looked into successful IT project management leadership styles. His results indicate that a combination of transformational and technical leadership behaviours augment the effectiveness of transactional leadership leading to high project success. Unfortunately Mohan also found that there is no one leadership style that is effective in all project situations. Therefore he recommends an underlying yet flexible style characterised by organisational catalyst, intellectual stimulation, behavioural charisma, and contingent reward behaviours for enhanced leadership effectiveness.

Project management and business development: integrating strategy, structure, processes and projects (Van Der Merwe, 2002)

Montag, Juli 14th, 2008

Business development

Van Der Merwe, A. P.: Project management and business development: integrating strategy, structure, processes and projects; in: International Journal of Project Management, Vol. 20 (2002), No. 5, pp. 401-411.
http://dx.doi.org/10.1016/S0263-7863(01)00012-6

Van Der Merwe outlines organisational theories and configurations. Furthermore he applies systems and process theory to explain the relationship between strategy, structure, processes, and projects. The author shows that projects in business development are used to transform a vision into results by bringing together diverse teams. He concludes with this [delightful] paragraph:

„This aspect [projects bringing together diverse people] revealed project management as the point of departure for management theory, where management manages the behavioural processes of people who manage the continuous incremental improvement of business procedures in the organisation, through projects that guide the business process to address the change in the strategic direction of the organisation. If business is to develop then the successful outcome of any change in the organisation can only be achieved when business processes and human behavioural processes converge in the person of the project manager.“ (Van Der Merwe, 2002, p. 411)

[Amen.]

Success factors regarding the implementation of ICT investment projects (Milis & Mercken, 2002)

Montag, Juli 14th, 2008

ITC Implementation in Banks CSF

Milis, Koen; Mercken, Roger: Success factors regarding the implementation of ICT investment projects; in: International Journal of Production Economics, Vol. 80 (2002), No. 1, pp. 105-117.
http://dx.doi.org/10.1016/S0925-5273(02)00246-3

 

Milis & Mercken outline critical success factors for IT implementation projects in banks and insurances. They did a literature review and qualitative field research.The authors describe 49 critical success factors falling into the categories of

  • Project selection
  • Project definition
  • Project plan
  • Management involvement and support
  • Project team
  • Change management
  • Project resources
  • Managing relationships

Building on these findings, Milis & Mercken build a framework of 4 categories of success factors. (1) factors that enhance goal congruence, (2) factors that are related with the project team, (3) factors that influence the acceptance of the project, and (4) elements of implementation politics.

 

The first category combines factors that influence goal congruency:

  • Good selection & justification practice
  • Scope/objectives/goals: defined and agreed upon
  • Criteria for judging success: defined and agreed upon
  • Business alignment

The second category contains factors of team management/leadership:

  • Realistic but challenging goals
  • Urgency built in
  • Evaluation and reward mechanisms in place.Effective communication and conflict control
  • Complementary skills (technical & social)
  • Select team players to staff the project team
  • Select a competent and experienced project manager

The third category focuses on the acceptance of deliverables:

  • Definition of the authority and responsibilities
  • User participation.
  • Training
  • Top management support
  • Continuous evaluation and debate among the different parties involved
  • Powerful project manager with sufficient social skills

The fourth category deals with the implementation politics and planning:

  • Functional decomposition
  • Proper level of detail
  • Sufficient resources to execute the tasks planned
  • Resources for change management & contingency planning
  • Built in resource buffers

Beyond the Gantt chart: Project management moving on (Maylor, 2001)

Montag, Juli 14th, 2008

 beyond the gannt chart

Maylor, Harvey: Beyond the Gantt chart – Project management moving on; in: European Managment Journal, Vol. 19 (2001), No. 1, pp. 92-100.
http://dx.doi.org/10.1016/S0263-2373(00)00074-8

Maylor argues that project management practice and research [which he analyses by it’s standard texts and bodies of knowledge] are stuck in a large-scale engineering mind set. He uses the advances in operations to show that knowledge in the project management realm is lacking behind. Maylor covers several key areas and challenges typical project management assumptions:

  • Project definition – projects are not a one-off effort; project managers need to be viewed as integrators of theories and knowledge and not as managers of plans
  • Manufacturing vs. Service – project management has no answer on the intangibility of service projects, thus expectation management and customer orientation are under represented; a SERVQUAL like paradigm change is needed
  • Project Management – the predominant focus on management activities and planning systems dilutes the importance of execution
  • Planning Process – Planning is somehow synonymous with network diagrams, freezes and baselines; Maylor encourages to make planning more visible, adopting lean tools from operations such as whiteboards and post-its
  • Conformance vs. Performance – Project management currently focuses on the conformance with budget, scope, and cost baselines; as operations did with TQM project should focus on delivering as soon as possible and as cheap as possible the maximal customer delight
  • Role of Strategy – Maylor cites Deming’s famous „defects are caused by the system“, to outline how argues that projects should not only be reactions to a company’s strategy but they need to contribute to and form part of the organisation’s strategy

Managing public–private megaprojects: Paradoxes, complexity, and project design (van Marrewijk et al., in press)

Montag, Juli 14th, 2008

Megaproject Culture (1) Megaproject Culture (2)

van Marrewijk, Alfons; Clegg, Stewart R.; Pitsis, Tyrone S.; Veenswijk, Marcel: Managing public–private megaprojects: Paradoxes, complexity, and project design; in: International Journal of Project Management, in press.
http://dx.doi.org/10.1016/j.ijproman.2007.09.007

Marrewijk et al. compare the project designs, daily practices, project cultures and management approaches in two case studies. The authors explore how actors on these megaprojects make sense of uncertainty, ambiguity and risk. They show that project design and project cultures influence cooperations between key players on the project.

They argue that each project has a specific project culture with subcultures, conflicts, powers, and cultural ambiguity. Thus making the staff of a project a modern tribe distinguishing themselves from the rest of the working world (and the parent corporation) via artifacts, practices, and values. Projects show multiple cultures, power relations, conflicts, and abnormalities just like any larger society. Post-Positivism research has shown the impact of the project culture on project’s success or failure. Unfortunately the authors found that megaprojects have a higher tendency than normal to develop a dysfunctional project culture.

Moreover Marrewijk et al. analyse the cultural strategies of change and the cultural forms, practices, and content themes found in their two megaproject case studies. Finally they outline how culture and project design influence a public-private partnership project. They conclude that there are 2 critical success factors on how to design a project organisation which can create a non-dysfunctional project culture.

  1. Design power relations between all players in the project in a way that balances these
  2. Design accountability in way that is NOT a zero-sum game and which serves the self-interest of all involved parties and individuals

Project organization – Exploring its adaptation properties (Lindkvist, 2008)

Montag, Juli 14th, 2008

 Project based firm

Lindkvist, Lars: Project organization – Exploring its adaptation properties, in: International Journal of Project Management, Vol. 26 (2008), No. 1, pp. 13-20.
http://dx.doi.org/10.1016/j.ijproman.2007.08.011

Linkdkvist describes in this EURAM 2007 paper the cultural characteristics of the classical functional organisation and the characteristics of the project based firm. Furthermore he outlines 5 critical success factors for changing a functional organization into a project based organisation.

  • Individual learning: Trial-and-Error-Learning on the project level
  • Team learning: Critical inquiry and reflection
  • Firm-wide learning: Strategic learning inspired by individual and team learning
  • Time boundedness: Focus on time-related concepts (plans, milestones, reviews etc.)
  • Reciprocity: Project-level process must be nested in firm-level processes

A set of frameworks to aid the project manager in conceptualizing and implementing knowledge management initiatives (Liebowitz & Megbolugbe, 2003)

Montag, Juli 14th, 2008

KM

Liebowitz, Jay; Megbolugbe, Isaac: A set of frameworks to aid the project manager in conceptualizing and implementing knowledge management initiatives; in: International Journal of Project Management, Vol. 21 (2003), No. 3, pp. 189-198.
http://dx.doi.org/10.1016/S0263-7863(02)00093-5

Liebowitz & Megbolugbe describe three frameworks which can be used by practitioners to think about Knowledge Management (KM) approaches. Firstly the outline Wiig’s framework which describes the knowledge activities cycle (Conceptualise –> Reflect –> Act –> Review –> Conceptualise…) and the connected workplace structure (Business processes, [used in] Knowlege items, [bound to] organisational roles).

Secondly they present the Knowledge Management Pyramid and thirdly they derive a new implementation framework. Liebowitz & Megbolugbe’s framework connects the KM Intentions and Needs with the KM Solution via 4 knowledge objects/critical factors. (1) Knowledge taxonomies, (2) organizational culture, (3) user feedback on usability and functionalities, and (4) alignment with business strategy and senior management committment.

Frames and inscriptions: tracing a way to understand IT-dependent change projects (Linderoth & Pellegrino, 2005)

Montag, Juli 14th, 2008

constructivism

Linderoth, Henrik C.; Pellegrino, Giuseppina: Frames and inscriptions – tracing a way to understand IT-dependent change projects; in: International Journal of Project Management, Vol. 23 (2005), No. 5, pp. 415-420.
http://dx.doi.org/10.1016/j.ijproman.2005.01.005

Linderoth & Pellegrino analyse sense-making in organizational transitions which are driven by IT projects. Sense-making of a new technology, they argue, happens on an individual level at the user and can not be dictated by some higher authority. The authors use two approaches to analyse how individuals make sense of new technology and how the sense shifts over time. The Actor-Network-Theory and Theory of Social Construction of Technology.

Actor-network theory (ANT) explains processes by which ideas are accepted, tools and methods adopted. There are two major methodologies on how to explore these network processes. One is following the actor (mostly by interviews, observation) and the other one is to analyse inscriptions. Inscriptions are artefacts of knowledge created by the actors. Linderoth & Pellegrino follow this second approach and they define the inscription as „desired program of action or pattern of use that someone inscribes into a medium as artefact.“ They find, that for IT most users are inflexible in how to use the technology, but users are highly flexible when and in which situation to use the technology.

Social Construction of Technology explains the counter party in this process – the user. Linderoth & Pellegrino define Technological frames as „outcome of organisation’s member interaction and sense-making of technology“. Furthermore they introduce the notion of dynamic shifts of these frames over time. [Thus adopting a more post-structuralist view on Social Constructivism].
Furthermore they use Social Construction of Technology to outline the 3 key points users engage in sense-making about; (1) the nature of the technology, (2) the strategy of the technology, and (3) the use of the technology. All three frames need a reasonable inter-connection. Furthermore Linderoth & Pellegrino argue that discrepancies between frames of different user groups lead to project failures.

Looking at the dynamics of frames the authors identified one dominating element in each project life stage.

  • Project start-up: Nature, Strategy, Use
  • Project in action: Nature, Strategy, Use
  • Project re-birth: Nature, Strategy, Use

Moreover Linderoth & Pellegrino show that a following the importance of context in building frames. [Thus following the ideas of the learning theory of Constructivism] They show that the sense-making processes to create the frames shift from a global discourse to a local discourse; and thus from a global context to a local context.

Change program initiation: Defining and managing the program–organization boundary (Lehtonen & Martinsuo, 2008)

Freitag, Juli 11th, 2008

Program initiation boundaries

Lehtonen, Päivi; Martinsuo, Miia: Change program initiation – Defining and managing the program–organization boundary; in: International Journal of Project Managment, Vol. 26 (2008), pp. 21-29.

Lehtonen & Martinsuo analyse change programs from a social perspective. Therefore programs are characterised as complex temporary organisations in an uncertain, dynamic context. The authors study the boundaries of change programs and identify boundary spanning activities and actors. Their research results show the need of each program to run through several iterative cycles of integration with and isolation from the parent organization during the project initiation phase. Actors (i.e. people) on the project define and shape the boundary, while also representing and legitimising the program. In further interactions with the parent company these actors scout for information, negotiate, ensure continuity, and guard & isolate themselves. Such interaction happens on an inidivdual level rather than on a team level. The organisation’s middle managers and the project’s central managers are the key interaction partners.

A Roadmap for IT Project Implementation – Integrating Stakeholders and Change Management Issues (Legris & Collerette, 2006)

Freitag, Juli 11th, 2008

History of PM Theories

Legris, Paul; Collerette, Pierre: A Roadmap for IT Project Implementation – Integrating Stakeholders and Change Management Issues; in: Project Management Journal, Vol. 27 (2006), No. 5, pp. 64-75.

Legris & Collerette start with an overview of theories on IT implementations. Locating the roots of these discussion in technology adoption models rather than in project management. Furthermore they break down the typical IT implementation project in 5 phases – preliminary analysis, systems requirement, preparation, implementation, and consolidation. They outline key factors for each phase and offer scales on how to score each of these factors to assess the condition of the project.

Perspectives on Project Management (Kolltveit et al. 2007)

Freitag, Juli 11th, 2008

Perspectives on PM

Kolltveit, Bjørn Johs.; Karlsen, Jan Terje; Grønhaug, Kjell: Perspectives on Project Management; in: International Journal of Project Management, Vol. 25 (2007), No. 1, pp. 3-9.
http://dx.doi.org/10.1016/j.ijproman.2005.12.002

Kolltveit et al. analyse the perspective of research articles and books published between 1983-2004 in the International Journal of Project Management. In total they mark 2977 observations of one of their 6 identified perspectives (task, leadership, business, transaction, systems, stakeholder). They characterize the average book on project management to contain 21% of knowledge on tasks, 51% on leadership, 10% on business, 8% on transactions, 5% on stakeholders, and 5% on systems.

Furthermore Kolltveit et al. describe theories of each perspective and key issues/research topics for each perspective. Plus they show the distribution over time, which shows a slightly decreasing trend for the task and systems perspective, whereas business and leadership perspectives are growing.

The ethical dimension of project management (Helgadóttir, in press)

Freitag, Juli 11th, 2008

Ethics

Helgadóttir, Hildur: The ethical dimension of project management, in: International Journal of Project Management, Article in Press
http://dx.doi.org/10.1016/j.ijproman.2007.11.002

Helgadóttir argues that project management needs perfection (=logical thinking), beauty (=creative thinking) and goodness (=ethical thinking). Then the author describes different ethical philosophies and how these philosophies manifest in teams and management decisions. First Helgadóttir describes the outcome oriented philosophies of virtue ethics, and utilitarianism. Secondly she details the process oriented philosophies of deontological ethics, natural rights theory, and social contract theory.

Development of the SMART(TM) Project Planning framework (Hartman 2004)

Freitag, Juli 11th, 2008

Smart Project

Hartman, Francis; Ashrafi, Rafi: Development of the SMARTTM Project Planning framework, in: International Journal of Project Management, Vol. 22 (2004), pp. 499-510.

Hartman & Ashrafi present a new trademarked framework for Project Planning. The idea behind this framework is to ensure that the project is SMART. Strategically Managed, Aligned with corporate strategy as well as stakeholder needs, Regenerative [sustainable] for the project team, and Transitional, which stands for smooth execution of changes to the project.

What is new? Four tools are presented by the authors (1) the SMART Breakdown Structure (SBS), (2) the priority triangle, (3) key questions, and (4) RACI+.

The SBS is basically a new take on the work break down structure. On the top-level is the project mission which is then broken down into the key stakeholders‘ expectations on the first level of decomposition. The next levels of decompositions break the expectations down to tangible deliverables. Furthermore they add a parking lot and an explicit list of exclusions.
The priority triangle extends the ABC-priority to 6 permutation of pairs of 2 priorities, e.g., Time (1st) and Cost (2nd); or Quality (1st) and Time (2nd).
The 3 key questions are (1) What is the final deliverable?, (2) What is everyone this project praising for?, and (3) Who decides the first two questions?
Finally the RACI+ chart (derived from the classical RACI „Responsibility, Accountability, Consult, Inform“-Matrix) clarifies the roles of each letter, R=responsible, A=action (does the work), C=consults (=has input, needs to be asked), I=informs (=reviews the output) and adds a new letter S=sanction (=signs-off acceptance).

Applying Traits Theory of Leadership to Project Management (Gehring, 2007)

Freitag, Juli 11th, 2008

 Traits Theory + PM

Gehring, Dean R.: Applying Traits Theory of Leadership to Project Management; in: IEEE Engineering Management Review, Vol. 35 (2007), No. 3, pp. 109ff.
And also in: Project Managment Journal, Vol. 38 (2007), No. 1, pp. 44-54. 

I, personally, have mixed attitudes towards the whole Personality Traits Theory. While I still think there is some ground for the NEO-PI constructs and scale, I really do believe the whole Meyers-Briggs-Type-Indicator (MBTI) is total crap, especially using a magical sorting hat which uses binominal (E or I, S or N, T or F, J or P) values on dimensions, when the scale seems to be normally distributed. Furthermore there seems to be proof that the whole thing is situational. I am an eNFP by the way.

However Gehring outlines the typically looked for leadership competencies of project managers in a very nice structured way (see my graphical summary). The author further describes the personality traits usually found with specific MBTI types. He then matches competencies to MBTI types.
ENTJ, ENFJ, INTJ, ISTJ, and INFJ art the top 5 matches between competencies and personality types. Unfortunately the sample is rather small (53 respondents) and the article lacks any statistical information about the validity and quality of the results.

Framing of project critical success factors by a systems model (Fortune & White 2006)

Mittwoch, Juli 9th, 2008

IT CSF Research and systems framing

Fortune, Joyce; White, Diana: Framing of project critical success factors by a systems model, in: International Journal of Project Management, Vol. 24 (2006), No. 1, pp. 53-65.
http://dx.doi.org/10.1016/j.ijproman.2005.07.004

How much overfitting does a model need? Fortune & White reviewed 63 studies on critical success factors of IT projects. And they identified 27 of them, the picture shows the success factors and in brackets how many publications were finding proof for it.
The Top-5 are: (1) Senior management support, (2) Clear and realistic objectives, (3) Strong/detailed project plan kept updated, (4) Good communication/feedback, and (5) user/client involvement.
Furthermore Fortune & White identify the 9 sub-systems typically found on an IT project and they sort the success factors accordingly. Nevertheless, DeMarco’s question (posted earlier in this blog) pops back into my mind: If only one thing succeeds – what should it be?

A comprehensive framework for the assessment of eGovernment projects (Esteves & Joseph, 2008)

Mittwoch, Juli 9th, 2008

eGov Assessment

Esteves, José; Joseph, Rhoda C.: A comprehensive framework for the assessment of eGovernment projects; in: Government Information Quarterly, Vol. 25 (2008), No. 1, pp. 118-132.
http://dx.doi.org/10.1016/j.giq.2007.04.009

I clearly expected more noteworthy things to write down in my summary sketch. Esteves & Rhoda built a framework on 3 dimensions. (1) Assessment Dimensions for the project, (2) Stakeholders, and (3) eGovernment Maturity Level. For the first dimension, the assessment of the project itself, they describe 6 more dimensions to look into. These are the technology implemented, the strategy behind it, organisational fit, economic viability, operational efficiency and effectiveness, and the services offered.

No Project is an Island (Engwall, 2003)

Mittwoch, Juli 9th, 2008

No Project is an Island

Engwall, Mats: No project is an island – linking projects to history and context; in: Research Policy, Vol. 32 (2003), No. 5, pp. 789-808.
http://dx.doi.org/10.1016/S0048-7333(02)00088-4

I read this article for it’s research implications. Engwall starts with the argument that a project’s success is not independent of the project’s context and the organisations history of previous projects. There is one great point in his argument: Projects become increasingly difficult if they are innovative. BUT innovativeness of a project does not depend whether the project manager has done something similar before, it depends on how new the sponsor thinks his project is.

Engwall’s implications are clear: extend the scope of research time wise and department wise. Furthermore he makes his stand for an open systems approach in researching projects.

Are we any closer to the end? Escalation and the case of Taurus (Drummond, 1999)

Dienstag, Juli 8th, 2008

Taurus

Drummond, Helga: Are we any closer to the end? Escalation and the case of Taurus; in: International Journal of Project Management, Vol. 17 (1999), No. 1, pp. 11-16.
http://dx.doi.org/10.1016/S0263-7863(97)00074-4

The Taurus Project is a great case study. First of all it is a failed IT project. It took the project some 500 million GBP and 5 years to fail. And secondly it was a visionary project overhauling the IT of the London financial market. Drummond examines the route to failure. In this article she applies Escalation Theory aka Escalation of Commitment or the Vietnam War Syndrome as it was labelled in Freakonomics.

What did Drummond see? A destructive progression, i.e., one sub-optimal decision leading to another sub-optimal decision, that leading to another sub-optimal decision and so on. This effect was reinforced by an effect first found by Kahnemann & Tversky. They showed that gradual deterioration in a condition is usually underestimated and goes unnoticed. [Therefore addicts need an intervention]

What are the lessons learned?
Avoid the Garbage Can Effect. Don’t let the solution dictate the problem. Especialy if you have a keen vendor.
Make progress tangible. On Taurus experienced managers where struggling with controlling and managing the project because progress in IT systems‘ development can not be touched.
Engage in Second-Order Thinking. First-order thinking is solving the problem with the usual problem solving patterns, aka ‚more of the same‘. This does not help in deteriorating conditions. To break that vicious cycle second-order thinking is needed, which basically examines the assumptions of given decisions, plans, requirements, solutions.
And lastly balance power and responsibility. Politics and outside over steering destroyed the power and responsibility balance in this case. Project Managers had huge responsibilities but no decision power whatsoever to really solve the problem. Even if they saw recognised the problem and asked for project cancellation earlier than it was acknowledged by the project board.

Rethinking Project Management: Researching the actuality of projects (Cicmil et al. 2006)

Dienstag, Juli 8th, 2008

Rethinking PM

Svetlana Cicmil, Svetlana; Williams, Terry; Thomas, Janice; Hodgson, Damian: Rethinking Project Management – Researching the actuality of projects; in: International Journal of Project Management, Vol. 24 (2006), No. 8, pp. 675-686
http://dx.doi.org/10.1016/j.ijproman.2006.08.006

Cicmil et al. describe their idea for the future direction of project management research. The authors outline 3 ideas they had in mind when thinking about project management. (1) projects are complex social settings loaded with conflicts, (2) project management practice is a social conduct, (3) Heidegger’s Da-Sein.  With this starting point Cicmil et al. describe their methodological considerations which are rooted in pragmatic epistemology. They argue that in this tradition non-quantitative research can build epistemic theories.

Moreover Cicmil et al. outline quality criteria/standards for Actuality Research. It needs to fulfil practical reasoning, sense-making and thus it can explain hard to quantify concepts of emotions, power, tensions, negotiations, and political agendas. Finally they highlight topics for future research which are suited to be explored using an Actuality Research approach.

Balancing strategy and tactics in project implementation (Pinto & Slevin 1987)

Dienstag, Juli 8th, 2008

Balancing Strategy and Tactics

Pinto, J.K.; Slevin, D.P.: Balancing strategy and tactics in project implementation; in: Sloan Management Review, (1987), pp. 33–41.

This article is a very classic. It is one of the most cited articles on success factors in research papers on IT projects. Pinto & Slevin outline 10 critical success factors (most of them seem common sense today), which are make-or-break factors on any given project

  1. Communication
  2. Project Mission
  3. Top Management Support
  4. Project Schedule
  5. Client Consultations
  6. Personnel Recruitment, Training, and Selection
  7. Technical Tasks
  8. Client Acceptance
  9. Monitoring & Feedback
  10. Trouble Shooting