๐ Lecture 4 โ Project Management Methodologies and Organizational Structures
๐ Overview: This lecture explores the fundamental distinction between project-driven and non-project-driven organizations, the historical evolution of project management methodologies through key "allies," and the hierarchical relationship between systems, programs, and projects. It also provides a comprehensive analysis of various organizational structuresโtraditional, line-staff, pure product, and matrix formsโalong with their advantages, disadvantages, and criteria for selection.
๐๏ธ Topics Covered
The lecture covers project-driven versus non-project-driven organizations and their characteristics; the historical development of project management methodologies from 1985 to 2000; definitions and relationships among systems, programs, and projects; four categories of projects; differences between product and project management; concepts of maturity and excellence in project management; informal project management principles; and a detailed examination of organizational structures including traditional, line-staff, pure product, and matrix forms with their modifications and selection criteria.
๐ Lecture Summary
Project driven versus Non โ project driven organizations
In a project-driven organization such as construction or aerospace, all work is characterized through projects, with each project as a separate cost center having its own profit-and-loss statement. The total profit to the corporation is the summation of the profits on all projects. In a non-project-driven organization such as low technology manufacturing, profit and loss is measured on vertical or functional lines, and projects exist merely to support product lines or functional lines.
Project management in non-project-driven organizations is generally more difficult because projects may be few and far between, not all projects have the same requirements, executives refuse to delegate authority, projects are delayed due to vertical chain of command, staffing is on a "local" basis, and there is heavy dependence on subcontractors. Non-project-driven organizations may have a steady stream of projects designed to enhance manufacturing operations, but if changes are not identified as specific projects, the result can be poorly defined responsibility areas, poor communications, slow implementation, lack of cost tracking, and poorly defined performance criteria.
Figure 4.1 shows the tip-of-the-iceberg syndrome, which is most common in non-project-driven organizations. On the surface, we see a lack of authority for the project manager, but beneath the surface lies excessive meddling due to lack of understanding of project management resulting from failure to recognize the need for proper training. Informal project management most often appears in non-project-driven organizations. Most firms that believed they were non-project-driven were actually hybridsโnon-project-driven firms with one or two divisions that are project-driven.
Project Management Methodologies
The recession of 1989โ1993 saw the growth of project management in the non-project-driven sector. Key allies for project management appeared:
- 1985: Companies recognized they must compete on quality as well as cost. The first ally surfaced with the "marriage" of project management and Total Quality Management (TQM).
- 1990: Companies recognized the importance of schedule compression and being first to market. Concurrent engineering promoted project management for better scheduling.
- 1991โ1992: Executives realized project management works best if decision-making and authority are decentralized, and control can be achieved by functioning as project sponsors.
- 1993: Companies began "re-engineering," eliminating organizational "fat." People were asked to do more work in less timeโa benefit of project management.
- 1994: A good project cost control system (horizontal accounting) allows improved estimating and firmer grasp of real costs.
- 1995: Few projects were completed within original objectives without scope changes. Methodologies were created for effective change management.
- 1996: Risk management plans were now included in project plans.
- 1997-1998: Recognition of project management as a professional career path mandated consolidation of knowledge and a centrally located project management group.
- 1999: Concurrent engineering and rapid product development required dedicated resources. The cost of over-management may be negligible compared to risks of under-management.
- 2000: Mergers and acquisitions created more multinational companies; multinational project management became the major challenge.
The reason for early resistance was that project management was customer-driven rather than internally driven. By 1995, project management became internally driven and a necessity for survival.
Systems, Programs, and Projects
4.3.1 Systems: A system is defined as: A group of elements, either human or nonhuman, that is organized and arranged in such a way that the elements can act as a whole toward achieving some common goal, objective, or end. Systems are collections of interacting subsystems that can provide synergistic output. Systems are characterized by their boundaries or interface conditions. A close system exists when the business firm system is completely isolated from the environmental system, giving management complete control. An open system reacts with the environment and must have permeable boundaries.
๐ Definition โ System: A group of elements, either human or nonhuman, organized and arranged so the elements can act as a whole toward achieving some common goal, objective, or end.
4.3.2 Programs: Programs are the necessary first-level elements of a system. Air Force definition: The integrated, time-phased tasks necessary to accomplish a particular purpose. NASA definition: A relative series of undertakings that continue over a period of time (normally years) designed to accomplish a broad scientific or technical goal. Programs are generally defined as time-phased efforts, whereas systems exist on a continuous basis.
4.3.3 Projects: Projects are time-phased efforts (much shorter than programs) and are the first level of breakdown of a program. NASA/Air Force definition: A project is within a program as an undertaking that has a scheduled beginning and end, and that normally involves some primary purpose.
Categories of Projects
There are four categories of projects:
- Individual projects: Short-duration projects assigned to a single individual who may act as both project manager and functional manager.
- Staff projects: Projects that can be accomplished by one organizational unit, such as a department.
- Special projects: Projects requiring certain primary functions and/or authority to be assigned temporarily to other individuals or units. Works best for short-duration projects.
- Matrix or Aggregate projects: Require input from a large number of functional units and usually control vast resources.
Project management is defined as the process of achieving project objectives through the traditional organizational structure and over the specialties of the individuals concerned. A project manager must: set objectives, establish plans, organize resources, provide staffing, set up controls, issue directives, motivate personnel, apply innovation for alternative actions, and remain flexible.
Product versus Project Management
There is no basic difference between program management and project management. However, the project manager focuses on the end date of the project, whereas the product manager is not willing to admit that the product line will ever end and seeks spin-offs to keep the product alive. When the project is in the Research and Development (R&D) phase, a project manager is involved. Once developed and introduced to the marketplace, control is taken over by the product manager.
Maturity and Excellence
Maturity in project management is defined as: The implementation of a standard methodology and accompanying processes, in such a way that ensures a high likelihood of repeated successes. Maturity implies the proper foundation of tools, techniques, processes, and culture exists. Debriefing with senior management reviews key performance indicators.
Excellence is defined as: An environment in which there exists a continuous stream of successfully managed projects where success is measured by what is in the best interest of both the company and the customer. Excellence goes well beyond maturityโit may take two years or more to reach initial levels of maturity, and an additional five years or more to achieve excellence.
Informal Project Management
Companies today manage projects more on an informal basis, which emphasizes managing with a minimum amount of paperwork while maintaining a reasonable degree of formality. Informal project management is based upon guidelines rather than policies and procedures. It mandates: effective communications, effective cooperation, effective teamwork, and trust. Not all companies have the luxury of using informal project management; customers often have a strong voice in whether formal or informal project management will be used.
Organizational Structures
Management has realized organizations must be dynamicโcapable of rapid restructuring if environmental conditions dictate. Wallace identified four major factors causing the organizational revolution: the technology revolution, competition and the profit squeeze, the high cost of marketing, and the unpredictability of consumer demands.
According to Grinnell and Apple, five indications that traditional structure may not be adequate: management is satisfied with technical skills but projects are not meeting requirements; high commitment but great fluctuations in performance; talented specialists feel exploited; groups constantly blame each other; projects are on time but groups are not satisfied.
4.8.1 Traditional (Classical) Organization: The traditional management structure survived for more than two centuries. Companies could survive with only one or two product lines fifty years ago. However, survival depended on multiple product lines and integration of technology. Managers searched for innovative organizational forms to alleviate integration and conflict problems.
Table 4.1: Advantages of traditional/classical organization:
- Clear authority structure
- Clear responsibility
- Clear chain of command
- Specialization promotes efficiency
- Simple cost tracking
Table 4.2: Disadvantages of traditional/classical organization:
- No single point of responsibility for projects
- Poor coordination across functions
- Slow response to project needs
- Conflicts between functional priorities
- Difficulty in integrating efforts
4.8.2 Line-Staff Organization (Project Coordinator): Control of a project must be given to personnel whose first loyalty is toward completion of the project. The project manager serves as the focal point for activity controlโa center for information. The prime responsibility is to keep the division manager informed of the project status and influence managers to complete activities on time. Serious problems arose regarding how much authority to give the project manager.
4.8.3 Pure Product (Projectized) Organization: The pure product organization develops as a division within a division. One individualโthe program managerโmaintains complete line authority over the entire project, assigns work, and conducts merit reviews. Each individual reports to only one person, creating strong communication channels and rapid reaction time.
Table 4.3: Advantages of Projectized organization:
- Complete authority for project manager
- Single point of responsibility
- Rapid communication and decision making
- Strong customer focus
- Team identity and loyalty
Table 4.4: Disadvantages of Projectized organization:
- Duplication of resources across projects
- Less technical depth in specialties
- Uncertainty about career path
- Anxiety about project completion
- Less efficient use of personnel
4.8.4 Matrix Organizational Form: The matrix organizational form combines advantages of pure functional structure and product organizational structure. Each project manager reports directly to the vice president and general manager. Since each project represents a potential profit center, the project manager has total responsibility and accountability for project success. Functional departments maintain functional responsibility to ensure technical excellence.
Project management is a "coordinative" function, whereas matrix management is a collaborative function. In the coordinative organization, work is assigned to specific people who "do their own thing." In the collaborative organization, information sharing may be mandatory, and several people may be required for the same work.
Ground rules for matrix development:
- Participants must spend full time on the project
- Horizontal and vertical channels must exist for commitments
- Quick and effective methods for conflict resolution
- Good communication channels and free access between managers
- All managers must have input into planning
- Both horizontally and vertically oriented managers must negotiate for resources
- Horizontal line must operate as separate entity except for administrative purposes
Table 4.5: Advantages of Matrix organization:
- Efficient use of resources across projects
- Technical excellence maintained
- Flexibility in staffing
- Balance between project and functional goals
- Information sharing across functions
Table 4.6: Disadvantages of Matrix organization:
- Dual reporting creates confusion
- Conflict between project and functional managers
- Power struggles over resources
- Time-consuming decision making
- Requires excellent communication and negotiation skills
4.8.4.1 Modification of Matrix Structures: Three common varieties of matrix structure exist, each representing different degrees of authority for the program manager. The weak matrix gives more authority to functional managers. The balanced matrix shares authority between project and functional managers. The strong matrix gives more authority to the project manager. As companies grew, a new positionโdirector of programs or manager of programsโwas created to free the general manager from daily monitoring of all programs.
The desired span of control varies by company and must consider: task complexity, available technology, external environment, organizational membership needs, and types of customers/products.
Selecting the Organizational Form
The project management approach can be effectively applied to a one-time undertaking that is: definable in terms of a specific goal, infrequent or unique to the organization, complex with interdependent tasks, and critical to the company.
Basic factors influencing selection of a project organizational form:
- Project size
- Project length
- Experience with project management organization
- Philosophy and visibility of upper-level management
- Project location
- Available resources
- Unique aspects of the project
Project management works best for labor-intensive projects rather than capital-intensive projects. Four fundamental parameters must be analyzed: integrating devices, authority structure, influence distribution, and information system.
๐ก Why this matters: The choice of organizational structure directly impacts project success, resource utilization, communication effectiveness, and conflict resolution. Understanding which form to use based on project characteristics is essential for effective project management.
โญ Key Takeaways
The distinction between project-driven and non-project-driven organizations critically affects how project management is implemented, with non-project-driven organizations facing more difficulties including lack of authority, poor understanding, and resistance to delegation. The evolution of project management methodologies from 1985-2000 was driven by key allies including TQM, concurrent engineering, and re-engineering, transforming project management from customer-driven to internally driven necessity. The hierarchy of systems, programs, and projects establishes clear relationships where systems are continuous collections of subsystems, programs are time-phased efforts, and projects are shorter undertakings within programs. Organizational structures range from traditional/classical to matrix forms, each with distinct advantages and disadvantagesโmatrix organizations combine functional and product benefits but require excellent communication and conflict resolution skills. Project maturity requires standardized methodology for repeated success, while excellence requires an additional five years or more and creates an environment of continuous successful projects serving both company and customer interests.
๐ง Quick Revision Questions
- What are the key differences between project-driven and non-project-driven organizations, and why is project management more difficult in non-project-driven organizations?
- List the major "allies" for project management that emerged between 1985 and 2000, and explain how each contributed to project management's growth.
- What is the difference between a system, a program, and a project? Provide definitions for each.
- Compare and contrast the traditional/classical organization, pure product organization, and matrix organizational formโwhat are the advantages and disadvantages of each?
- What is the "tip-of-the-iceberg syndrome" in matrix implementations, and why is it most common in non-project-driven organizations?
๐ Lecture 5 โ PROJECT LIFE CYCLES
๐ Overview: This lecture defines and explains the concept of life cycles as applied to products, systems, and projects. It details the distinct phases of each type of life cycle, explores system costs and cost-benefit analysis, and introduces the roles of the Project Management Office and the Project Management Officer, differentiating them from the traditional Project Manager.
๐๏ธ Topics Covered
This lecture covers the life cycle phases of a product and a system, including detailed explanations of conceptual, planning, testing, implementation, and closure phases. It delves into system costs and cost-benefit analysis, then examines the characteristics of the project life cycle. The lecture also introduces the Project Management Office and the Project Management Officer, highlighting key differences between a Project Manager and a Project Management Officer, and concludes with several examples of project life cycles (house, computer installation, engineering, nuclear power station).
๐ Lecture Summary
5.1 Life Cycle Phases of a Product
Every program, project, or product has certain phases of development known as life-cycle phases. A clear understanding of these phases permits managers to better control total corporate resources. For a product, these phases include: Research and development, Market introduction, Growth, Maturity, Deterioration, and Death. There is no universal agreement on the life cycle phases of a project due to the complex nature and diversity of projects.
5.2 Life Cycle Phases of a System
The theoretical definitions of the life cycle phases of a system can be applied to a project. These phases include: Conceptual, Planning, Testing, Implementation, and Closure.
5.2.1 Conceptual Phase
This first phase includes the preliminary evaluation of an idea. The most important aspect is a preliminary analysis of risk and its impact on time, cost, and performance requirements, along with the potential impact on company resources. This phase also includes a "first cut" at the feasibility of the effort.
5.2.2 Planning Phase
The second phase is a refinement of the elements described in the conceptual phase. It requires a firm identification of resources and the establishment of realistic time, cost, and performance parameters. This phase also includes the initial preparation of all documentation necessary to support the system. For a competitive bid project, the planning phase includes developing the total bid package (time, schedule, cost, and performance).
5.2.2.1 System Costs
During the conceptual and planning phases, analyzing system costs is not an easy task. Most project costs are broken down into operating (recurring) costs, such as manpower, and implementation (nonrecurring) costs, such as construction of a new facility. Operating costs may be reduced if personnel perform at a higher position on the learning curve. The identification of a learning curve position is vitally important during the planning phase.
๐ Definition โ Learning Curve: A concept that shows a reduction in recurring costs as workers become more efficient with experience.
5.2.2.2 Cost Benefit Analysis
Once the approximate total cost is determined, a cost-benefit analysis should be conducted to determine if the estimated value of the information obtained from the system exceeds the cost of obtaining it. This analysis is often part of a feasibility study. Top-management approval is almost always necessary before initiating such a study.
5.2.3 Testing Phase
The third phase is predominantly a testing and final standardization effort so that operations can begin. Almost all documentation must be completed in this phase.
5.2.4 Implementation Phase
The fourth phase integrates the project's product or services into the existing organization. If the project was for a marketable product, this phase could include the product life cycle phases of market introduction, growth, maturity, and a portion of deterioration.
5.2.5 Closure Phase
The final phase includes the reallocation of resources. The closure phase evaluates the efforts on the total system and serves as input to the conceptual phases for new projects and systems. This final phase also has an impact on other ongoing projects regarding priority identification. Large projects require full-time staffs, while small projects may require only part-time people, implying an individual can be responsible for multiple projects.
Questions for multi-project management include:
- Are the project objectives the same?
- Is there a distinction between large and small projects?
- How do we handle conflicting priorities?
5.2.6 Explanation of Various Life Cycle Phases
The phases of a project and those of a product are compared; product life cycles generally do not overlap, whereas project phases can and often do overlap. Different industries have different definitions for life cycle phases. For computer programming, life cycle phases show how manpower resources build up and decline during a project. Most executives prefer short data processing life cycles because computer technology changes rapidly. Top management is responsible for the periodic review of major projects at the completion of each life cycle phase.
Reasons for companies using procedural manuals for project life cycles include:
- A clear description of the work may be possible.
- Pricing and estimating may be easier.
- Key decision points exist for incremental funding.
Not all projects can be simply transposed into life cycle phases (e.g., Research and Development).
5.3 Characteristics of Project Life Cycle
- The project life cycle defines phases that connect the beginning and end of a project.
- Phases can be overlapped for fast tracking to compress the schedule.
- There is no ideal way to define a Project Life Cycle; only three phases are always certain: conceptualization, intermediate phase(s), and closure.
- Phases are generally defined in sequential order, and cost and staffing levels are defined for each phase.
- A project may have sub-projects, and sub-projects may have their own project life cycle.
- In the beginning of a project, the level of uncertainty and risk is always high.
- The typical project life cycle has critical decision points where the project may continue, be changed, or be abandoned.
- A Community of Professionals (COPs) may provide support and guidance at many points within the project life cycle.
- During project close, reassignment and intelligent preservation of resources and sharing lessons learned are facilitated.
๐ก Why this matters: Understanding the inherent uncertainty at the start of a project and the flexibility of life cycle definitions helps managers plan for risk and adapt their management approach effectively.
5.4 Project Management Office
The Project Management Office (PMO) sets project standards and oversees the organizationโs portfolio of projects. This allows the organization to evaluate the use of resources across all projects and resolve conflicts. The PMO is also a good place to examine how communities are linked across projects. Using communities for knowledge transfer is efficient because:
- Evaluation of knowledge is done by a broader range of people.
- Communities exist outside the project framework and trust is already established.
- They can be used instead of more formal structures.
- Knowledge is transferred from expert to recipient, including tacit knowledge.
- Community transfer shares knowledge broadly, strengthening the entire organization.
The PMO and top management are responsible for the periodic review of major projects at the completion of each life cycle phase.
5.5 Project Management Officer (PMO)
A Project Management Officer (PMO) centralizes and coordinates the management of projects under his/her domain. The PMO focuses on coordination planning, prioritization of all resources, and deliverables of projects and sub-projects. The PMO is responsible for keeping top management and clients informed about all running projects or the product life cycle.
The PMO is generally responsible for:
- Providing a monitoring platform for the Project Manager.
- Identifying the Project Management Methodology and best practices.
- Acting as a clearing house for defining project policies, procedures, and templates.
- Configuration management for all projects.
- Developing a repository and risk management for projects.
- Developing and maintaining tools for project management (e.g., Enterprise Wide Project Management Software).
- Management, coordination, and monitoring of communications, timelines, budget, and quality standards.
- The PMO may have the authority to terminate a project anytime.
5.6 Difference Between Project Manager and Project Management Officer
- Both have different objectives, driven by different requirements aligned with strategic needs.
- Project Manager is responsible for delivering specific project objectives within constraints, while Project Management Officer is responsible for organizational structure-specific mandates with a much broader perspective.
- Project Manager focuses on project objectives; Project Management Officer focuses on major programs, scope, and changes required.
- Project Manager is constrained with assigned resources for a specific project; Project Management Officer is supposed to optimize the use of shared organizational resources across all projects.
- Project Manager manages scope, schedule, cost, and quality of a product; Project Management Officer manages overall risk, opportunities, interdependencies, and links among different projects.
- Project Manager reports on project-specific progress; Project Management Officer provides consolidated reporting/enterprise view of all running projects.
5.7 Some Examples of Project Life Cycle
There are many variations on project phases, influenced by the projectโs scope of work. The project life cycle is often represented by a bar chart indicating the duration and overlap of each phase.
5.7.1 House Project: A simple subdivision into four phases. The level of effort follows a typical profile, increasing during the building phase and declining during the interior phase. 5.7.2 Computer Installation: The training phase overlaps with both system selection and the implementation phase. 5.7.3 Engineering Project: All phases overlap, which could indicate fast tracking. 5.7.4 Nuclear Power Station Project: This project may span 50 years. The environmental constraints have changed significantly between the design and decommissioning phases.
โญ Key Takeaways
A projectโs life cycle, consisting of conceptual, planning, testing, implementation, and closure phases, provides a structured framework for management. The closure phase is critical for resource reallocation and feeding lessons learned into new projects, ensuring organizational survival. The Project Management Office and Project Management Officer play a strategic, organization-wide role, distinct from the project-specific focus of a Project Manager, by optimizing resources and managing interdependencies across the entire portfolio of projects.
๐ง Quick Revision Questions
- What are the five life cycle phases of a system, and how are they applied to a project?
- What are the two main categories of system costs, and how does the "learning curve" impact operating costs?
- List at least three characteristics of a project life cycle, including one about risk and one about phase overlap.
- What are the primary responsibilities of a Project Management Office and a Project Management Officer?
- Describe two key differences between the role of a Project Manager and the role of a Project Management Officer.
๐ Lecture 06 โ The Project Manager
๐ Overview: This lecture examines the comprehensive skill set required for effective project management, distinguishing between the roles of Project Managers and Functional Managers. It covers the selection process for Project Managers, their typical duties and job descriptions, and the evolving skills needed for next-generation Project Managers in the 21st century.
๐๏ธ Topics Covered
The lecture begins by identifying and explaining ten specific skill requirements for Project Managers, including team building, leadership, conflict resolution, and technical expertise. It then contrasts the role of the Functional Manager versus the Project Manager, discusses the selection process for Project Managers, and outlines typical duties across planning, organizing, directing, and controlling functions. Finally, it addresses the changing skill demands for next-generation Project Managers and provides a table of methods for developing these professionals.
๐ Lecture Summary
6.1 Skill Requirements for Project Managers:
Projects are often complex and multifaceted, requiring skills in team building, leadership, conflict resolution, technical expertise, planning, organization, entrepreneurship, administration, management support, and resource allocation. A key factor for good project performance is the Project Manager's ability to integrate personnel from many disciplines into an effective work team. The Project Manager must relate to the people to be managed, the task to be done, the tools available, the organizational structure, and the organizational environment. Ten specific skills are identified and discussed in this section.
-
Team Building Skills: Building the project team is a prime responsibility of the Project Manager. It involves a spectrum of skills to identify, commit, and integrate various task groups from the traditional functional organization into a single Project Management system. The Project Manager must nurture a climate with committed team members, good interpersonal relations, clearly defined goals, and open communication. Three major considerations for integration are effective communication, sincere interest in professional growth, and commitment to the project.
-
Leadership Skills: An essential prerequisite for project success is the Project Manager's ability to lead the team within a relatively unstructured environment, often dealing with managers across functional lines with little or no formal authority. It involves information processing skills, the ability to integrate individual demands into decisions, and the ability to resolve inter-group conflicts. Quality leadership depends heavily on the Project Manager's personal experience and credibility within the organization. Personal traits supporting these skills include flexibility, innovative thinking, initiative, and charisma.
-
Conflict Resolution Skills: Conflict is fundamental to complex task management and is often determined by the interplay of the project organization and the larger host organization. Understanding the determinants of conflict is important for the Project Manager's ability to deal with conflicts effectively. When dysfunctional, conflict can result in poor decision making and disruption of team efforts. However, conflict can be beneficial when it produces involvement and enhances the competitive spirit. Project Managers must understand organizational and behavioral elements, communicate effectively, and recognize the determinants of conflict and their timing in the project life cycle.
-
Technical Skills: The Project Manager rarely has all the technical, administrative, and marketing expertise but must understand the technology, markets, and business environment to participate effectively in integrated solutions. Without this understanding, the integrated consequences of local decisions cannot be foreseen. Technical expertise is necessary to evaluate technical concepts, communicate effectively in technical terms, and make trade-offs between cost, schedule, and technical issues. This is why many project managers have an engineering background.
-
Planning Skills: Planning skills are absolutely essential for the successful management of large complex projects, as the project plan is the roadmap defining how to get from start to final results. Project planning is an ongoing activity, and preparation of the project summary plan is the responsibility of the Project Manager. Effective planning requires skills in information processing, communication, resource negotiations, and securing commitments. The Project Manager must also assure that the plan remains a viable document throughout the project life cycle and avoid over-planning where it becomes a poor substitute for innovative work.
-
Organizational Skills: The Project Manager must be a social architect, understanding how the organization works and how to work with it. Organizational skills are important during project formation and startup when establishing the project organization by integrating people from different disciplines. This requires defining reporting relationships, responsibilities, lines of control, and information needs. A good project plan and task matrix are useful organizational tools.
-
Entrepreneurial Skills: The Project Manager needs a general management perspective, considering economic considerations and broader objectives beyond profits, such as customer satisfaction and future growth. Entrepreneurial skills are developed through actual experience, but formal training like MBA programs, special seminars, and cross-functional training can help develop these skills.
-
Administrative Skills: These skills are essential, requiring experience in planning, staffing, budgeting, scheduling, and control techniques. The problem with technical personnel is not making them understand administrative techniques but impressing that costs and schedules are as important as technical solutions. For larger projects, managers may need to delegate administrative tasks to support groups or hire a project administrator. Helpful tools include the meeting, the report, the review, and budget and schedule controls.
-
Management Support Building Skills: The Project Manager is surrounded by organizations that either support them or control activities. Understanding these interfaces enhances the ability to build favorable relationships with senior management, which is often an absolute necessity for dealing effectively with interface groups. Four key variables influence this ability: ongoing credibility, visibility of the project, priority of the project, and own accessibility.
-
Resource Allocation Skills: A project organization has many bosses, and functional lines often shield support organizations from direct financial control by the project office. Once a task is authorized, it is often impossible to control personnel assignments and costs. Effective and detailed project planning may facilitate commitment and reinforce control. The "Statement of Work" establishes a basis for resource allocation, and specific agreements with key contributors on tasks, budgets, and schedules are important.
6.2 Functional Manager versus Project Manager:
Assuming the Project and Functional Manager are not the same person, specific roles are identified. The Functional Manager has the responsibility to define how the task will be done and where, provide sufficient resources, and is responsible for the deliverable. The major responsibility of the Project Manager is planning. The Project Manager must provide complete task definitions, resource requirement definitions, major timetable milestones, definition of end item quality requirements, and the basis for performance measurement. These factors result in assurance that functional units understand their responsibilities and that problems are identified beforehand. Project Managers are responsible for project administration and have the right to establish their own policies, procedures, and guidelines, provided they conform to overall company policy.
6.3 Selecting the Project Manager:
Selecting a Project Manager is a difficult decision for upper management, as some managers work best on long-duration projects while others thrive on short-duration ones. Executives cannot always go with seasoned veterans without frustrating younger personnel. Project Manager selection is a general management responsibility because the Project Manager cuts across organizational lines, project management will not succeed without good Project Managers, and they are more likely to accomplish goals if it's obvious they were selected by management. Five basic questions must be considered: sources, selection method, career development, skill development, and performance evaluation.
๐ Definition โ General Management Responsibility: The duty of upper-level management to select and appoint Project Managers, delegating authority to cut across organizational lines and signaling support to subordinates.
๐ Formula: Good Project Manager Selection = [General Management Responsibility] + [Delegated Authority] + [Apparent Support]
6.5 Duties and Job Descriptions:
Job descriptions for Project Managers vary by company and project. The lecture lists duties for a Project Manager in the construction industry across four functions:
6.5.1 Planning:
The Project Manager must become completely familiar with contract documents, develop the basic plan for executing and controlling the project, direct preparation of project procedures, budget, schedule, and design criteria, and review plans periodically, instituting changes if necessary.
6.5.2 Organizing:
The Project Manager develops the organization chart for the project, reviews position descriptions, participates in selecting key supervisors, develops manpower requirements, and continually reviews the organization and recommends changes in structure and personnel if necessary.
6.5.3 Directing:
The Project Manager directs all work required to meet contract obligations, develops a system for decision making, promotes growth of key supervisors, establishes objectives and performance goals, fosters team spirit, assists in resolving differences or problems, and anticipates and minimizes potential problems by maintaining current knowledge of overall project status.
6.5.4 Controlling:
The Project Manager monitors project activities for compliance with company policies, interprets and requires compliance with the contract and approved plan, maintains control of contract warranty provisions, monitors activities for conformity to scope provisions, establishes change notice procedures, and maintains effective communications with the client and all groups performing work.
6.6 Next Generation Project Managers:
The skills needed for an effective 21st-century Project Manager have changed from those needed in the 1980s. Historically, only engineers became Project Managers based on the belief that a command of technology was necessary. As projects became larger and more complex, it became obvious that Project Managers might need understanding rather than a command of technology. The primary skills needed will be:
- Knowledge of the business
- Risk management
- Integration skills
The critical skill is risk management, which requires a sound knowledge of the business.
6.7 Table: Methods and Techniques for Developing Project Managers:
Methods for developing Project Managers fall into three categories:
- Experiential training/on-the-job: Working with experienced leaders, job rotation, assigning a variety of responsibilities, and customer liaison activities.
- Conceptual training/schooling: Courses, seminars, simulations, games, cases, group exercises, professional meetings, and readings.
- Organizational development: Formally established project management function, proper project organization, project support systems, project charter, and project management directives and procedures.
โญ Key Takeaways
- The Project Manager requires a diverse set of ten specific skills, with team building and leadership being foundational for integrating multidisciplinary teams in an environment with little formal authority.
- The Functional Manager focuses on how and where the work is done and providing resources, while the Project Manager's primary responsibility is planning and administration across organizational lines.
- Selection of the Project Manager is a general management responsibility that requires careful consideration of sources, development paths, and the ability to delegate authority with visible top management support.
- The duties of a Project Manager span four critical functions: planning, organizing, directing, and controlling, with job descriptions varying based on industry and project complexity.
- For next-generation Project Managers, the emphasis is shifting from technical command to understanding the business, risk management, and integration skills.
๐ง Quick Revision Questions
- What are the ten specific skills required for effective Project Management, and which one is considered a prime responsibility?
- How does the role of the Functional Manager differ from that of the Project Manager?
- What five basic questions must be considered in the selection process for a Project Manager?
- What are the four main categories of duties for a Project Manager in the construction industry, and what does each involve?
- What are the three primary skills needed for next-generation Project Managers, and which one is considered the critical skill?