Project based organisations
From apppm
(Difference between revisions)
| Line 1: | Line 1: | ||
| − | |||
| − | |||
| − | |||
| − | Big | + | == Big Idea == |
| − | |||
| − | |||
| − | |||
| − | + | === What are project based organisations | |
| − | + | Project based organisations (PBO) is an organisational structure where projects are the main driver of business.<ref name="DaviesHobday"/> 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. | |
| − | + | ||
| − | + | [[File:kurt_lewis.png|380px|thumb|Figure 1: Kurt Lewin's three step change management process (created by Cirkeline, inspired by <ref>''https://expertprogrammanagement.com/2021/09/unfreeze-change-refreeze/'' ''Unfreeze, change, refreeze'', last visited 02-03-2023</ref>)]] | |
| − | + | [[File:PBO_functional.jpg]] | |
| − | + | ||
| + | === Why choose a project based organisational structure? === | ||
| + | |||
| + | The high level of control that lies with the project managers of each project in the PBO means that each project | ||
| − | |||
| − | |||
*Organisation carrying out many projects (Sundqvist et al., 2014) | *Organisation carrying out many projects (Sundqvist et al., 2014) | ||
* An organizational structure that helps the overall project management of all projects.(Söderlund et al., 2014) | * An organizational structure that helps the overall project management of all projects.(Söderlund et al., 2014) | ||
| − | * Further elaborate using the key reference (Davies and Hobday, 2005), waiting to be delivered from librabry | + | * Further elaborate using the key reference (Davies and Hobday, 2005), waiting to be delivered from librabry. |
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | === Setting the terminology === | ||
| + | |||
| + | |||
| + | |||
| − | === What are the key | + | === What are the key characteristics of project based organisations? === |
*Knowledge- transfer is one of the key things to utilised to reap the benefits of PBOs(Sundqvist et al., 2014) | *Knowledge- transfer is one of the key things to utilised to reap the benefits of PBOs(Sundqvist et al., 2014) | ||
*Innovation (creativity) in PBO's (Söderlund et al., 2014)(Thiry and Deguire, 2007) | *Innovation (creativity) in PBO's (Söderlund et al., 2014)(Thiry and Deguire, 2007) | ||
*Efficiency… effectiveness…. These are the kay aspect that PBO structures focus on improving more holistically (Sundqvist et al., 2014) | *Efficiency… effectiveness…. These are the kay aspect that PBO structures focus on improving more holistically (Sundqvist et al., 2014) | ||
| − | === How do project based organisations relate to program management | + | |
| + | |||
| + | === How do project based organisations relate to program management === | ||
*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. (Project Management Institute, 2017) | *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. (Project Management Institute, 2017) | ||
*The theories on project management and organisational structures have not always been interrelated and investigated as correlating topics and theories. (Sundqvist et al., 2014) | *The theories on project management and organisational structures have not always been interrelated and investigated as correlating topics and theories. (Sundqvist et al., 2014) | ||
| + | |||
| + | |||
=== Why choose a project based organisation structure? === | === Why choose a project based organisation structure? === | ||
| Line 54: | Line 61: | ||
== Application == | == Application == | ||
| − | === | + | === In what context? === |
* how and in what context to utilise the benefits of having an project-based organisational structure, drawing on the theory above in the applied field. (Mahura and Birollo, 2021) | * how and in what context to utilise the benefits of having an project-based organisational structure, drawing on the theory above in the applied field. (Mahura and Birollo, 2021) | ||
* how the above mentioned structure influences the leadership, discussing both centralised and decentralised management (Project Management Institute, 2017) | * how the above mentioned structure influences the leadership, discussing both centralised and decentralised management (Project Management Institute, 2017) | ||
*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 (Mahura and Birollo, 2021) | *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 (Mahura and Birollo, 2021) | ||
| + | |||
=== A case study === | === A case study === | ||
| Line 64: | Line 72: | ||
*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) | ||
| − | === | + | === Application === |
== Limitations == | == Limitations == | ||
| Line 84: | Line 92: | ||
== Annotated bibliography == | == Annotated bibliography == | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | + | <references> | |
| + | <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> | ||
Revision as of 11:47, 9 April 2023
Contents |
Big Idea
=== What are project based organisations
Project based organisations (PBO) is an organisational structure where projects are the main driver of business.[1] 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.
Why choose a project based organisational structure?
The high level of control that lies with the project managers of each project in the PBO means that each project
- Organisation carrying out many projects (Sundqvist et al., 2014)
- An organizational structure that helps the overall project management of all projects.(Söderlund et al., 2014)
- Further elaborate using the key reference (Davies and Hobday, 2005), waiting to be delivered from librabry.
Setting the terminology
What are the key characteristics of project based organisations?
- Knowledge- transfer is one of the key things to utilised to reap the benefits of PBOs(Sundqvist et al., 2014)
- Innovation (creativity) in PBO's (Söderlund et al., 2014)(Thiry and Deguire, 2007)
- Efficiency… effectiveness…. These are the kay aspect that PBO structures focus on improving more holistically (Sundqvist et al., 2014)
How do project based organisations relate to program management
- 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. (Project Management Institute, 2017)
- The theories on project management and organisational structures have not always been interrelated and investigated as correlating topics and theories. (Sundqvist et al., 2014)
Why choose a project based organisation structure?
This chapter will answer:
- Problem it solves: organisational structures instead of operational project management – the framework and context of the project management has an influence on the management and the success (Leiringer and Zhang, 2021)
- How Efficiency and effectivness can be improved (relate to the key aspects of PBO's)
- 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 PBO's are different from Matrix organising structure (Davies and Hobday, 2005)
- Explain how they tackle fast change and innovation (Davies and Hobday, 2005)
Application
In what context?
- how and in what context to utilise the benefits of having an project-based organisational structure, drawing on the theory above in the applied field. (Mahura and Birollo, 2021)
- how the above mentioned structure influences the leadership, discussing both centralised and decentralised management (Project Management Institute, 2017)
- 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 (Mahura and Birollo, 2021)
A case study
- Not yet specified (will be chosen later to fit the context of the rest of the wiki article)
Application
Limitations
What to be aware of in project based organisations
- how the framework has flexibility as a core, and this can also a limitation because project-based organisation can differ so much it becomes more difficult to understand and generalise across project based organisations (Turner and Miterev, 2019)
- in line with the above and the theory how knowledge sharing could be a strength but if not done is one of the weak links of project-based organisations
- More to be added
The status qou in the litterature
- a lot of articles referring to project based organisations but a lot may not use the terminology Project-based organisation, but rather describe it or call it something else
- Articles often refer to it but do not describe it in greater detail – one book had “project based organisation” in the title but did not refer to that actual term once in the text of the book. (Pryke, 2017)
- “The embeddedness in projects” is pointed out by (Sundqvist et al., 2014), to be one of the acknowledgements one needs to make.
- When is an organisation project based?
- How embedded should the project practice be in an organisation to call it project based?
- Do project based organisations have the same structure? Is it a question of structure or a question of the amount of project or that the organisation have somehow organised themselves around project in some way (not specified/defined by literature)
- The definition of a project is highlighted as a part of the discussion on project management and organisation theories – this is the most important thing to remember (Söderlund et al., 2014)
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
- ↑ https://expertprogrammanagement.com/2021/09/unfreeze-change-refreeze/ Unfreeze, change, refreeze, last visited 02-03-2023
