Project organization
Marcus chr (Talk | contribs) |
Marcus chr (Talk | contribs) |
||
| Line 3: | Line 3: | ||
== Abstract == | == Abstract == | ||
| − | The success of a project is highly dependent | + | The success of a project is highly dependent on the project organization, which is defined as a clear establishment in the project beginning of the project management team structure along with a communication approach. Maintaining the project organization during the entire project is essential to make the project a success. According to the PRINCE2 standard, the purpose of project organization is ''to define and establish the project's structure of accountability and responsibilities'' <ref name="prince2"/>. |
| − | To successfully create and institutionalize a project organization, the project authority should be clearly communicated throughout the project team. This implies that each project team member knows their respective responsibilities. An effective way to visualize and hence intuitively communicate the organizational structure along with its division of authority is using organization charts (or organigrams). | + | To successfully create and institutionalize a project organization, the project authority should be clearly communicated throughout the project team. This implies that each project team member knows their respective responsibilities. An effective way to visualize and hence intuitively communicate the organizational structure along with its division of authority is using organization charts (or organigrams). <ref name="lock"/>. |
__TOC__ | __TOC__ | ||
| Line 13: | Line 13: | ||
* What consequences occur if project organization is neglected? | * What consequences occur if project organization is neglected? | ||
| − | Project organization is a term describing the structure of a project throughout its entire lifecycle based on communication, coordination and management. The purpose of project organization is to define a structure of responsibilities and accountability across the project management team <ref name="prince2"/>. Therefore, an effective establishment of a project organization requires unambiguously communicated authority. Additionally, each project management team member should know their specific role along with the associated responsibilities. Neglecting efficient organization of projects often leads to a lack of motivation, which causes schedule overruns and hence | + | Project organization is a term describing the structure of a project throughout its entire lifecycle based on communication, coordination and management. The purpose of project organization is to define a structure of responsibilities and accountability across the project management team <ref name="prince2"/>. Therefore, an effective establishment of a project organization requires unambiguously communicated authority. Additionally, each project management team member should know their specific role along with the associated responsibilities. Neglecting efficient organization of projects often leads to a lack of motivation, which causes schedule overruns and hence budget overruns <ref name="lock"/>. |
| Line 19: | Line 19: | ||
* What are the current modern and updated ways of doing this? (This have will be further discussed in applications). | * What are the current modern and updated ways of doing this? (This have will be further discussed in applications). | ||
- Agile versus non-agile | - Agile versus non-agile | ||
| − | |||
| − | |||
| − | |||
== Application == | == Application == | ||
* How should project managers approach project organization? | * How should project managers approach project organization? | ||
| + | This section will provide a broad type of guidance to PMs, which is applicable to all projects. | ||
| + | |||
* What do they need to reflect upon before diving into different methods and tools? | * What do they need to reflect upon before diving into different methods and tools? | ||
| + | This section will describe what needs to be considered in the individual projects before choosing which methods to apply. This is because every project is unique despite there is a lot of identical aspects in all projects. | ||
| + | |||
| + | === Existing tools and methods to organize projects === | ||
* What different methods/tools exist, and what characterizes each of them? | * What different methods/tools exist, and what characterizes each of them? | ||
| − | === Organization charts (organigrams) === | + | |
| − | ==== Project matrix organizations ==== | + | ==== Organization charts (organigrams) ==== |
| − | ==== Project team organization ==== | + | ===== Project matrix organizations ===== |
| + | ===== Project team organization ===== | ||
<ref name="lock"/> | <ref name="lock"/> | ||
| Line 43: | Line 46: | ||
* Critical reflection regarding project organization in general. | * Critical reflection regarding project organization in general. | ||
* What can each tool/method do, and under what circumstances should they be applied? | * What can each tool/method do, and under what circumstances should they be applied? | ||
| + | |||
* Which tools/methods are a part of the current standards of project organization, and which ones extend the current standards of project organization. | * Which tools/methods are a part of the current standards of project organization, and which ones extend the current standards of project organization. | ||
=== Organizational charts === | === Organizational charts === | ||
| + | Despite organization charts are very effective to communicate organizational structure and division of authority, they are illustrated by vertical lines of communication. In practice, communication is far more complex due to informal communication across the organization. Hence this tool is mostly applicable to organizational structure and its responsibility division rather than constraining the organizational communication <ref name="lock"/>. | ||
| + | |||
=== Agile PM methods with well-established project organization === | === Agile PM methods with well-established project organization === | ||
=== Discussing Tool/method 3 === | === Discussing Tool/method 3 === | ||
Revision as of 16:00, 19 February 2023
Purpose --> Understanding the context
Abstract
The success of a project is highly dependent on the project organization, which is defined as a clear establishment in the project beginning of the project management team structure along with a communication approach. Maintaining the project organization during the entire project is essential to make the project a success. According to the PRINCE2 standard, the purpose of project organization is to define and establish the project's structure of accountability and responsibilities [1].
To successfully create and institutionalize a project organization, the project authority should be clearly communicated throughout the project team. This implies that each project team member knows their respective responsibilities. An effective way to visualize and hence intuitively communicate the organizational structure along with its division of authority is using organization charts (or organigrams). [2].
Contents |
Big idea
- What is project organization (including essential aspects described), and what is its purpose (why is it important)?
- What consequences occur if project organization is neglected?
Project organization is a term describing the structure of a project throughout its entire lifecycle based on communication, coordination and management. The purpose of project organization is to define a structure of responsibilities and accountability across the project management team [1]. Therefore, an effective establishment of a project organization requires unambiguously communicated authority. Additionally, each project management team member should know their specific role along with the associated responsibilities. Neglecting efficient organization of projects often leads to a lack of motivation, which causes schedule overruns and hence budget overruns [2].
State of the art
- What are the current modern and updated ways of doing this? (This have will be further discussed in applications).
- Agile versus non-agile
Application
- How should project managers approach project organization?
This section will provide a broad type of guidance to PMs, which is applicable to all projects.
- What do they need to reflect upon before diving into different methods and tools?
This section will describe what needs to be considered in the individual projects before choosing which methods to apply. This is because every project is unique despite there is a lot of identical aspects in all projects.
Existing tools and methods to organize projects
- What different methods/tools exist, and what characterizes each of them?
Organization charts (organigrams)
Project matrix organizations
Project team organization
Agile PM methods with well-established project organization
- How are agile methods like SCRUM or KANBAN applied to a well organized project?
- Are agile methods more applicable than less agile methods like the waterfall method?
Tool/method 3
Limitations
- Critical reflection regarding project organization in general.
- What can each tool/method do, and under what circumstances should they be applied?
- Which tools/methods are a part of the current standards of project organization, and which ones extend the current standards of project organization.
Organizational charts
Despite organization charts are very effective to communicate organizational structure and division of authority, they are illustrated by vertical lines of communication. In practice, communication is far more complex due to informal communication across the organization. Hence this tool is mostly applicable to organizational structure and its responsibility division rather than constraining the organizational communication [2].
Agile PM methods with well-established project organization
Discussing Tool/method 3
Annotated bibliography
References
- ↑ 1.0 1.1 A. (2017). Managing successful projects with prince2 2017 edition. The Stationery Office Ltd., Available at: https://ebookcentral.proquest.com/lib/dtudk/reader.action?docID=4863041 (Accessed: 12 February 2023).
- ↑ 2.0 2.1 2.2 2.3 D. Lock, Project Management. 10th edn., (Gower Published Limited, 2013), pp. 131–154, Available at: https://www.perlego.com/book/1645789/project-management-pdf (Accessed: 12 February 2023).
- ↑ Project Management Institute, Inc. (PMI). (2021). A Guide to the Project Management Body of Knowledge (PMBOK ® Guide) – 7th Edition and The Standard for Project Management - Section 2.2.1 and 3.2. Project Management Institute, Inc. (PMI). Sections respectively retrieved from https://app.knovel.com/hotlink/pdf/id:kt012LZGJB/guide-project-management/project-team-management and https://app.knovel.com/hotlink/pdf/id:kt012LZF39/guide-project-management/create-collaborative (Accessed: 12 February 2023)
