Project organization
From apppm
(Difference between revisions)
Marcus chr (Talk | contribs) |
Marcus chr (Talk | contribs) m |
||
| Line 3: | Line 3: | ||
== Abstract == | == Abstract == | ||
| − | The success of a project is highly dependent of 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''. | + | The success of a project is highly dependent of 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 vizualize and hence intuitively communicate the organizational structure along with its division of authority is using organization charts (or organigrams). However, this tool illustrates vertical lines of communication, and 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 divion rather than constraining the organizational communication. | + | 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 vizualize and hence intuitively communicate the organizational structure along with its division of authority is using organization charts (or organigrams). However, this tool illustrates vertical lines of communication, and 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 divion rather than constraining the organizational communication <ref name="lock"/>. |
__TOC__ | __TOC__ | ||
== Big idea == | == Big idea == | ||
| + | <ref name="prince2"/><ref name="lock"/> | ||
* What is project organization (including essential aspects described), and what is its purpose (why is it important)? | * 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? | * What consequences occur if project organization is neglected? | ||
| Line 20: | Line 21: | ||
=== Organization charts (organigrams) === | === Organization charts (organigrams) === | ||
| − | + | ==== Project matrix organizations ==== | |
| − | + | ==== Project team organization ==== | |
| + | <ref name="lock"/> | ||
| − | === | + | === 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 === | === Tool/method 3 === | ||
| Line 32: | Line 36: | ||
* 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 === |
| − | === | + | === Agile PM methods with well-established project organization === |
=== Discussing Tool/method 3 === | === Discussing Tool/method 3 === | ||
== Annotated bibliography == | == Annotated bibliography == | ||
| + | <ref name="PMI"/> | ||
== References == | == References == | ||
| − | + | <references> | |
| − | + | <ref name="lock">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).</ref> | |
| − | + | ||
| − | + | <ref name="prince2">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).</ref> | |
| − | + | ||
| − | + | <ref name="PMI">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)</ref> | ||
| + | |||
| + | |||
| + | </references> | ||
Revision as of 10:50, 12 February 2023
A part of understanding the context under purpose.
Abstract
The success of a project is highly dependent of 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 vizualize and hence intuitively communicate the organizational structure along with its division of authority is using organization charts (or organigrams). However, this tool illustrates vertical lines of communication, and 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 divion rather than constraining the organizational communication [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?
- What are the current modern and updated ways of doing this? (This have will be further discussed in applications).
Application
- How should project managers approach project organization?
- What do they need to reflect upon before diving into different methods and tools?
- 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
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 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)
