Archive for the ‘Organisational capabilities’ Category

Integrating the change program with the parent organization (Lehtonen & Martinsuo, 2009)

Dienstag, April 28th, 2009

DSC02128

Lehtonen, Päivi; Martinsuo, Miia: Integrating the change program with the parent organization; in: International Journal of Project Management, Vol. 27 (2009), No. 2, pp. 154-165.
http://dx.doi.org/10.1016/j.ijproman.2008.09.002

 

Lehtonen & Martinsuo analyse the boundary spanning activities of change programmes.  They find five different types of organisational integration – internal integration 1a) in the programme, 1b) in the organisation; external integration 2a) in the organisation, 2b) in the programme, and 3) between programme and parent organisation.

Furthermore they identify mechanisms of integration on these various levels.  These mechanisms are

  Mechanism of integration
Structure & Control Steering groups, responsibility of line managers
Goal & content link Programme is part of larger strategic change initiative
People links Cross-functional core team, part-time team members who stay in local departments
Scheduling & Planning links Planning, project management, budgeting, reporting
Isolation Abandon standard corporate steering group, split between HQ and branch roll-out

 

Among most common are four types of boundary spanning activities – (1) Information Scout, (2) Ambassador, (3) Boundary Shaping, and (4) Isolation.  Firstly, information scouting is done via workshops, interviews, questionnaire, data requests &c.  Secondly, the project ambassador presents the programme in internal forums, focuses on quick wins and show cases them, publishes about the project in HR magazines &c.  Thirdly, the boundary shaping is done by negotiations of scope and resources, and by defining responsibilities.  Fourthly, isolation typically takes place through withholding information, establishing a separate work/team/programme culture, planning inside; basically by gate keeping and blocking.   

Making a difference? Evaluating an innovative approach to the project management Centre of Excellence in a UK government department (O’Leary & Williams, 2008)

Donnerstag, Oktober 23rd, 2008

Making a difference? Evaluating an innovative approach to the project management Centre of Excellence in a UK government department (O’Leary & Williams, 2008)

O’Leary, Tim; Williams, Terry: Making a difference? Evaluating an innovative approach to the project management Centre of Excellence in a UK government department; in: International Journal of Project Management, Vol. 26 (2008), No. 5, pp. 556-565.
http://dx.doi.org/10.1016/j.ijproman.2008.05.013

The UK has rolled out the ambitious programme of setting-up IT Centres of Excellence in all its departments. Focal point of these Centres of Excellence are Programme Offices.

The role of these Programme Offices has been defined as: Reporting, Recovering & Standardising.
The objectives for the programme offices are monitoring and reporting the status of the IT initiatives in the department, and implementing a structured life cycle methodology. This methodology ties in with a stage-gate framework that needs to be introduced. Additionally hit-teams of delivery managers have been set-up to turn-around ailing projects.

O’Leary and Williams find that the interventions seem to work successfully, whereas the reporting and standardisation objective has yet to be fulfilled. Moreover the authors analyse the root causes for this success. They found that the basis of success was:

  • Administrative control of department’s IT budget
  • Leadership of IT director
  • Exploitation of project management rhetoric
  • Quality of delivery managers

Relating, reflecting and routinizing: Developing project competence in cooperation with others (Söderlund et al., 2008)

Montag, Oktober 20th, 2008

Relating, reflecting and routinizing: Developing project competence in cooperation with others (Söderlund et al., 2008)

Söderlund, Jonas; Vaagaasar, Anne Live; Andersen, Erling S.: Relating, reflecting and routinizing – Developing project competence in cooperation with others; in: International Journal of Project Management, Vol. 26 (2008), No. 5, pp. 517-526.
http://dx.doi.org/10.1016/j.ijproman.2008.06.002

Söderlund et al. explore the question – How do organisations build project management capabilities? They analyse a focal project to show how the specific competence, project management, is build in an ever changing environment. As such comptence creation is situated and recursive.

The authors use a process view to explain the capabilities building. The process is three-fold – (1) Relating, (2) Reflecting, and (3) Routinising.

First step – Relating to expand the resource base, in this step the organisation

  • Acknowledges the situated character of project competence
  • Expands the resource base, which builds social capital
  • Engages in boundary spanning activites to cooperate with stakeholders and act against de-coupling, which decreases the overall resources needed for the authority system as coordination mechanism
  • Creates interdependencies

Second step – Reflecting to improve use of resource base, in this step the organisation highlights actions of importance for institutionalising a common frame of reference and stimulating shared reflection in the project. As such it:

  • Improves the resource base
  • Engages in problem solving
  • Shifts from exploitation based to experimentation learning, which re-uses previous processes, and recycles old solutions
  • Detects system-wide errors & generates new associations

Third step – Routinising to secure resource base and improve relational activity, in this step the organisation tries to ensure the best use of its resource base. Therefore it

  • Codifies new knowledge
  • Triggers reflecting
  • Exploits what is known
  • Emphasises and builds project-level comptence

Tailored task forces: Temporary organizations and modularity (Waard & Kramer, 2008)

Montag, Oktober 20th, 2008

Tailored task forces: Temporary organizations and modularity (Waard & Kramer, 2008)

Waard, Erik J. de; Kramer, Eric-Hans: Tailored task forces – Temporary organizations and modularity; in: International Journal of Project Management, Vol. 26 (2008), No. 5, pp. 537-546.
http://dx.doi.org/10.1016/j.ijproman.2008.05.007

As a colleague once put it: Complex projects should be organised like terrorist organisations – Autonomous cells of highly motivated individuals.

Waard & Kramer do not analyse projects but it’s fast paced and short lived cousin – the task force. The task force is THE blueprint for an temporary organisation. The authors found that the more modularised the parent company is, the easier it is to set-up a task force/temporary organisations. Waard & Kramer also found that the temporary organisations are more stable if set-up by modular parent companies. They explain this with copying readily available organisational design principles and using well excercised behaviours to manage these units.

The more interesting second part of the article describes how a company can best set-up task forces. Waard & Kramer draw their analogy from Modular Design.

„Building a complex system from smaller subsystems that are independently designed yet function together“

The core of modular design is to establish visible design rules and hidden design parameters. The authors describe that rules need to be in place for (1) architecture, (2) interfaces, and (3) standards. The remaining design decisions is left in the hands of the task force, which is run like a black box.
In this case Architecture defines which modules are part of the system and what each modules functionality is. Interface definition lays out how these modules interact and communication. Lastly, the Standards define how modules are tested and how their performance is measured.

Embedding projects in multiple contexts – a structuration perspective (Manning, 2008)

Freitag, Oktober 3rd, 2008

Embedding projects in multiple contexts – a structuration perspective (Manning, 2008)

Manning, Stephan: Embedding projects in multiple contexts – a structuration perspective; in: International Journal of Project Management, Vol. 26 (2008), No. 1, pp. 30-37.
http://dx.doi.org/10.1016/j.ijproman.2007.08.012

Manning argues that projects are embedded in multiple contexts at the same time. These context facilitate and constrain the project at the same time and dynamically he describes this as „projects partly evolve in idiosyncratic ways as temporary systems, embedding needs to be understood as a continuous process linking projects to their environments“ (p.30).

Manning bases his analysis on Structuration Theory. It’s premise is to analyse action and structure (to interdependent concepts) in practice. Structuration Theory is defined by three key concepts – (1) structure, (2) actors, and (3) reflexive monitoring.

Structure is the set of symbolic and normative rules found in organisations. Furthermore the structure is set by authoritative and allocative resources. Actors are defined as potentially powerful and knowledgeable agents, who apply rules and resources in interactions, thus impacting the flow of events. As such structure impacts actions, which in turn impacts the structure. Reflexive monitoring is exactly this feedback loop from action to structure.

Applying structuration theory to projects Manning builds the concept of the project as temporary organisation, which is characertised by its tasks (=specification), times (=constraints), and teams (=relations). The author furthermore notices a constant process of disembedding and re-embedding into different contexts.

Which contexts are there? Manning identfies three. (1) organisations which are the collecitve actors engagned in coordinating projects, (2) interorganisational networks which are relations of legally independent organisations, and (3) organisation fields which are areas of institutional life by organisations and their members. Projects are embedded in all three of these contexts at the same time.

Lastly, Manning describes two embedding and re-embedding activities. Enactment of social contexts takes place top-down, that is from organisation fields –> interorganisational networks –> organisations –> projects, whereas the reproduction of social contexts takes place bottowm up.

Post-project reviews as a key project management competence (Anbari et al., 2008)

Mittwoch, September 17th, 2008

 Post-project reviews as a key project management competence

Anbari, Frank T.; Carayannis, Elias G.; Voetsch, Robert J.: Post-project reviews as a key project management competence; in: Technovation, Vol. 28 (2008), No. 10, pp. 633-643.
http://dx.doi.org/10.1016/j.technovation.2007.12.001

George Santayana was the wise guy who said: „Those who cannot remember the past are condemned to repeat it.“ At university I learned that 2 strategies exist to make an organisation remember it’s past – Internalisation and Codification. While internalisation usually happens anyway and an organisation only needs to keep track on who did which projects in the past, so that he can be interviewed, the codification bit is tricky.

Anbari et al. describe which interest are held by which stakeholder group and how that is going to impact any knowledge management or lack thereof. The authors also outline useful techniques and critical aspects, plus when project reviews are most usefully held during the project lifecycle.

Furthermore, the paper discusses where post-project reviews fit into the project life cycle and project management processes. It assesses how such reviews can assist an organization in improving the manner in which its projects are conceived, planned, implemented, reported, and evaluated.

Finally Anbari et al. outline a 3-fold growth model for organisations
(1) Vicious circle = no real reviews
(2) Functional circle = reviews which no one knows about
(3) Virtuous circle = reviews everybody knows.

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

Dienstag, 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.

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.]

Fundamental Uncertainties in Projects and the Scope of Project Mangement (Atkinson et al. 2006)

Montag, Juli 7th, 2008

Uncertainty(1-Thumb) Uncertainty(2-Thumb)

Atkinson, Roger; Crawford, Lynn; Ward, Stephen: Fundamental Uncertainties in Projects and the Scope of Project Management, in: International Journal of Project Management, Vol. 24 (2008), pp. 687-698.

Very interesting article, clearly in the normative/positivist’s tradition of how to do Risk Management better. Firstly the authors dissect uncertainties typically found in projects into (1) Uncertainty in estimates, (2) Uncertainty with project parties, and (3) Uncertainty with project life cycle. What does it matter? The authors argue that not all uncertainties are typically the scope of classic risk management. Therefore the project objective should be the ultima ratio, especially if trade-off decisions are needed. Furthermore crystal clear decision making needs one decision-maker, therefore project uncertainties need an owner.

In the second part (on my page 2) Atkinson et al. outline the difference between hard and soft projects. They do outline some characteristics of hard vs. soft projects, e.g. degree of external influences, tangibility of artefacts. Secondly they outline two modes of problem-solving sense-making, and data collecting. They put forward, that a problem rooted in a difference in information required vs. information at hand, calls for a data collection effort to solve; whereas a problem caused by different interpretion of the same data requires sense-making as a problem-solving technique. Moreover they locate the typical soft projects in a high ambiguity and high uncertainty quadrant, thus needing sense-making, and value analysis for problem solving.

Lastly they call for trust (especially on soft projects) instead of controls. And outline a Trust Audit as a project management tool, instead of auditing controls.