File:Organizational chart matrix homemade.PNG

2023-05-05T09:12:28Z

Marcus chr: Marcus chr uploaded a new version of "File:Organizational chart matrix homemade.PNG"

File:Organizational chart matrix homemade.PNG

2023-05-05T09:07:09Z

Marcus chr:

File:Organizational chart project team organization homemade.PNG

2023-05-05T09:05:41Z

Marcus chr:

File:Organizational chart staff line project organization.PNG

2023-05-05T09:01:27Z

Marcus chr:

2023-04-30T13:32:34Z

Marcus chr:

Project organization

2023-04-30T12:27:03Z

Marcus chr:

Purpose --> Understanding the context

== Abstract ==

The success of a project is highly dependent on the term project organization. The term is defined as a clear establishment of the project management team structure along with a communication approach in the beginning of the project. 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). <ref name="lock"/>.

__TOC__

== Big idea ==

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. This decrease of confusion and uncertainty about responsibility and accountability will reduce the risk of conflict emergence between employees working on the project. Also, a well-defined project organization establishes common expectations among the project team members, which implies a united project team work to achieve the desired project objectives. Neglecting efficient organization of projects often leads to a lack of motivation, which causes schedule overruns and hence budget overruns <ref name="lock"/>. Accordingly, well planned project organization and maintaning it during the project is essential to the success of the project <ref name="kerzner"/>.

=== State of the art ===

The modern way to establish an effective organizational is to create an organization chart. Organization charts vertically represent the role or status and authority of each organization member. The status and authority decreases from top to bottom of the chart, which means the most powerful member organizational role is located in the top of the chart. An example of organization chart is given in '''Figure 1'''. This tool is very powerful to demonstrate and clearly communicate the authority and roles within projects. Additionally, it emphasizes the internal organizational context of the project. This can further be useful to communicate the organizational project governance structure and interdependencies between the specific project and other projects and/or programs of the organization <ref name="lock"/>.

[[File:Organizational chart.PNG|thumb|400px|'''Figure 1:''' Organization chart (simplified example) <ref name="lock"/>]]

<ref name="gary"/>

== Application ==
To ensure success of the project as a project manager, efficiently establishing a project organization is essential. However, since project managers tend to work in large organizations with many employees, it is redundant to create an organization chart involving the whole organization with all its associated nuances and politics. Therefore, it is recommended that project managers focuses only on the people having influence on activities of the project while creating the project organization structure.

Before initiating the creation of an organization chart, several different aspects are important to consider.

First of all, it is significant to consider what '''roles''' that needs to be assigned within the project team to achieve the defined objectives. The term role refers to a specific function assigned to an individual.

Since the project team roles identifies the functions needed to make the project a success, it is important to determine which '''competences''' that are associated with each role. When the identification of desired competences is executed, the roles are assigned to individuals from the organization. However, sometimes it is required to hire people to acquire the optimal competences if these are not already obtainable within the organization.

Assigning the roles to the right people implies assigning the '''responsibility''' associated with the roles. The individuals fulfilling their roles are accountable of the completion of the project activities related to their role of the project.

The '''authority''' over the project might already be determined and distributed between the project manager and their managers <ref name="gary"/>. In traditional project management, this would often be the case where mostly the project manager made the important decisions, managed deliverables and applied resources. However, today's project management is highly influenced by an agile approach. In this environment, the management style is rather participative than authoritarian. This implies that the management of the project team members is built on trust, which means that decisions made regarding the completion of project activities are made progressively by the project team members themselves <ref name="kerzner"/>. Hence the authority over the project is more divided between the project team members in the agile project environments.

=== Creating an organization chart ===

Ultimately, the organization chart of the project will be associated with the overall structure of the company regarding division of authority and roles. Therefore, if the organization in which the project takes place already has an organization chart, it is advantageous to either draw inspiration from that or create the organization chart of the project directly on the one made by the company.

Assuming the required roles within the project team are fulfilled, each role is supposed to be indicated as a box containing the function and the name of the employee. By convention, the function of an employee is supposed to be the job title. The boxes are then arranged with regard to authority, where the most powerful role of the project is placed at the top. As illustrated in '''Figure 1''', the manager of Department A is above the members of Department A. If this department e.g. represented a project team, the project manager would be the manager of Department A, while the project team would be represented as boxes below the project manager. Usually in case of smaller projects, the project team members are represented with equal authority, i.e. they are placed side-by-side horizontally. However, large projects often tend to deviate from this flat structure due to the increasing amount of employees. Accordingly, the authority is distributed further within the project team, and this implies more layers of authority below the project manager. The solid lines illustrated in '''Figure 1''' demonstrates lines of command. Downwards, the lines indicate who the employee can give commands to. Upwards, the lines indicate who the employee has to report to. Dotted lines between employees demonstrate appointed lines of communication or reporting. E.g. in '''Figure 1''', the manager of department B might have to communicate with the members of Department C for some specific reason, and this would then be indicated by a dotted line. However, the dotted lines are not usually implemented in organization charts. Finally, staff roles such as the Secretary in '''Figure 1''' have no direct authority. Nevertheless, by supporting their line manager, they exploit the authority and status of their manager.

There exist a broad range of different types of organization charts based on the terms and definitions specified above. The most efficient ones regarding project organization are project matrix organizations and project team organizations <ref name="lock"/>.

[[File:Organizational chart matrix.PNG|thumb|400px|'''Figure 2:''' Project matrix organization example where the project manager ("project coordinater" in the figure) has no direct line of authority over the project employees <ref name="lock"/>]]

[[File:Organizational chart project team organization.PNG|thumb|400px|'''Figure 3:''' Project team organization example where the project manager has direct authority over all aspects of the project <ref name="lock"/>]]

==== Project matrix organizations ====
A project matrix organization is an organizational structure often referred to as a ''coordination matrix'' or a ''functional matrix''. This kind of organization chart is used when a project is executed within an organization alongside its regular manufacturing activities. Consequently, the original line of command of the organization and its authority is allowed to continue normally parallel to the project execution. However, this implies that the project manager has no authority over any manager or their staff. Accordingly, the project manager must have high skills in dealing with people along with associated skills in motivation and reasoning. An example of a project matrix organization is illustrated in '''Figure 2'''. Note that the project manager in this figure is called ''Project coordinator'', and the vertical levels generally but not necessarily indicate authority.

In case conflicts arise and the project manager fails to resolve the matter, the project manager has the opportunity to seek support from the senior management. Hence the project manager can obtain the power needed to accomplish the needed changes to achieve the desired project objectives. This use of the management's authority is equivalent to how the secretary in '''Figure 1''' acquires authority in certain situations <ref name="lock"/>.

==== Project team organization ====

In case a project has its individual autonomous unit within an organization, the organization chart of the project is defined as a project team organization. The role of the project manager of this project organization is completely opposite to their role in project team organizations. In project team organization charts, the project manager is located on top of the autonomous project unit. This implies the project manager has a direct line of authority over all project employees. Hence the project manager is accountable for all specialized project facets alongside the traditional activities of work allocation, planning and progress. Such an organizational chart is shown in '''Figure 3''', which illustrates an example of a project team established to construct and design a chemical processing plant. The example demonstrates a project as an individual and autonomous unit within the organization due to its organized departments, which respectively are accountable for their own industrial disciplines required to achieve the desired project objectives. Since the project manager has complete responsibility over all project aspects, communication between technical practices are easier, and motivation of employees across departments becomes easier to achieve for the project manager. One way to enhance efficient communication within the project team across areas of expertise is by using the approach of [[Visual Project Management - War Rooms|war rooms]] <ref name="lock"/>.

== Limitations ==

It is important to acknowledge that effective project organization only reduces the need for change throughout the project lifecycle and does not completely eliminate the need for change. Therefore, despite organizing the project effectively, project managers still need to be open-minded towards changes throughout the project lifecycle <ref name="kerzner"/>.

=== Organization 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 emphasize organizational structure and its responsibility division rather than constraining the organizational communication <ref name="lock"/>. For instance using the Organization chart simplified example above, the manager of department A could be using the members of department B as consultants temporarily. In that case, the members of department B will report to the manager of department A instead of the manager of department B. Therefore, organization charts are effective foundation for project organization but not necessarily for strictly defining organizational communication.

Due to organizational changes or new projects arising, it is advantageous to create new organization charts. However, the resulting organizational changes of individuals' status or authority can cause unexpected reactions from people. Some people may feel they are not appreciated as sufficiently important employees, and an organizational feeling of injustice can arise <ref name="lock"/>. A potential solution is to distribute updated organization charts with a thorough explanation and enable employees to express their feelings and thoughts through open communication.

The organization charts typically only show the role of the project team member and not the specific assigned responsibilities. To emphasize the assignment of project tasks to individuals or teams within the overall project team, a [[Responsibility Assignment Matrix (RACI Matrix)|Responsibility assignment matrix]] is suitable to apply. An effective way of doing this is to construct and implement a [[Responsibility Assignment Matrix (RACI Matrix)|RACI matrix]], which describes different categories of responsibility assignment <ref name="gary"/>.

Find a source describing that project organization is bad

==== Project matrix organizations ====
* What can this tool/method do, and under what circumstances should it be applied?
* Is this tool/method a part of the current standards of project organization, or does it extend the current standards of project organization?

==== Project team organizations ====
* What can this tool/method do, and under what circumstances should it be applied?
* Is this tool/method a part of the current standards of project organization, or does it extend the current standards of project organization?

=== Project organization in an agile project management environment ===
In the modern business society characterized by rapid project execution, it can be difficult to develop a comprehensive project organization due to the lack of available information in the beginning of projects. Because of this continuously increasing uncertainty, it is beneficial to manage projects in an agile environment.

Despite that today's project management is heavily dominated by an agile approach, the traditional practice of project organization is still essential to achieve the desired objectives of a project. The informal approach of agile project management built on a dynamic and fluid approach experience difficulties without any implementation of traditional project management practices <ref name="kerzner"/>. Hence, even in an agile project management environment, establishing an efficient project organization creates a structured project management foundation. Consequently, the uncertainty related to responsibility and accountability is minimized as much as possible. Implementing this traditional project management practice will complement the agile approach by ensuring everyone knows their assigned responsibility. This makes more room for the project team to navigate smoothly in the agile project management environment and focus on the right things.

== Annotated bibliography ==
<ref name="PMI"/>

== References ==
<references>
<ref name="lock">D. Lock, ''Project Management. 10th edn.'', (Gower Published Limited, 2013), pp. 131–154.</ref>

<ref name="prince2">A. (2017). Managing successful projects with prince2 2017 edition. The Stationery Office Ltd.</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>

<ref name="kerzner">Kerzner, Harold. (2017). Project Management: A systems approach to planning, scheduling, and controlling - Section 11.8 and 8.12. 12th ed. Wiley.</ref>

<ref name="gary"> Gary L. Richardson and Brad M. Jackson. 2018. Project Management Theory and Practice - Section 17.1, Third Edition (3rd. ed.). Auerbach Publications, USA.</ref>

</references>

Project organization

2023-04-30T12:24:52Z

2023-02-12T07:10:20Z

Marcus chr:

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

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.

__TOC__

== 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?

=== Tool/method 1 ===
=== Tool/method 2 ===
=== 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.

=== Discussing Tool/method 1 ===
=== Discussing Tool/method 2 ===
=== Discussing Tool/method 3 ===

== Annotated bibliography ==

== References ==
* Project Management by Dennis Lock (2013).
* [https://ebookcentral.proquest.com/lib/dtudk/reader.action?docID=4863041] , A. (2017). Managing successful projects with prince2 2017 edition. The Stationery Office Ltd.
* 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 - 3.2 Create a Collaborative Project Team Environment. Project Management Institute, Inc. (PMI). Retrieved from
[https://app.knovel.com/hotlink/pdf/id:kt012LZF39/guide-project-management/create-collaborative]
* 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 - 2.2.1 Project Team Management and Leadership. Project Management Institute, Inc. (PMI). Retrieved from
[https://app.knovel.com/hotlink/pdf/id:kt012LZGJB/guide-project-management/project-team-management]