The changing paradigms of project management (Pollack, 2007)

Juli 15th, 2008

Changing Paradigm

Pollack, Julien: The changing paradigms of project management; in: International Journal of Project Management, Vol. 25 (2007), No. 3., pp. 266-247.
http://dx.doi.org/10.1016/j.ijproman.2006.08.002

This article is closely related to the 2006 article by Atkinson et al., which are all based on the hard-soft-framework first published in

Crawford, Lynn; Pollack, Julien: Hard and soft projects – a framework for analysis, in: International Journal of Project Management, Vol. 22 (2004), No. 8, pp. 645-653.

In this article Pollack analyses project management literature in order to identify paradigms associated with project management research. He uses the concept of the paradigm as defined by Kuhn in 1962 as a „commonly shared set of assumptions, values and concepts within a community, which constitutes a way of viewing reality. Individuals within the community may embody these assumptions in different ways, and so paradigm is used in his context to refer to a general tendency for thought“ (Pollack 2007, p. 266).

Pollack then describes the hard and soft paradigm he helped establishing with research on best practice organisational change projects. The hard paradigm is characterised by

  • Predefined project goals
  • Positivist and Realist philosophies
  • Emphasis on control
  • Quantitative measures
  • Reductionist techniques
  • Emphasis on structure
  • No need for participation
  • Project Manager as Expert

Whereas the soft paradigm is characterised by

  • Ill-defined and ambiguous goals
  • Qualitative measures
  • Emphasis on learning
  • Need for participation
  • Interpretivist philosophies
  • Emphasis on social processes
  • Project Manager as Facilitator

Furthermore Pollack argues that most of the current research is deeply rooted in the hard paradigm, although the literature on the soft paradigm is growing significantly. He then argues that a paradigmatic expansion could provide increased opportunity for practitioners and researchers. Since choosing a paradigm automatically defines certain assumptions for the research and thus limiting it. Nevertheless he points out that neither one perspective is appropriate to all situations.

How to fail in project management – without really trying (Pinto & Kharbanda, 1996)

Juli 15th, 2008

 How to ensure failure

Pinto, Jeffrey K.; Kharbanda, Om P.: How to fail in project management – without really trying; in: Business Horizons, Vol. 39 (1996), No. 4, pp. 45-53.
http://dx.doi.org/10.1016/S0007-6813(96)90051-8

Since Pinto popularised the critical success factor and failure factor research, which established a large body of research I wanted to include this paper though it is a bit dated. Pinot & Kharbanda basically illustrate how one can ensure complete and utterly failure as an owner of an IT project:

  • Ignore the environment (espy. stakeholders)
  • Push a new technology in a market too quickly
  • Don’t bother building fall back options
  • When problems occur shoot the most visible one
  • Let new ideas starve to death by inertia
  • Don’t bother conducting feasibility studies
  • Never admit project is a failure
  • Over manage project managers and their team
  • Never ever conduct post-failure reviews
  • Never bother to understand project trade-offs
  • Allow political expediency and infighting dictate crucial project decisions
  • Make sure project is run by a weak leader

Defining uncertainty in projects – a new perspective (Perminova, 2008)

Juli 15th, 2008

 Uncertainty

Perminova, Olga; Gustafsson, Magnus; Wikström, Kim: Defining uncertainty in projects – a new perspective; in: International Journal of Project Management, Vol. 26 (2008), No. 1, pp. 73-79.
http://dx.doi.org/10.1016/j.ijproman.2007.08.005

Perminova et al. argue that traditional project risk management focuses on risk and that the notion of uncertainties is generealy overlooked. In their literature review the authors show the difference between risk and uncertainties in 6 selected areas of research – Economics, Psychology, Philosophy, Organisational Theory, Dictionary, Project Management. Finally they establish a working definition for project managers: „[uncertainty occurs] when existing factors/assumptions are questioned and therefore the basis for calculating risks is questionable“. Perminova et al. argue that essential for managing uncertainty are reflective learning and sense-making, since they enable  flexibility and rapidness in decision-making especially since they do not restrict the choice of alternative actions in response to the situation.

The importance of context in programme management: An empirical review of programme practices (Pellegrinelli et al., 2007)

Juli 15th, 2008

 Context in Programs

Pellegrinelli, Sergio; Partington, David; Hemingway, Chris; Mohdzainb, Zaher; Shah, Mahmood: The importance of context in programme management – An empirical review of programme practices; in: International Journal of Project Management, Vol. 25 (2007), No. 1, pp. 41-55.
http://dx.doi.org/10.1016/j.ijproman.2006.06.002

Pellegrinelli et al. study actual practices on programs which mainly consist of projects. Surprisingly they find that the OGC’s Managing Successful Programmes framework (MSP) is not consistently adopted even when its use is mandated by the organisation. Furthermore they found that following MSP rigorously leads to a controlling dominated management agenda and not a empowering agenda. Their main findings for each MSP category are

  • Organisation & Leadership – mostly living on paper only, IT rather than business counterparts perform the roles needed
  • Benefits Management – mostly unquantifiable benefits or intangible benefits, general perception that this approach doesn’t fit RUP  (or any of the other unified processes of software development)
  • Stakeholder Management & Communication – n/a
  • Risk Management & Issue resolution – mostly risk management is missing completely on a program level
  • Program Planning & Control – often overruled by central head quarter
  • Business Case Management – Only symbolic artifact or only used to secure funding and never updated afterwards
  • Quality Management – are more adoptions of organisational practices already in place than the MSP processes

In short Pellegrinelli et al. revealed significant and on-going crafting of programme content, structures and processes to reconcile divergent aims and interests, to expedite progress in the face of adversity and to engage multiple sponsors, contributors and stakeholders. Thus the authors showed the importance and influence of context, namely the dynamic cultural, political and business environment in which the programmes operate, and the organisationally embedded nature of programme management.

Inquiring into the temporary organization: New directions for project management research (Packendorff, 1995)

Juli 15th, 2008

Inquiring temp orga

Packendorff, Johann: Inquiring into the temporary organization: New directions for project management research; in: Scandinavian Journal of Management, Vol. 11 (1995), No. 4, pp. 319-333.
http://dx.doi.org/10.1016/0956-5221(95)00018-Q

Firstly Packendorff gives a brief overview about the research on project management. He roots PM research in operations research with the development of the Gantt-Chart in 1910. The other big themes of research Packendorff identifies are

  • scheduling techniques (1950s and onwards)
  • Organisation Theory/HR Management/Leadership (1960s and onwards)
  • software tools/2nd generation Operations Research (1980s and onwards)
  • critical success factor research (1990s and onwards)
  • team building and matrix organisations (1995 [the year the article was written])

In this article Packendorff identifies three main shortcomings of project management research and theory. (1) Project Management is usually seen as a general theory and a theoretical field in its own right, (2) research on project management offers an abundance of normative advice despite being not sufficiently empirical, and (3) projects are seen as “tools” and not organisations.

Furthermore Packendorff recommends three changes in project management research to overcome these shortcomings. (1) Middle range theories for different kinds of projects should replace the general theory focus. (2) The aim of research should be to provide a descriptive theory (instead of the normative advice) which is grounded in empirical narrative studies on human interaction on projects = comparative case studies. (3) Projects should be seen as temporary organisations (instead of management tools) which are an aggregate of individuals temporarily enacting a common cause.

Matching the project manager’s leadership style to project type (Müller & Turner, 2007)

Juli 14th, 2008

Leadership Schools

Müller, Ralf; Turner, Rodney J.: Matching the project manager’s leadership style to project type; in: International Journal of Project Management, Vol. 25 (2007), No. 1, pp. 21-32.
http://dx.doi.org/10.1016/j.ijproman.2006.04.003

Müller & Turner shortly describe 6 modern and 3 historical schools of leadership before they investigate if leadership styles have an impact on the success of projects and whether there are different styles needed for different projects. The 9 schools they outline briefly are

  1. Confucius – it’s all about relationships, moderation, values, and process
  2. Aristotle – it’s all about relationships, values, and process
  3. Barnard – it’s all about relationship vs. processes
  4. Trait Theory – leaders are born not made
  5. Behavioural Theory – leadership skills can be developed
  6. Contingency Theory – effective leadership depends on the situation
  7. Visionary/charismatic leadership – transformation vs. transaction
  8. Emotional Intelligence – your (gut) feelings matter
  9. Competency – all matters (traits, behaviours, styles, emotions, processes, intellect…)

Furthermore the authors link each item of their 3 dimensional leadership model (Emotional, Managerial, Intellectual) to project performance in different project categories. Their results show that in general IT projects motivational skills and a strategic perspective positively influence the project’s success. In the case of high performing IT projects Self-Awareness, Communication and Self-Development impact the success positively, whereas visionary capacities have a negative impact on the success.

Determinants for external communications of IT project managers (Müller 2003)

Juli 14th, 2008

 Determinants of Communication

Müller, Ralf: Determinants for external communications of IT project managers; in: International Journal of Project Management, Vol. 21 (2003), No. 5, pp. 345-354.
http://dx.doi.org/10.1016/S0263-7863(02)00053-4

Müller analysis empirically the determinants of external communication of IT project managers in a business-to-business market. The study is based on the concepts of Media Richness Theory (which postulates that the richer the medium the more effective the communication) and Transaction Economics.

Müller finds no evidence for an influence of the organisation’s structure. The risk in the project has a negative impact on communication frequency and communication contents in general. Specifically he finds that higher risk increases communications frequency and preference for face-to-face meetings whilst decreasing the preference for written reports.
Relational norms have a positive influence on communication frequency, media, and contents.

The impact of principal–agent relationship and contract type on communication between project owner and manager (Müller & Turner, 2005)

Juli 14th, 2008

Communication and Contract type

Müller, Ralf; Turner, Rodney J.: The impact of principal–agent relationship and contract type on communication between project owner and manager; in: International Journal of Project Management, Vol. 23 (2005), No. 5, pp. 398-403.
http://dx.doi.org/10.1016/j.ijproman.2005.03.001

Müller & Turner argue that a project should be analysed in two distinctive stages pre and post contract. The pre contract perspective follows the laws outlined in Transaction Economics (or Transaction Cost Theory), which postulates that companies choose the governance structure with the lowest transactions costs. Specifically the degree of asset specificity, the degree of uncertainty, and the frequency of transactions determine the transaction costs both parties (vendor and buyer) consider in this phase.

The post-contract perspective is best conceptualised by the Principal-Agent-Theory, specifically by with the phenomena of moral hazard and adverse selection. Game theory usually calls this equilibria with correlated strategies and calls for contractual design in a way that each player is receiving incentives for compliance.

On a side-note: This behaviour is a classical chicken game. Imagine a vendor and a buyer who build up an integrated team. Both agree (orally) to send their most experienced experts (unfortunately they cost more), which would be best for the project work to be done. In this game each party can choose to give the work either to experts or to rookies:

  Rookies Experts
Rookies (0,0) (8,2)
Experts (2,8) (6,6)

Thus it is better for each team to sent rookies if the other team sends experts (which gives us the two Nash-equilibria of the game). If vendor and buyer send their rookies no one will know what is going on and what they have to do and both earn nothing (0,0). On the other hand the oral agreement of both parties to send their experts is not credible. Since this is a one-shot game the strategy (6,6) can only be reached if both parties agree on binding contracts or a negotiator.

Müller & Turner show that decisions made in the pre-contract phase with the objective to minimize the transaction costs (e.g. fixed-price or cost-plus contracts) can potentially have
have adverse effects on the project in the post-contract phase – by increasing the administrative costs for communication due to their negative impact on owner–manager
collaboration.

Leadership styles in information technology projects (Thite, 2000)

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)

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)

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)

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)

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)

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)

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)

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)

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)

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)

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)

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.