Project based organisations
From apppm
(Difference between revisions)
| Line 30: | Line 30: | ||
The different terms are often used in different context and highlight a specific field of study, eg. temporary organisations are often PBO's but refer to the study of the organisational structures whereas literature using the term project based organisation is often in the crossing between the two fields of study; project management and organisational structures<ref name="Bakker">. | The different terms are often used in different context and highlight a specific field of study, eg. temporary organisations are often PBO's but refer to the study of the organisational structures whereas literature using the term project based organisation is often in the crossing between the two fields of study; project management and organisational structures<ref name="Bakker">. | ||
| − | In this article | + | In this article the term PBO is used to cover these different terms. Furthermore, the term "pure PBO" is used when refferring to a PBO that is not diluted but in the given form described above. |
| Line 37: | Line 37: | ||
The article has already given an overview of some the characteristics of project based organisations. This paragraph will present these in more detail, and explain the underlying mechanisms and principles of the characteristics. | The article has already given an overview of some the characteristics of project based organisations. This paragraph will present these in more detail, and explain the underlying mechanisms and principles of the characteristics. | ||
| − | + | * projects as driver of business | |
| + | ** PBO are contextual: level of product or system innovation influences the given organisational structure as well as the project management | ||
| + | * The power of the project manager | ||
| + | ** Project manager is dependent on distributing the management | ||
| + | ** PM has huge power over project and this is the key to agility and flexibilty that is inherent to PBO's, but is also leaves the PM with huge responsibility - Project management becomes of vital importance | ||
| + | ** Cross functional business expertise is needed in PBO | ||
| + | ** Advantage: the PM's authority leads to flexibility | ||
| − | * | + | * The structure of PBOs and its advantages in project work |
| − | * | + | ** open structure leads to innovation - temporary collaboration forms |
| − | * | + | ** co-creation and inclusion of the client in the project progress |
| + | ** prime contractors can look very different - PBO structure helps adapt to the best possible way of operating with the specific client | ||
| + | ** only one main contact point - that can take action on the spot without asking 5 functional units permission | ||
| + | ** flexible structure leads to proactive to uncertainties | ||
| + | * project shape the organisation | ||
| + | ** kownledge capabilites resources are achieved and shaped through the project <ref name="Leiringer_Zhang"> | ||
| + | ** prime contractors can look very different - this shapes the communication etc. | ||
| − | + | * pure PBO or diluted to PLO | |
| + | ** PBO can exist within a static organisation | ||
| + | ** Some of the weaknesses of PBO can be lessened or converted to strengths by "diluting" the pure PBO | ||
| + | ** What does the PBO look like when embeeded in a static organisation - describing the mechanisms between the flexibility of the PBO and the static nature of the parent organisation (Mahura og Birillo) (læs op på denne) | ||
| − | * | + | * How PBO's are different from the Matrix organisation (Davies and Hobday, 2005) |
| − | + | ||
| + | All of the above should be elaborated in text. | ||
| − | |||
| − | + | References that still need reading: | |
| − | * | + | *Liekinger (læs op på denne) |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
== Application == | == Application == | ||
| − | === | + | === The context of Project based organisations === |
| − | |||
| − | |||
| − | |||
| Line 78: | Line 84: | ||
*Not yet specified (will be chosen later to fit the context of the rest of the wiki article) | *Not yet specified (will be chosen later to fit the context of the rest of the wiki article) | ||
| − | === | + | === A guide to PBO === |
| − | + | Still to be researched. Here a kind of step by step guide is though to be created from relevant litterature. | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | == | + | == Limitations of PBO == |
| − | * | + | |
| − | * | + | *Knowledge sharing is one of the key limitations of PBO's - because the PBO handles everything in a flexible way the formal structures for knowledge sharing and developing skills <ref name="Thiry_Deguire"> The underlying mechanism are the formal structure eg. that reporting is missing or done in different ways from project to project. Reporitn is adapted to the projects' needs but makes it harder to communicate across projects <ref name="DaviesHobday"> |
| − | * | + | ** In PBO there are no structures integrated that incentivise cross project learning <ref name="DaviesHobday">. Therefore actions needs to be taken explicit to help these constraints and to effectivise project work. |
| − | ** | + | ** No time set aside for learning and skill development <ref name="DaviesHobday">. This is further strenghted in pure PBO's where you always need to be moving to the next project as the business depends on it. Therefore, there is no formal time set aside to learn from the previous projects. |
| − | * | + | |
| − | ** | + | |
| − | * | + | * Learning is not only internally in the PBO or organisation, but learning how to establish good collaboration relationsships is missed. Here lies potential for improving collaboration processes <ref name="Leiringer_Zhang">. |
| + | |||
| + | * Projects within the PBO, or if part of a static organisation become isolated and have a hard time communicating their benefits etc. to senior management and learn across projects this can create tension acroos the company wide processes. <ref name="DaviesHobday"> This can furthermore make project teams become disconnected, which again adds to the tension across projects, that should learn from eachother and not diconnect from one another. <ref name="Leiringer_Zhang"> | ||
| + | * Hard to show the importance and impact of the project <ref name="DaviesHobday"> | ||
| + | |||
| + | |||
| + | *how the framework has flexibility as a core, and this can also be a limitation because project-based organisation can differ so much it becomes more difficult to understand and generalise across project based organisations <ref name="Turner_Miterev"> | ||
| + | |||
| + | * Pure PBO may be risky - it depends on project which means you always need to be moving to the next project to keep being in business <ref name="DaviesHobday">. | ||
| + | |||
| + | * For employees PBO's can create anxiety and uncertainty because they do not know where to go next <ref name="DaviesHobday"> <ref name="Bakker">. | ||
| + | |||
| + | * The domain specific leadership is dispersed - this means two things: | ||
| + | # The project is dependent on a project manager who is highly skillfull in project management | ||
| + | ## becasue there are no functional units - it is hard to divide in domains - everybody needs to know a little bit of everything - you do not utilise specialities as much | ||
| + | |||
| + | |||
| + | |||
| + | === Opportunities that arise from the mapped out limitations === | ||
| + | |||
| + | One of the key opportunities that arise from the limitations found in the litterature is that project and programme management are of vital importance to target some of the limitations of the PBO. The PBO has a lot of valuable characteristics and advantages. By targeting some of the limitations | ||
| + | |||
| + | *organisational structures instead of operational project management – the framework and context of the project management has an influence on the management and the success of the project (Leiringer and Zhang, 2021) | ||
| + | * how PBO's can help stabilize specific factors whilst keeping flexibility for the changing nature of projects. (Jerbrant, 2013) (Jerbrant and Karrbom Gustavsson, 2013)(Pryke, 2017) | ||
| + | |||
| + | * How PBO's can be a supportive framework for program and portfolio management and its success, due to several tasks being streamlined across project (Petro and Gardiner, 2015) | ||
| + | |||
| + | *how knowledge sharing and learning can happen within the organisation to help learn across the project - and when this is is relevant and when it is not <ref name="Mahura_Birollo"> | ||
| + | |||
| + | *Connecting to project management and the PMI (or other standard) – there is multiple levels of project and they form huge complexities within organisations(Söderlund et al., 2014). The different levels may be called programs and portfolios, and need management as well, and this management need to be and embedded part of the context of the project, programs and portfolios. <ref name="PMI"> | ||
| + | *The theories on project management and organisational structures have not always been interrelated and investigated as correlating topics and theories. (Sundqvist et al., 2014) | ||
| + | |||
| + | *Knowledge- transfer is one of the key things to utilised to reap the benefits of PBOs, but is really hard(Sundqvist et al., 2014) | ||
| + | *Innovation (creativity) in PBO's (Söderlund et al., 2014) <ref name="Thiry_Deguire"> | ||
| + | *Efficiency… effectiveness…. These are the kay aspect that PBO structures focus on improving more holistically (Sundqvist et al., 2014) | ||
| + | *PBO influences the leadership, discussing both centralised and decentralised management <ref name="PMI"> | ||
| − | |||
| + | == References == | ||
<references> | <references> | ||
| Line 103: | Line 140: | ||
<ref name="DaviesHobday">Davies, A., Hobday, M., 2005. The project-based organisation, in: The Business of Projects: Managing Innovation in Complex Products and Systems. Cambridge University Press, pp. 117–147. https://doi.org/10.1017/CBO9780511493294.007</ref> | <ref name="DaviesHobday">Davies, A., Hobday, M., 2005. The project-based organisation, in: The Business of Projects: Managing Innovation in Complex Products and Systems. Cambridge University Press, pp. 117–147. https://doi.org/10.1017/CBO9780511493294.007</ref> | ||
<ref name="Leiringer_Zhang">Leiringer, R., Zhang, S., 2021. Organisational capabilities and project organising research. Int. J. Proj. Manag. 39, 422–436. https://doi.org/10.1016/j.ijproman.2021.02.003</ref> | <ref name="Leiringer_Zhang">Leiringer, R., Zhang, S., 2021. Organisational capabilities and project organising research. Int. J. Proj. Manag. 39, 422–436. https://doi.org/10.1016/j.ijproman.2021.02.003</ref> | ||
| + | <ref name="Mahura_Birollo">Mahura, A., Birollo, G., 2021. Organizational practices that enable and disable knowledge transfer: The case of a public sector project-based organization. Int. J. Proj. Manag. 39, 270–281. https://doi.org/10.1016/j.ijproman.2020.12.002</ref> | ||
| + | <ref name="PMI">Project Management Institute, I. (PMI), 2017. 1.8 Relationships among Portfolio Management, Organizational Strategy, Strategic Business Execution, and Organizational Project Management. Stand. Portf. Manag. (4th Ed.</ref> | ||
<ref name="Thiry_Deguire">Thiry, M., Deguire, M., 2007. Recent developments in project-based organisations. Int. J. Proj. Manag. 25, 649–658. https://doi.org/10.1016/j.ijproman.2007.02.001</ref> | <ref name="Thiry_Deguire">Thiry, M., Deguire, M., 2007. Recent developments in project-based organisations. Int. J. Proj. Manag. 25, 649–658. https://doi.org/10.1016/j.ijproman.2007.02.001</ref> | ||
| + | <ref name="Turner_Miterev">Turner, R., Miterev, M., 2019. The Organizational Design of the Project-Based Organization. Proj. Manag. J. 50, 487–498. https://doi.org/10.1177/8756972819859746</ref> | ||
| + | |||
| + | |||
| + | |||
| + | |||
| + | == Annotated bibliography == | ||
| + | |||
| + | Davies, A., Hobday, M., 2005. The project-based organisation, in: The Business of Projects: Managing Innovation in Complex Products and Systems. Cambridge University Press, pp. 117–147. https://doi.org/10.1017/CBO9780511493294.007 | ||
| + | |||
| + | This book is a great resource for understanding the core principles of project based organisations. The book is about projects and complex products and systems and suggests a form of PBO for the development of such complex and uncertain systems. In it you will find project management and organisational theories in general with a specific chapter dedicated to project based organisations. Here a case study compares the PBO to a functional organisation. | ||
Revision as of 20:34, 9 April 2023
Contents |
Big Idea
What are project based organisations?
Project based organisation (PBO) is an organisational structure where projects are the main driver of business. In a pure project based organisation the project manager will have control over all functions of the project, with only senior management to refer to. This means that the functional units, ie. R&D, finance, marketing etc. are integrated in each project in the PBO instead of going across multiple projects. Furthermore, because projects are the main driving force, each project organisation structure looks different. This is because projects drive the business and therefore also shapes the organisational structure. Figure 1 illustrates that projects are the driving force of the project based organisation, whilst the functional units and their expertise is the driving force of a functional unit, they are respectivly in the top of the organisational diagram. Furthermore it illlustrates how in the PBO, the functional units are integrated under each project and that each project in the PBO looks slightly different in the organisational structure, i.e. the functional units may be placed differently and some may be more important to some projects than others. The project based organisation stucture gives the project manager authority over resources. This high level of control that lie with the project managers of each project in the PBO leads to high flexibility within the project. [1]
Why choose a project based organisational structure?
The purpose of introducing a project based organisation is that it has the ability to deal with fast change as well as being proactive to uncertainty and project risk. Furthermore, PBO's have an openness in the organisational structure that makes it easier to work across organisations and include external stakeholders in the project process. Thus the PBO becomes an enabler for co-creation in projects. PBO's are proven to be useful when dealing with complex products or systems where the clients needs may change through the progression of the project as they gain more knowledge. [1]
The PBO terminology
The definition of a project based organisation can be hard to determine. This is because in litterature there are several terms and forms of project based organisations. This is partly because the project based organisation is dependent on context and therefore changes with it, which makes it difficult to define. Furthermore, the PBO can exist as a pure form like described above, but can also be diluted. In the diluted form "in which the needs of the project outweigh the functional influence on decision making"[1].
In the following will be given an overview of some of the terms that can refer to a form of PBO or organisational form that uses similar core principles Cite error: Closing </ref> missing for <ref> tag [1] [2] [3] [4] [5] [6]
Annotated bibliography
Davies, A., Hobday, M., 2005. The project-based organisation, in: The Business of Projects: Managing Innovation in Complex Products and Systems. Cambridge University Press, pp. 117–147. https://doi.org/10.1017/CBO9780511493294.007
This book is a great resource for understanding the core principles of project based organisations. The book is about projects and complex products and systems and suggests a form of PBO for the development of such complex and uncertain systems. In it you will find project management and organisational theories in general with a specific chapter dedicated to project based organisations. Here a case study compares the PBO to a functional organisation.
Cite error:
<ref> tags exist, but no <references/> tag was found
