Professional Documents
Culture Documents
Ch. 4 Project Organization
Ch. 4 Project Organization
Ch. 4 Project Organization
PROJECT ORGANIZATION
When projects are initiated then the first decision to be made is how to tie the project to parent organization. Project
manager usually has no influence over the interface between the organization and the project but senior management does.
PM’s work is however strongly affected by the project’s structure, and the PM should understand it’s working.
1. Policies of the organization can get violated. PM has the authority to make his own policies with respect to
project.
2. Staff and equipment shortages in case of multiple pure projects
3. Low efficiency of utilization of resources.
4. Skilled staff not available for routine work
5. For long term pure projects, the project team members get left behind in the technology of their respective
departments.
6. There is anxiety among project team members, what would happen after the project finishes.
7. For long term projects the project team members often get overlooked for promotion.
Disadvantages
The Project Manager in this case usually reports to program manager who also exercises supervision over other projects.
See Figure below
Here as we see in the figure above, several different projects are run at the same time for an organization. Each project has
its respective project manager and its designated team members from each department (just like a pure project). But as we
see in the diagram above each of the projects are interconnected, which means that the respective team members can be
shifted to other projects or to the routine work if they have less work in their respective project.
Each project team member would work in his respective project as first priority. When there is less or no work in his
project for the person then the respective functional manager would shift him to another project which has work for him, or
to the routine work. So for each of the team members of all the projects there are two bosses at the same authority level,
which creates the biggest conflict of authority. This is the only big disadvantage in Matrix projects, which can be resolved
by making certain rules.
1. Project manager has full authority over his project team, i.e. unity of command.
2. Project takes labor and talent of all departments temporarily.
3. Maximum efficiency of utilization of resources of all the departments.
4. Moderate mental concentration.
5. Several projects can run concurrently, efficiently.
6. Less anxiety when the project will finish
7. Focus on client and project
8. No violation of organizational policies
9. Better use of resources by several projects.
10. Normal path of advancement of careers
11. No chances of anybody leaving behind in technology of their parent departments.
1. The biggest disadvantage is that there are two bosses i.e. the PM and the FM, at the same level of authority,
creates conflict of authority.
2. The movement of resources between different projects foster infighting among several PMs, focusing on their
respective projects.
The following key members will be needed plus an appropriate no. of scientists, engineers, technicians, clerks and the
like.
1. Project Engineer :- Incharge of product design and development
2. Manufacturing Engineer :- Efficient production of the process
3. Field manager :- Installation, testing, support
4. Contract Administrator :- Official paperwork, contracts
5. Project Controller :- Keeps daily account of budgets, costs, supplies etc
6. Support Service manager :- Incharge of product support, subcontractors
The Project Engineer and Product Controller report directly to PM to have control of tech performance and budget.