A pure matrix form of organization

 

A pure matrix form of organization is a type of organizational structure that combines elements of both functional and projectized structures. In a pure matrix, the project manager has full authority and responsibility over the project team, while functional managers retain control over the resources and technical expertise of their departments. This creates a balance between the centralized control of a functional structure and the decentralized control of a projectized structure.

Merits of a pure project organization structure include:

1. Greater focus: Projects are the primary focus, with teams dedicated to specific projects, allowing for a greater level of focus on project objectives and outcomes.

2. Faster decision-making: The project manager has the authority to make decisions without having to consult with multiple functional managers, leading to faster decision-making.

3. Improved communication: Communication channels are streamlined, leading to greater collaboration between team members.

4. Better resource utilization: Resources are allocated based on project needs, leading to better resource utilization.

5. Flexibility: Teams can be formed and disbanded quickly in response to changing project requirements.

However, there are also several potential drawbacks of a pure project organization structure, including:

1. Conflict: The dual authority structure can lead to conflicts between the project manager and functional managers over resource allocation and priorities.

2. Lack of continuity: Team members may be reassigned to different projects after completing one, leading to a lack of continuity and potential loss of expertise.

3. High costs: Maintaining a dedicated project team can be expensive, particularly if there are frequent changes in project requirements.

4. Overemphasis on project objectives: Functional managers may be less focused on long-term strategic objectives if they are primarily focused on meeting the needs of individual projects.

5. Limited career paths: Career paths may be limited for employees who are primarily focused on project work, as they may lack exposure to other functional areas.

Overall, a pure project organization structure may be suitable for organizations that prioritize project outcomes and require a high degree of flexibility and responsiveness. However, it is important to carefully consider the potential drawbacks before adopting this structure.

Organizational culture

Organizational culture refers to the shared values, beliefs, customs, behaviors, and practices that characterize an organization. It is the "personality" of an organization and is reflected in the way employees interact with each other, customers, and other stakeholders. Here are some of the key aspects of organizational culture:

1. Values: These are the guiding principles and beliefs that an organization follows. Values may include things like innovation, customer focus, teamwork, or ethical behavior.

2. Beliefs: These are the assumptions and perceptions that people hold about the organization and its goals, processes, and outcomes.

3. Norms: These are the unwritten rules and expectations that govern behavior within an organization. Norms may include things like dress code, work hours, communication style, and decision-making processes.

4. Symbols: These are the physical or tangible representations of an organization's culture, such as logos, slogans, office layout, and artwork.

5. Rituals: These are the formal or informal events or activities that reinforce an organization's culture, such as staff meetings, recognition ceremonies, and social events.

6. Language: This refers to the vocabulary and jargon used within an organization, which reflects its values, beliefs, and norms.

7. Stories: These are the anecdotes, legends, and myths that circulate within an organization, which illustrate its values and beliefs.

8. Attitudes: These are the emotions, feelings, and opinions that employees hold about the organization, its leaders, and its practices.

Organizational culture can have a significant impact on employee morale, job satisfaction, and performance, as well as on the success or failure of the organization itself. It is therefore important for leaders to be aware of and actively manage their organization's culture. 

Work Breakdown Structure (WBS)

Work Breakdown Structure (WBS) is a hierarchical decomposition of the work to be executed by the project team in order to accomplish the project objectives and deliverables. It is a visual tool that helps to organize and define the scope of the project, and break down complex tasks into smaller, more manageable pieces.

In this example, the project is building a house. The WBS is broken down into several main components: Planning, Design, Construction, Testing and Commissioning, and Project Closure. Each of these components is further divided into smaller, more specific tasks or sub-components. For instance, under the Planning component, there are several tasks such as defining project scope, identifying key stakeholders, developing project schedule, determining project budget, and obtaining necessary permits and approvals. Similarly, the Construction component is broken down.

Question bank

 Project definition:

1. Knowledge: What are the components of a project charter?
2. Comprehension: How do feasibility studies impact project viability?
3. Application: Can you provide an example of a project requirement and constraint?
4. Analysis: How can identifying stakeholders influence project planning?
5. Synthesis: How would you develop a high-level project plan for a complex project?
6. Evaluation: How can you determine if a project objective is achievable?

Cost and time estimates for projects:

1. Knowledge: What factors are included in project cost estimates?
2. Comprehension: How do you validate project estimates with stakeholders?
3. Application: Can you estimate the cost of a project task using a given resource requirement?
4. Analysis: How do changing resource requirements impact project costs?
5. Synthesis: How would you create a detailed project budget for a large project?
6. Evaluation: How do you know if a project estimate is accurate?

Process of developing a project plan:

1. Knowledge: What are the components of a project plan?
2. Comprehension: How are project objectives and scope defined?
3. Application: Can you identify the milestones for a project?
4. Analysis: How do you sequence project tasks to create a logical order?
5. Synthesis: How would you assign tasks and responsibilities to project team members?
6. Evaluation: How can you determine if a project plan is realistic?

Activity on node analysis:

1. Knowledge: What is an activity on node diagram?
2. Comprehension: How is the critical path identified in an AON diagram?
3. Application: Can you create an AON diagram for a simple project?
4. Analysis: How do you determine the duration of a project task using an AON diagram?
5. Synthesis: How would you use an AON diagram to identify potential project risks?
6. Evaluation: How can you determine if a project is on track using an AON diagram?

Practical issues in project planning:

1. Knowledge: What are some common practical issues in project planning?
2. Comprehension: How can project scope changes impact project timelines?
3. Application: Can you provide an example of a project risk and how it could be managed?
4. Analysis: How do you balance project time, cost, and quality constraints?
5. Synthesis: How would you create a project communication plan?
6. Evaluation: How can you assess the social responsibility of a project?

Steps in project definition. Cost and time estimates for projects. Process of developing a project plan. Activity on node analysis. Practical issues in project planning.

 Project definition:

1. Identify the project objective, scope, and deliverables
2. Identify stakeholders and project team members
3. Develop a project charter and gain approval from stakeholders
4. Conduct a feasibility study to determine the project's viability
5. Define project requirements and constraints
6. Develop a high-level project plan, including timelines and budgets

Cost and time estimates for projects:

1. Identify project activities and their associated costs and time requirements
2. Estimate resource requirements and costs, including personnel, equipment, materials, and overhead
3. Develop a project budget and schedule based on the estimated costs and time requirements
4. Review and validate the estimates with stakeholders and project team members
5. Update the estimates throughout the project lifecycle as necessary

Process of developing a project plan:

1. Define project objectives and scope
2. Identify project deliverables and milestones
3. Break down the project into smaller tasks and activities
4. Sequence the tasks and activities in a logical order
5. Estimate the time and resources required for each task and activity
6. Assign tasks and responsibilities to project team members
7. Develop a project schedule and budget
8. Review and refine the plan with stakeholders and project team members

Activity on node analysis: Activity on node (AON) is a project management technique that involves representing project tasks and their dependencies as nodes on a network diagram. The AON diagram shows the critical path, which is the sequence of tasks that must be completed on time for the project to be completed on schedule. AON analysis helps project managers identify potential bottlenecks and delays in the project schedule and make informed decisions to mitigate risks.

Practical issues in project planning:

1. Managing project scope and changes
2. Identifying and managing project risks
3. Ensuring adequate resources are available for the project
4. Balancing project time, cost, and quality constraints
5. Communicating with stakeholders and project team members effectively
6. Managing project documentation and reporting
7. Ensuring compliance with regulations and standards
8. Addressing ethical considerations and social responsibility.

Functional organization structure

Functional organization is a type of project management structure where employees are organized based on their areas of expertise, and they work within their respective departments. Here are some advantages and disadvantages of a functional organization:

Advantages:

1. Expertise: Employees have specialized skills and expertise in their respective fields, which enables them to provide high-quality work.
2. Efficient resource allocation: Resources are allocated efficiently since employees are already grouped by department and can easily be assigned to work on different projects.
3. Clear career paths: Employees have clear career paths and can easily advance within their respective departments.
4. Better communication: Communication within departments is often better since employees work closely with others in their department on a daily basis.
5. Reduced duplication: Resources and skills are not duplicated since each department is responsible for specific tasks.

Disadvantages:

1. Limited flexibility: The structure can be inflexible and slow to adapt to changing requirements or priorities.
2. Lack of collaboration: Communication and collaboration between departments may be limited, which can lead to a lack of cooperation and coordination.
3. Silo mentality: Departments may become silos and focus solely on their own objectives, rather than the objectives of the project as a whole.
4. Limited accountability: There may be limited accountability since project managers have limited authority over resources, and functional managers may not be held accountable for project outcomes.
5. Duplication of resources: Resources may be duplicated if multiple projects require the same skills or expertise, leading to unnecessary costs.

Overall, a functional organization structure can work well for projects that require specialized expertise and have a clear scope of work. However, it may not be suitable for projects that require a high degree of collaboration and flexibility or where a project manager needs to have greater control over resources. 

                                            CEO/Top Management

                                                        |

               .---------------------- ---------------------------------------------------

               |                                        |                                                        |

          Finance                        Operations                                      Human Resources

               |                                        |                                                        |

          Accounting                     Production                             Employee Relations

               |                                      |                                                           |

           Budgeting               Quality Control                        Compensation & Benefits