MGMT627 — Midterm Summary (Lectures 1–22)

📘 Lecture 01 — Introduction to Project Management

📖 Overview: This lecture introduces the fundamental concepts of management and project management. It defines management as both a process and a group of people, explores key concepts like goals and resources, and traces the evolution of management thought through pioneers like Frederick Taylor and Henry Gantt. The lecture concludes by comparing 20th and 21st-century organizations and examining the forces driving organizational change, providing a foundational understanding for the project management course.

🗂️ Topics Covered

The lecture covers the definition of management as an art and process, key management concepts including project organization, goals, and resources, and the evolution of management concepts in the modern era with contributions from Frederick Taylor and Henry L. Gantt. It then details the key aspects and functions of management—planning, organizing, leading, and controlling—and presents a comparison of 20th and 21st-century organizations, along with the economic and social forces driving organizational change and paradigm shifts.

📝 Lecture Summary

1.1 What is Management?

Managing is an art of getting things done through and with people in formally organized groups. Management is the process of designing and maintaining an environment in which individuals, working together in groups, efficiently accomplish selected aims towards any project. It is the art of creating an environment in which people can perform as individuals and yet cooperate towards the attainment of group goals.

🔑 Definition — Management as a Process: the process of using organizational resources to achieve the organization’s goals through planning, organizing, leading, and controlling.

🔑 Definition — Management as People: a group of people who engage in the “Process of Management”.

1.2 Key Management Concepts

Key concepts include the project organization, which comprises people working together and coordinating their actions to achieve specific goals. A goal is a desired future condition that the organization seeks to achieve. A resource is an asset, competency, process, skill, or knowledge controlled by an organization.

Various types of resources an organization possesses are: People, Information, Machinery, Financial capital, and Raw Materials. A resource is a strength if it provides a competitive advantage; it is a weakness if the organization does it poorly or lacks the capacity to do it. Organizational resources include: Human, Physical, Financial, Technological, and Information.

1.3 Evolution of Management Concept in Modern Era

Frederick Taylor – Father of Scientific Management and a Mechanical Engineer. He invented high-speed steel cutting tools. He identified that to improve management quality, the major concern was to increase efficiency in production, lower cost, raise profits through higher productivity, and increase worker pay. His message was to give people their best opportunities to be productive and reward them for individual productivity. This increase in labor productivity requires providing ample rewards, adequate trainings, and continuous managerial support. Taylor concluded that “low productivity in any project is a matter of ignorance on part of labor and management.”

Henry L. Gantt stressed the importance of “developing understanding of systems both for labor as well as management,” emphasizing that the human element is the most important in all management problems. Gantt gave graphic methods of describing project plans for better managerial control, highlighting the importance of time and cost. He created the famous Gantt chart, which is the forerunner of PERT.

1.4 Key Aspects of the Management Process

The key aspects of the Management Process are illustrated in a diagram showing a cycle: Efficient & Effective use of Resources leads to Achievement of Organizational Goals.

1.5 Functions of Management

The process of management consists of four basic managerial functions:

a) Planning: The process of setting objectives in any project and then determining what should be done to accomplish them. It is the capstone activity of management. Planning determines an organization’s objective and helps establish appropriate strategies for achieving them, providing direction and obtaining a match between the external environment and internal capabilities.

b) Organizing: The process of assigning tasks, allocating resources, and arranging coordinated activities to implement plans. It involves establishing an intentional structure of roles for people to fill in organizations.

c) Leading: The process of arousing enthusiasm and directing human resource efforts toward project and organizational goals. It involves influencing people to contribute towards goals. Leadership is predominantly concerned with the interpersonal aspect of managing. In projects, most important problems arise from people (desires, attitudes, behavior), so effective project managers must be effective leaders. Leadership implies follower-ship; people follow those who offer means of satisfying their own needs.

d) Controlling: The process of measuring performance and taking actions to ensure desired results in any project. It involves measuring and correcting individual and organizational performance to ensure events conform to plans. The three basic elements of controlling are:

1. Management should establish standards of performance.
2. Performance should be assessed periodically to indicate deviation between actual and standards.
3. Actions should be taken to correct performance that does not conform to standards.

1.6 Management Functions: Planning, Organizing, Leading & Controlling

A diagram shows these four functions as interconnected components of the management process.

1.7 Managerial Functions in Organizations Undertaking Projects

Organizations are arranged to maximize synergy, the ability of the whole to equal more than the sum of its parts. A diagram shows various organizational levels. A model for the organizational environment depicts the External Environment (Economic, Technological, Social/Political, Ethical) surrounding the Internal Environment (Organization: Production, Marketing, Finance, Human Resources).

1.8 Comparison of 20th And 21st Century Organizations

The lecture provides a detailed comparison of these two eras across three dimensions:

• Structure: 20th-century organizations are bureaucratic, multi-leveled, and managed by senior management with many complicated internal interdependencies. 21st-century organizations are not bureaucratic, have fewer levels and employees, with management leading and lower-level employees managing, and minimal internal interdependence.
• Systems: 20th-century organizations depend on few performance information systems, distribute data only to executives, and offer management training only to senior people. 21st-century organizations depend on many performance information systems (especially on customers), distribute data widely, and offer training to many people.
• Culture: 20th-century culture is inwardly focused, centralized, slow to decide, political, and risk-averse. 21st-century culture is externally oriented, empowering, quick to decide, open and candid, and more risk-tolerant.

1.9 Economic And Social Forces Driving Need For Major Changes in Organizations

A diagram illustrates economic and social changes driving change. Distinctive transformation processes for large-scale organizational change include: Reengineering, Restructuring, Quality programs, Mergers and acquisitions, Strategic changes, and Cultural changes.

1.10 Paradigm Shifts

The lecture lists key paradigm shifts from the Industrial Society to the Information Society:

• Industrial Society → Information Society
• Forced Technology → High Tech/High Touch
• National Economy → World Economy
• Short Term → Long Term
• Centralization → Decentralization
• Institutional Help → Self-Help
• Representative Democracy → Participatory Democracy
• Hierarchies → South
• Either/OR → Multiple Option

⭐ Key Takeaways

Students must remember that management is the process of achieving organizational goals through planning, organizing, leading, and controlling resources efficiently. The contributions of Frederick Taylor (Scientific Management) and Henry Gantt (Gantt chart, human element) are foundational for project management. The four core management functions—planning, organizing, leading, and controlling—are the central framework for all managerial activities. Finally, the comparison between 20th and 21st-century organizations highlights a clear shift towards flatter, more flexible, externally-oriented, and empowered structures, which is critical for understanding modern project environments.

🧠 Quick Revision Questions

1. What are the four basic functions of management as described in the lecture?
2. Who is known as the "Father of Scientific Management" and what was his key conclusion about low productivity?
3. What is the significance of Henry Gantt's contribution to project management?
4. List three key differences between the structure of 20th-century and 21st-century organizations.
5. Name three economic and social forces or transformation processes that drive the need for major changes in organizations.

📘 Lecture 2 — Concepts, Definitions and Nature of Projects

📖 Overview: This lecture establishes the foundational understanding of what constitutes a project, distinguishing it from routine operations. It explores why projects are initiated, their core attributes and characteristics, the environment in which they operate, and the key participants or stakeholders involved. Understanding these fundamentals is critical as they form the basis for all project management theory and practice.

🗂️ Topics Covered

The lecture begins by defining a project and its two main types (short-range and long-range), then explains why projects are initiated. It details the attributes and characteristics of projects, the project environment (cultural, political, physical), and project participants including stakeholders. The lecture also covers projects and strategic planning, sub-projects, the triple constraint, examples of projects, differences between operations and projects, and concludes with a classification of project types.

📝 Lecture Summary

What is a Project?

J. M. Juran defined that “a project is a problem scheduled for solution.” The term "problem" refers to the gap between where you are and where you want to be, with an obstacle preventing easy movement to close that gap. Projects are a group of activities that must be performed with limited resources to yield specific objectives within a specific time and locality. Thus, a project is a temporary endeavour employed to create a unique product, service or result. Projects are an investment on which resources are used to create assets that will produce benefits over an expanded period of time. It is a unique process consisting of a set of coordinated and controlled activities with start and finish dates, undertaken to achieve an objective conforming to specific requirements, including the constraints of time, cost and resources.

🔑 Definition — Project: A temporary endeavor undertaken to create a unique product, service, or result.

Short Range Projects

These projects are completed within one year and are focused towards achieving tactical objectives. They are less rigorous and require less or no risk. They are not cross-functional and require limited Project Management tools with a low level of sophistication. It is easy to obtain approval, funding and organizational support for short range projects. For example, "reduce defect in shop number two from 6 to 4 percent."

Long Range Projects

These projects involve higher risk and a proper feasibility analysis is essential before starting them. They are most often cross-functional. Their major impact is over a long period of time, affecting internal as well as external organization. Large numbers of resources are required, and they require breakthrough initiatives from the members.

Why Projects are Initiated?

Projects are initiated in the following scenarios:

• When starting a new business
• To develop/modify a product or service
• For relocating and/or closing a facility
• For regulatory mandate
• For community issues
• To re-engineer the process (to reduce complaints, reduce cycle time, eliminate errors)
• For implementing a new system or process
• To introduce new equipment, tools or techniques

Attributes of a Project

Projects focus on a single goal as compared to a program. They have customers who are affected by the end results. They must be completed within a specified time frame (completion date), within budget (limited resources including people, money, machines), and should be according to specifications (with a certain level of functionality and quality).

In brief, projects are:

• Directed towards achieving a specific result
• Coordination of interrelated activities
• Of limited duration, with a beginning and an end
• Prone to risks (every project has a certain amount of risk)

Characteristics of Projects

Projects are temporary with a definite beginning and end. They have temporary opportunities and temporary teams. Projects are terminated when the objectives are achieved, or conversely, if the objectives cannot be met. Most projects last for several years, but they have a finite duration. They involve multiple resources (human and non-human) and require close coordination. Projects are composed of interdependent activities. At the end of the project, a unique product, service or result is created, with some degree of customization. Projects encompass complex activities that are not simple and may require repetitive acts. They include connected activities where some order and sequence is required, and the output from one activity is an input to another. Project Management lives in the world of conflict — management must compete with functional departments for resources and personnel. There is constant conflict for project resources and for leadership roles. Clients want changes, while the parent organization aims at maximization of profits. There can be two bosses at a time with different priorities and objectives.

💡 Why this matters: Understanding that projects operate in a world of conflict helps prepare project managers to navigate competing demands from stakeholders, functional departments, and clients.

Project Environment

All projects are planned and implemented in a social, economic, environmental, political and international context.

• Cultural and Social Environment: How a project affects people and how they affect the project. This requires understanding of economic, demographic, ethical, ethnic, religious and cultural sensitivity issues.

• International and Political Environment: Knowledge of international, national, regional or local laws and customs, time zone differences, teleconferencing facilities, level of technology use, national holidays, travel means and logistic requirements.

• Physical Environment: Knowledge about local ecology and physical geography that could affect the project or be affected by the project.

Project Participants

Stakeholders

Stakeholders are the ones who have a share or an interest in an enterprise. Stakeholders in a company may include shareholders, directors, management, suppliers, government, employees, customers, and the community. Stakeholders are influenced by the outcomes and objectives and have varying levels of responsibility and authority. They should not be ignored. A project manager should try to manage and fulfill the expectations of the stakeholders. There are both positive and negative stakeholders. In some cases, stakeholder roles and responsibilities overlap (e.g., an engineering firm also provides financing).

Project stakeholders are individuals and organizations that are actively involved in the project, or whose interests may be affected by project execution or completion. They may also exert influence over the project's objectives and outcomes. The project management team must identify the stakeholders, determine their requirements and expectations, and manage their influence to ensure a successful project.

Stakeholders have varying levels of responsibility and authority, which can change over the project life cycle. Their responsibility ranges from occasional contributions in surveys to full project sponsorship, including providing financial and political support. Stakeholders who ignore this responsibility can have a damaging impact on project objectives. Similarly, project managers who ignore stakeholders risk damaging project outcomes.

Stakeholder identification can be difficult. For example, an assembly-line worker whose future employment depends on a new product-design project is a stakeholder. Failure to identify a key stakeholder can cause major problems.

Positive stakeholders benefit from a successful project outcome, while negative stakeholders see negative outcomes from the project's success. For example, business leaders benefiting from an industrial expansion are positive stakeholders, while environmental groups viewing the project as harmful are negative stakeholders. Positive stakeholders' interests are best served by helping the project succeed; negative stakeholders' interests are served by impeding the project's progress. Negative stakeholders are often overlooked at the risk of project failure.

🔑 Definition — Stakeholder: An individual or organization that is actively involved in a project, or whose interests may be affected by project execution or completion, and who may exert influence over the project's objectives and outcomes.

Key Stakeholders

a) Project Manager: The person responsible for managing the project.

b) Customers / End Users: The person or organization that will use the project's product. These may be multiple layers (e.g., doctors who prescribe, patients who take, insurers who pay for a pharmaceutical product). In some areas, customers and users are synonymous; in others, customer refers to the acquiring entity and users are those who directly utilize the product.

c) Performing Organization: The enterprise whose employees are most directly involved in doing the project work.

d) Project Management Working on the Project: Team members directly involved in project management activities.

e) Project Team Members: The group performing the work of the project, including members directly involved in project activities.

f) Sponsors: The person or group that provides financial resources (cash or in kind) for the project.

g) Influencers: People or groups not directly related to the acquisition or use of the project's product, but who can influence (positively or negatively) the project's course due to their position.

h) Project Management Organization: If it exists in the performing organization, it can be a stakeholder if it has direct responsibility for project outcomes.

Project Stakeholders (Broader Category)

In addition to key stakeholders, there are many different names and categories: internal or external, owners and investors, sellers and contractors, team members and their families, government agencies and media outlets, individual citizens, lobbying organizations, and society-at-large. Project managers must manage stakeholder expectations, which can be difficult because stakeholders often have conflicting objectives.

Examples of conflicting stakeholder objectives:

• A department manager requesting a new system may desire low cost; the system architect emphasizes technical excellence; the programming contractor wants to maximize profit.
• VP of Research defines success as state-of-the-art technology; VP of Manufacturing as world-class practices; VP of Marketing focuses on number of new features.
• A real estate owner focuses on timely performance; local government maximizes tax revenue; environmental group minimizes adverse impacts; nearby residents hope to relocate the project.

Projects and Strategic Planning

Projects are the means of achieving an organization's strategic plans. Strategic considerations for project planning include:

• Market demand (e.g., a new refinery)
• Organizational needs (e.g., a university offering new courses for revenue generation)
• Customer requests (e.g., an ISP launching DSL)
• Technological demand (e.g., new video games, advanced cell phones)
• Legal requirements (e.g., child labor control project, toxic waste disposal center)

Sub Projects

Projects are frequently divided into more manageable components or sub-projects. Individual sub-projects are also projects and are managed as such. They can be sub-contracted or outsourced.

The Triple Constraint of Project Management

Meeting stakeholder needs and expectations involves balancing competing demands among cost, quality, scope, and time.

Q = f (T, C, S)

• Where Q is Quality, S is Scope, T is Time, and C is Cost.
• Project quality is affected by balancing these three factors.
• Projects fail when: a) Estimates are faulty b) Time, talent and resources are insufficient or incorrectly applied

Project management is designed to manage or control company resources on a given activity within time, within cost, and within performance expectations. Time, cost, and performance are the constraints. If the project is for an outside customer, there is a fourth constraint: good customer relations.

📐 Formula: Q = f(T, C, S) → Quality is a function of Time, Cost, and Scope; changing any one factor affects the others and overall quality.

Examples of Projects

• Designing and implementing an auto tax filing system
• Hosting a website for a department
• Executing an environmental clean-up of a contaminated site
• Holding a university alumni reunion
• Provision of clean water to a nation
• Developing a new product or service
• Effecting a change in structure, staffing, or style of an organization
• Developing or acquiring a new or modified information system

Operations and Projects

Operations are ongoing and repetitive activities conducted by staff, including:

• Financial management and control
• Continuous manufacturing
• Product distribution

Projects are temporary and unique, performed by teams with:

• Clearly defined team and individual roles
• Open and effective communication systems
• Visible rewards for good performance
• Constant pressure to improve poor performance

Common characteristics between operations and projects:

• Both are performed by people
• Both are constrained by limited resources
• Both are planned, executed, and controlled

Project Types

Type I Projects – Large Engineering Projects

Have well defined project methods and well defined end project requirements. Examples include construction projects.

Type II Projects – Product Development Projects, Early Space Projects

Have poorly defined project methods but well defined project end requirements.

Type III Projects – Software Development Projects

Have well defined project methods but poorly defined project end requirements. The shape of the end product proceeds as work advances.

Type IV Projects – Organizational Development Projects, Vision Definition, Assessment of Impact of Trainings

Have both poorly defined project methods and poorly defined project end requirements.

💡 Why this matters: Understanding project types helps managers select appropriate management approaches, tools, and techniques based on how well-defined the methods and end requirements are.

Why Systems Are Necessary

Companies are often structured with "class or prestige" gaps between levels of management and functional gaps between working units. This creates small operational islands that refuse to communicate. The project manager's responsibility is to get these islands to communicate cross-functionally toward common goals and objectives. Projects fill an essential need in society as the major mode by which change is accomplished, corporate strategy is implemented, business change is addressed, and quality of deliverables is tracked.

The basic business premise never changes: Accomplish the right thing right the first time within justifiable time, resources, and budget. Projects are the means for responding to, if not proactively anticipating, the environment and opportunities of the future.

⭐ Key Takeaways

A project is fundamentally a temporary endeavor with a unique output, constrained by time, cost, and scope—the triple constraint where Quality is a function of all three. Projects differ from ongoing operations in their temporary nature, unique deliverables, and inherent conflict with functional departments. Stakeholders are critical to project success; they can be positive or negative, internal or external, and must be identified and managed carefully as they often have conflicting objectives. Projects are the primary vehicle for implementing organizational strategy and responding to market demands, customer requests, and legal requirements. Finally, projects can be classified into four types based on how well-defined their methods and end requirements are, which determines the appropriate management approach.

🧠 Quick Revision Questions

1. What is the definition of a project according to J.M. Juran, and how does it differ from routine operations?
2. List the four categories of project types and provide one example for each based on the defined project methods and end requirements.
3. What are the three components of the triple constraint, and how is Quality expressed as a function of these components?
4. Explain the difference between positive and negative stakeholders, and why is it important for a project manager to identify negative stakeholders?
5. What are the five strategic considerations that must be kept in mind while planning for projects?

📘 Lecture 03 — Concepts of Project Management

📖 Overview: This lecture introduces the fundamental concepts of project management, defining it as the discipline of managing resources to deliver projects within constraints. It explores the critical distinction between efficiency and effectiveness, the structure of the project management system driven by survival, and provides a comprehensive overview of the project manager's role, activities, skills, and the evolving nature of management.

🗂️ Topics Covered

The lecture covers the core definition of project management, its focus on productivity through efficiency ("doing things right") and effectiveness ("doing right things"). It then examines the project management system, identifying survival as the ultimate driving force. The second half of the lecture is dedicated to the project manager, detailing their types (line, staff, functional, general, administrator), major activities (traditional management, communication, HRM, networking), the formula for success (S = A x M x O), ten facts of managerial life, and essential managerial skills (technical, human, conceptual, design). The lecture concludes with a forward-looking view of "Tomorrow’s Management Today."

📝 Lecture Summary

3.1 What is Project Management?

Project Management is the discipline of organizing and managing resources to deliver all the work required to complete a project within defined scope, time, and cost constraints. A project is a temporary and one-time endeavor to create a unique product or service, contrasting with ongoing operations. The first challenge is delivering within constraints; the second is the optimized allocation of inputs (money, people, materials, etc.) to meet objectives.

Management in any project is concerned with productivity, which refers to both efficiency and effectiveness. 🔑 Definition — Efficiency: minimizing resource costs. It is "doing things right." 🔑 Definition — Effectiveness: getting activities completed. It is "doing right things." Efficiency is concerned with means, and effectiveness with ends. They are interrelated. An organization can be effective but inefficient (getting jobs done at a very high cost) or efficient but not effective (doing wrong things well). Good management requires both getting activities completed and doing so as efficiently as possible.

3.2 The Project Management System

The project management system is composed of interrelated driving forces. Due to this interrelatedness, some contend that the only true driving force is survival. When a company recognizes that its survival is at stake, the implementation of project management becomes easier. The speed at which companies achieve maturity in project management is based on how important they perceive these driving forces to be.

3.3 Who is a Project Manager?

A project manager is a professional responsible for the planning and execution of any project. Their central duty is to ensure project success by minimizing risk throughout the project's lifetime. A successful project manager must be able to envisage the entire project from start to finish and ensure this vision is realized.

3.3.1 Types of Project Managers: Project managers must be responsive to economic, technological, social, political, and ethical factors. The types are:

• Line managers: Responsible for activities making direct contributions to the production of the organization's basic goods or services.
• Staff managers: Use special technical expertise to advise and support line workers.
• Functional managers: Responsible for only one area of activity (e.g., finance, marketing).
• General managers: Responsible for a complex organizational unit with many functional areas.
• Administrator: Someone who administers work in any kind of organization.

3.3.2 Activities of Project Managers: Four major activities are undertaken by project managers:

1. Traditional management: Decision making, planning, and controlling (32% of time).
2. Communication: Exchanging routine information and processing paperwork (29% of time).
3. Human Resource Management (HRM): Motivating, disciplining, managing conflict, staffing, and training (20% of time).
4. Networking: Socializing and interacting with outsiders (19% of time).

The role of project managers is witnessing rapid changes as the business environment moves away from conventional practices.

3.3.3 Success for Project Managers: Three general preconditions for achieving lasting success as a project manager are:

• Ability (A)
• Motivation to manage (M)
• Opportunity (O) Together, they constitute the basic formula for managerial success: 📐 Formula: S = A x M O → Success is the product of Ability, Motivation, and Opportunity. If any one factor is zero, success is zero.

3.3.4 Ten Facts of Project Managerial Life: i) Work long hours, which tend to increase as one climbs the managerial ladder. ii) Are busy, with a day made up of hundreds of brief incidents. iii) Work is fragmented, with little time for any single activity; interruptions are the rule. iv) Job is varied, involving paperwork, meetings, and interaction with many people. v) Are “homebodies”, spending most of their time within their own organizations. vi) Work is primarily oral, spending most time communicating verbally. vii) Use a lot of contacts, continually exchanging information with others. viii) Are not reflective planners, being too busy for uninterrupted planning. ix) Information is the basic ingredient of their work, spending most time obtaining, interpreting, and giving it. x) Do not know how they spend their time, consistently underestimating time on meetings and overestimating time on other tasks.

3.3.5 Managerial Skills: A skill is an ability or proficiency in performing a task. Skills are of the following types: 🔑 Definition — Technical Skill: Knowledge of and proficiency in activities involving methods, processes, and procedures. 🔑 Definition — Human Skill: The ability to work with people, cooperative effort, and teamwork. 🔑 Definition — Conceptual Skill: The ability to see the “big picture” in order to recognize significant elements and understand relationships among them. 🔑 Definition — Design Skill: The ability to solve problems in ways that will benefit the enterprise.

3.4 Tomorrow’s Management Today

The future of management is characterized by:

• Smaller average companies with fewer people.
• More team-based and boundaryless organizational structures.
• Empowered employees who make decisions.
• Flatter organizations as the norm.
• Work organized around teams and processes.
• Changing bases of power.
• Knowledge-based organizations.
• Stress on vision and values.
• Managers as change agents.
• Increased importance of leadership.

⭐ Key Takeaways

The most critical concepts from this lecture are the clear distinction between efficiency ("doing things right") and effectiveness ("doing the right things") and the understanding that successful project management requires both. The project manager’s role is multifaceted, with specific types, a defined breakdown of how they spend their time (32% traditional management, 29% communication, etc.), and the need for a combination of technical, human, conceptual, and design skills. The formula for a project manager's success is S = A x M x O (Ability, Motivation, and Opportunity), where all three factors are essential multipliers, not just add-ons. Finally, the field is evolving towards flatter, team-based, and knowledge-driven organizations where leadership and empowerment are key.

🧠 Quick Revision Questions

1. What is the fundamental difference between a project and an ongoing operation?
2. Explain the difference between efficiency and effectiveness in the context of project management. Can a firm be efficient without being effective?
3. According to the lecture, what is the only true driving force for implementing project management in a firm?
4. A project manager spends 32% of their time on "Traditional Management." List the other three major activity categories and the percentage of time spent on each.
5. What is the formula for managerial success (S) and what do its three components represent?

📘 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:

1. Individual projects: Short-duration projects assigned to a single individual who may act as both project manager and functional manager.
2. Staff projects: Projects that can be accomplished by one organizational unit, such as a department.
3. 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.
4. 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

1. 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?
2. List the major "allies" for project management that emerged between 1985 and 2000, and explain how each contributed to project management's growth.
3. What is the difference between a system, a program, and a project? Provide definitions for each.
4. Compare and contrast the traditional/classical organization, pure product organization, and matrix organizational form—what are the advantages and disadvantages of each?
5. 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:

1. Are the project objectives the same?
2. Is there a distinction between large and small projects?
3. 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

1. Both have different objectives, driven by different requirements aligned with strategic needs.
2. 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.
3. Project Manager focuses on project objectives; Project Management Officer focuses on major programs, scope, and changes required.
4. 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.
5. Project Manager manages scope, schedule, cost, and quality of a product; Project Management Officer manages overall risk, opportunities, interdependencies, and links among different projects.
6. 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

1. What are the five life cycle phases of a system, and how are they applied to a project?
2. What are the two main categories of system costs, and how does the "learning curve" impact operating costs?
3. List at least three characteristics of a project life cycle, including one about risk and one about phase overlap.
4. What are the primary responsibilities of a Project Management Office and a Project Management Officer?
5. 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.

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

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

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

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

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

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

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

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

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

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

1. 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.
2. 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.
3. 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.
4. 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.
5. For next-generation Project Managers, the emphasis is shifting from technical command to understanding the business, risk management, and integration skills.

🧠 Quick Revision Questions

1. What are the ten specific skills required for effective Project Management, and which one is considered a prime responsibility?
2. How does the role of the Functional Manager differ from that of the Project Manager?
3. What five basic questions must be considered in the selection process for a Project Manager?
4. What are the four main categories of duties for a Project Manager in the construction industry, and what does each involve?
5. What are the three primary skills needed for next-generation Project Managers, and which one is considered the critical skill?

📘 Lecture 7 — The Project Manager (Contd.)

📖 Overview: This lecture continues the exploration of the project manager role, focusing on what makes a project manager successful, their responsibilities, and the critical relationships they must manage. It also examines project champions, the power and authority of project managers, and the differences between functional and project organizations, including matrix structures.

🗂️ Topics Covered

The lecture covers the characteristics of a successful project manager and their dependence on line managers. It details the role, responsibilities, and required skills of a project manager, including risk management. The concept of a project sponsor and the project champion is introduced, along with the differences between a champion and a manager. The lecture then explores the power and authority of a project manager, their different sources, and potential problems. Finally, it compares functional and project organizations, detailing the advantages and disadvantages of functional structures and the three types of matrix organizations: weak, balanced, and strong.

📝 Lecture Summary

Successful Project Manager

A good project management methodology provides a framework to increase success, but project management is not purely a science. A successful Project Manager is strongly dependent on a good daily working relationship with line managers who assign resources and the ability of functional employees to report vertically to their line manager and horizontally to one or more project managers. This creates a critical dynamic where employees favor the manager who controls their "purse strings," often putting project managers at the mercy of line managers.

🔑 Definition — Classical Management: A process in which the manager does not necessarily perform things for himself, but accomplishes objectives through others in a group situation.

Role of the Project Manager

A Project Manager is the person with overall responsibility for the successful planning and execution of a project. They must possess a combination of skills, including the ability to ask penetrating questions, detect unstated assumptions, resolve interpersonal conflicts, and apply systematic management skills. The Project Manager's key duty is to recognize that risk directly impacts the likelihood of success and must be formally and informally measured. A good PM can reduce risk through open communication, ensuring every significant participant can express opinions.

Roles and Responsibilities of Project Manager

The role encompasses many activities, including planning, scheduling, budgeting, controlling quality, managing risks, and team leadership. The project manager operates within time, cost, and performance constraints, reminding line managers of all three, not just performance. Success is like a three-legged stool composed of the Project Manager, the line manager, and senior management. The critical interface is between the project and line managers, who must share authority, responsibility, and accountability.

A project sponsor (often an executive) provides behind-the-scenes assistance, advice, and guidance, especially during a crisis. The sponsor’s responsibility is to make effective and timely decisions based on accurate data provided by the Project Manager. The line manager must cope with numerous challenges like unlimited work requests, predetermined deadlines, and unscheduled changes.

When staffing, a candidate's interpersonal and communication skills are crucial. An individual qualified for a vertical promotion (line management) may not be suitable for a horizontal promotion (project management). A good Project Manager understands both their own strengths and weaknesses and those of their employees.

🔑 Formula: Project Success = Project Manager + Line Manager + Senior Management

📌 Example: A major utility company starts each computer project with a feasibility study. Project Managers perform the study without functional support. Functional managers argue the results are inaccurate. The PMs argue they lack time and money for a complete analysis. This demonstrates organizational conflict.

Project Champions

Corporations encourage employees to think up new ideas. One reward for an idea generator is the title of "Project Champion." However, if the Champion becomes the Project Manager, the project may fail because championing an idea requires different skills than managing a project.

Power and Authority of Project Manager

Authority is the legal or rightful power to command or direct others. Power is granted by subordinates and is a measure of their respect. In a traditional structure, power comes from hierarchy; in a project structure, it comes from credibility, expertise, and good decision-making. Project authority is the way of thinking to unify all activities towards the project's goal. A good PM knows where their authority ends and must have more authority than their responsibility calls for, especially when risk is high.

Common sources of power and authority problems include poorly documented authority, dual accountability, and shifting personnel loyalties. The project environment is an arena of continuous conflict and negotiation. Ground rules for negotiations include taking place at the lowest level, defining the problem first, and escalating only if agreement cannot be reached.

💡 Why this matters: A project manager's authority is not always clearly defined. Understanding its sources and limitations is critical for navigating conflicts and successfully managing across functional lines.

🔑 Definition — Influence Project Manager: A project manager who has only monitoring authority.

Functional and Project Organizations

A Functional Organization is a structure where authority rests with functional heads and is sectioned by departmental groups. Advantages: Simple, clear, reduces overhead, and provides clear career paths. Disadvantages: Coordination of tasks is difficult, and there is little reward for cross-functional cooperation, leading to departmental blaming.

Matrix Organizations fall between fully functional and fully projectized structures. Three types exist:

1. Weak/Functional Matrix: A Project Administrator with limited authority tracks progress and enhances communication; functional managers control resources.
2. Balanced/Functional Matrix: Power is shared equally between the Project Manager and functional managers. This is the most difficult system to maintain.
3. Strong/Project Matrix: The Project Manager is primarily responsible; functional managers provide technical expertise. Conflicts can arise over resource assignment.

💡 Why this matters: The choice of organizational structure directly impacts a project manager's authority and ability to manage resources, making it a critical strategic decision for any project.

⭐ Key Takeaways

The success of a project manager hinges on a strong, collaborative relationship with line managers, who are the true controllers of resources. While a project manager's formal authority may be limited, their effectiveness relies on earning power through credibility, expertise, and negotiation. The project manager's primary role is to balance time, cost, and performance constraints while managing risk through open communication. Organizational structures, whether functional or matrix (weak, balanced, or strong), define the distribution of power and are a major source of conflict and negotiation in project management. Finally, the skills of a project champion and a project manager are distinct; a person good at generating ideas is not necessarily good at executing them.

🧠 Quick Revision Questions

1. What is the "three-legged stool" analogy for project management success, and who represents each leg?
2. What is the critical difference between authority and power as defined for a project manager?
3. Name the three types of matrix organizations and briefly describe where the power lies in each.
4. Why is it often risky to make a "Project Champion" the "Project Manager"?
5. List two potential problems that can arise from a failure to establish clear authority relationships on a project.

📘 Lecture 08 — Project Conception and Project Feasibility

📖 Overview: This lecture introduces the initial stage of project development—project conception and feasibility assessment. It explains how project ideas originate, how alternatives are formulated and selected, and why a thorough feasibility analysis is critical before committing resources to a project.

🗂️ Topics Covered

The lecture covers the concept of project conception and its three main stages: defining a requirement or opportunity, formulating preliminary alternatives, and initial selection of alternatives. It then provides a detailed explanation of feasibility analysis, including its purpose and process, followed by the nine distinct types of feasibility that must be assessed. The lecture concludes with a discussion on distinguishing between tangible and intangible benefits and costs in project evaluation.

📝 Lecture Summary

Project Conception

Project conception is the initial step in defining the actual scope of a project. It generally starts with a manifestation of a requirement or an opportunity that will benefit the corporate interests and culminates when one or more preliminary options have been formulated. The process, while illustrated by an industrial project, has features directly translatable to conceptual evolution in many diverse applications.

Stages of Project Conception

Initial conceptualization of a project has various degrees of complexity, depending on the nature of the specific project. The company's planning strategy may require formulations of programs involving several projects; conception of the overall program should then precede conception of the individual specific projects.

The conceptual stage involves the following activities:

1. Definition of a requirement or an opportunity that commands the interests of the company.
2. Formulation of a set of preliminary alternatives capable of fulfilling the initial requirement.
3. Selection of alternative(s) that might satisfy the requirements in terms and conditions attractive to the company.

Definition of the Requirement or Opportunity: The continuity of efficient operations and the opening of new business areas are the main drives for capital investments. Investment opportunities are detected through operational analysis of current performance and by forecasts of the most likely future scenarios. Initially, the scope of any new investment is likely to be vague; subsequent definition involves consideration of all available relevant facts, required resources, and constraints.

Preliminary Formulation of the Alternatives: Project conception continues with development of alternatives capable of fulfilling the expressed objectives. The preliminary formulation of alternatives is important as it sets the pace of the subsequent definition and elaboration of the project scope. The company calls upon the experience and creativity of its technicians, managers, and directors to generate an adequate group of alternatives.

Initial Selection of Alternatives: After alternatives have been identified, comparative analyses are made to select the most beneficial and reject the least attractive. The selection process employs a basic feasibility analysis of each alternative and the establishment of criteria that will allow the identification of the most attractive options. The cost, schedule, profitability, and other salient advantages and disadvantages of each of the selected alternatives are assessed in terms of order of magnitude.

Feasibility Analysis

A feasibility study is an analytical tool used during the project planning process that shows how a business would operate under an explicitly stated set of assumptions. These assumptions include the technology used (facilities, types of equipment, manufacturing process, etc.) and the financial aspects of the project (capital needs, volume, cost of goods, wages, etc.).

What is Feasibility Assessment?

A feasibility study is an analysis of the viability of an idea. It focuses on helping answer the essential question: "Should we proceed with the proposed project idea?" Determining early on that a business idea will not work saves time, money, and heartache later.

A feasible business venture is one where the business will generate adequate cash flow and profits, withstand the risks it will encounter, remain viable in the long-term, and meet the goals of the founders.

A feasibility study is usually conducted after producers have discussed a series of business ideas or scenarios. It helps to "frame" and "flesh-out" specific business alternatives so they can be studied in-depth. A pre-feasibility study may be conducted first to help sort out relevant alternatives. A market assessment may be conducted to help determine the viability of a proposed product in the marketplace.

The go/no-go decision is one of the most critical in business development—it is the point of no return. The feasibility study will be a major information source in making this decision.

A feasibility study is not a business plan. The feasibility study provides an investigating function (addressing "Is this a viable business venture?"), while the business plan provides a planning function (outlining actions needed to take the proposal from "idea" to "reality"). The feasibility study outlines and analyzes several alternatives; the business plan deals with only one alternative or model. The feasibility study is conducted before the business plan.

From a financial perspective, project selection is basically a two-part process: first, the organization conducts a feasibility study to determine whether the project can be done; second, it performs a benefit-to-cost analysis to see whether the company should do it.

Types of Feasibility

1. Technical Feasibility: Reviews the engineering feasibility of the project, including structural, civil, and other relevant engineering aspects. The technical capabilities of the personnel as well as the capability of the projected technologies are considered. In third world countries, technology transfer between geographical areas and cultures needs to be analyzed.

2. Managerial Feasibility: Demonstrated management capability and availability, employee involvement, and commitment are key elements. This addresses the management and organizational structure of the project, ensuring the proponent's structure is well suited to the type of operation undertaken.

3. Economic Feasibility: Involves the feasibility of the proposed project to generate economic benefits. A benefit-cost analysis and a break-even analysis (when appropriate) are required aspects. The tangible and intangible aspects of a project should be translated into economic terms to facilitate a consistent basis for evaluation.

4. Financial Feasibility: Should be distinguished from economic feasibility. Financial feasibility involves the capability of the project organization to raise the appropriate funds needed to implement the proposed project. Loan availability, credit worthiness, equity, and loan schedule are reviewed as aspects of financial feasibility analysis.

5. Cultural Feasibility: Deals with the compatibility of the proposed project with the cultural environment of the project. In labor-intensive projects, planned functions must be integrated with the local cultural practices and beliefs.

6. Social Feasibility: Addresses the influences that a proposed project may have on the social system in the project environment. The effect of the project on the social status of the project participants must be assessed to ensure compatibility.

7. Safety Feasibility: Refers to an analysis of whether the project is capable of being implemented and operated safely with minimal adverse effects on the environment.

8. Political Feasibility: Requires an evaluation of the compatibility of project goals with the prevailing goals of the political system. Political considerations often dictate directions for a proposed project, particularly for large projects with significant visibility.

9. Environmental Feasibility: Often a killer of projects through long, drawn-out approval processes and active opposition. Concern must be shown and action must be taken to address any and all environmental concerns. This component also addresses the ability of the project to timely obtain needed permits, licenses, and approvals.

10. Market Feasibility: Should not be confused with Economic Feasibility. The market needs analysis views the potential impacts of market demand, competitive activities, and market share available. Possible competitive activities by competitors must be analyzed for early contingency funding and impacts on operating costs.

💡 Why this matters: Understanding the distinct types of feasibility ensures that a project is evaluated from all critical angles—technical, financial, social, and environmental—preventing costly failures that arise from a narrow assessment focus.

Tangible and Intangible Benefits

Estimating benefits and costs in a timely manner is very difficult.

Benefits are often defined as:

• Tangible benefits for which dollars may be reasonably quantified and measured.
• Intangible benefits that may be quantified in units other than dollars or may be identified and described subjectively.

Minimum costs that must be determined include:

• The current operating costs or the cost of operating in today's circumstances.
• Future period costs that are expected and can be planned for.
• Intangible costs that may be difficult to quantify and are often omitted if quantification would contribute little to the decision-making process.

There must be careful documentation of all known constraints and assumptions made in developing costs and benefits. The go or no-go decision to continue with a project could very well rest upon the validity of the assumptions.

⭐ Key Takeaways

The lecture establishes that project conception begins with identifying a requirement or opportunity, followed by formulating and selecting preliminary alternatives. A feasibility study is a critical analytical tool that answers whether a project should proceed, and it must be conducted before a business plan is developed. There are ten distinct types of feasibility—technical, managerial, economic, financial, cultural, social, safety, political, environmental, and market—each examining a different dimension of project viability. Benefits and costs are categorized as tangible (quantifiable in dollars) or intangible (subjective or measured in other units), and all assumptions must be clearly documented. The go/no-go decision is a point of no return that relies heavily on the findings of a properly conducted feasibility study.

🧠 Quick Revision Questions

1. What are the three main activities involved in the conceptual stage of a project?
2. What is the fundamental question that a feasibility study is designed to answer?
3. How does a feasibility study differ from a business plan in terms of its purpose and scope?
4. List and briefly describe the ten types of feasibility discussed in the lecture.
5. What is the difference between a tangible benefit and an intangible benefit, and why must assumptions be carefully documented when estimating costs and benefits?

📘 Lecture 09 — Project Feasibility (Contd.)

📖 Overview: This lecture provides a comprehensive examination of feasibility studies, their purpose, scope, and structure. It explains how feasibility studies serve as decision-making tools for determining project viability, distinguishing them from business plans and other project documents, while outlining the critical elements and assessment components needed for thorough project evaluation.

🗂️ Topics Covered

The lecture covers the definition and purpose of feasibility studies, explaining why organizations conduct them before project implementation. It clarifies what a feasibility study is not, distinguishing it from business plans and other documents. The scope of feasibility analysis is examined through seven key elements including need analysis, process work, engineering, cost estimation, financial analysis, project impacts, and conclusions. Finally, the elements of a feasibility assessment are detailed, covering executive summary, need analysis, engineering, advantages/disadvantages, market analysis, financial analysis, risk analysis, comparative analysis, and recommendations.

📝 Lecture Summary

9.1 What is a Feasibility Study?

A feasibility study is essentially a process for determining the viability of a proposed initiative or service and providing a framework and direction for its development and delivery. It is a process for making sound decisions and setting direction. This process is driven by research and analysis, usually involves some form of consultation with stakeholders, community, and users, focuses on analyzing, clarifying and resolving key issues and areas of concern or uncertainty, and very often involves basic modeling and testing of alternative concepts and approaches.

There is no universal format for a feasibility study, as studies can be adapted and shaped to meet the specific needs of any given situation. A feasibility study is designed to provide an overview of the primary issues related to a business idea, with the purpose being to identify any "make or break" issues that would prevent your business from being successful in the marketplace. In other words, a feasibility study determines whether the business idea makes sense.

A thorough feasibility analysis provides necessary information for the business plan. For example, a good market analysis is necessary to determine the project's feasibility, and this information provides the basis for the market section of the business plan. Because putting together a business plan represents a significant investment of time and money, you want to ensure there are no major roadblocks facing your business idea before making that investment.

A feasibility study looks at three major areas: market issues, organizational/technical issues, and financial issues. This is meant to be a "first cut" look at these issues. For example, a feasibility study should not do in-depth long-term financial projections, but it should do a basic break-even analysis to see how much revenue would be necessary to meet your operating expenses.

🔑 Definition — Feasibility Study: A process for determining the viability of a proposed initiative or service and providing a framework and direction for its development and delivery.

9.2 Why Do Feasibility Studies?

Developing any new business venture is difficult, and taking a project from the initial idea through the operational stage is a complex and time-consuming effort. Most ideas, whether from a cooperative or an investor-owned business, do not develop into business operations. If these ideas make it to the operational stage, most fail within the first 6 months. Before potential members invest in a proposed business project, they must determine if it can be economically viable and then decide if investment advantages outweigh the risks involved.

Many cooperative business projects are quite expensive to conduct and involve operations that differ from those of the members' individual business. These operations involve risks with which the members are unfamiliar. The study allows groups to preview potential project outcomes and to decide if they should continue. Although the costs of conducting a study may seem high, they are relatively minor when compared with the total project cost. The small initial expenditure on a feasibility study can help to protect larger capital investments later.

Feasibility studies are useful and valid for many kinds of projects. Evaluation of new business ventures is the most common usage, but studies can help groups decide to expand existing services, build or remodel facilities, change methods of operation, add new products, or even merge with another business. A feasibility study assists decision makers whenever they need to consider alternative development opportunities.

Feasibility studies permit planners to outline their ideas on paper before implementing them, which can reveal errors in project design before their implementation negatively affects the project. Applying the lessons gained from a feasibility study can significantly lower project costs. The study presents the risks and returns associated with the project so prospective members can evaluate them. There is no "magic number" or correct rate of return a project needs to obtain before a group decides to proceed. The acceptable level of return and appropriate risk rate will vary for individual members depending on their personal situation.

The proposed project usually requires both risk capital from members and debt capital from banks and other financers to become operational. Lenders typically require an objective evaluation of a project prior to investing. A feasibility study conducted by someone without a vested interest in the project outcome can provide this assessment.

💡 Why this matters: The feasibility study acts as a risk management tool that protects against significant capital losses by identifying potential problems before major investments are made.

9.3 What a Feasibility Study is not:

Feasibility studies are conducted on "real-world" projects and are not academic or research papers. Simulations or projection models, though useful on some projects, do not replace a feasibility study. The study should not be a "cookie cutter" approach to a project and should not merely be a generic source of information. Once completed, a study should permit a group to make better decisions for the strategic issues of their specific project.

A feasibility study is not a business plan. A business plan is elaborated later in the project development process than the feasibility study. The main purpose of a business plan is to function as a blueprint for the group's business operations. The business plan presents the group's intended responses to the critical issues raised in the feasibility study. The feasibility study results form the basis for developing a business plan.

The purpose of a feasibility study is not to identify new ideas or concepts for a project. These ideas should be clearly identified before a study is initiated. The group needs to accomplish a number of steps before a feasibility study is instituted. The closer the assumptions lie to the "real-world", the more value the feasibility study will hold for the group.

A feasibility study should not be conducted as a forum merely to support a desire that the project will be successful. The study should be an objective evaluation of the project's chance for success. Negative results can be just as useful for decision-makers as positive results. Financers may require a feasibility study before providing loans, but this should not be the only purpose of a study. A feasibility study should enhance a banker's ability to evaluate a project, but the primary goal should be to aid a group's decision-making, not to secure financing.

A feasibility study will not determine whether or not a project should be undertaken. The potential members have to decide if the economic returns justify the risks involved in their continuing the project. The results of the feasibility study assist them in this. A feasibility study serves as an analytical tool to present the basic assumptions of a project idea, shows how results vary when these assumptions change, and provides guidance as to critical elements of a project.

9.4 Scope of Feasibility Analysis:

In general terms, the elements of a feasibility analysis for a project should cover the following:

1. Need Analysis: This indicates recognition of a need for the project. The need may affect the organization itself, another organization, the public, or the government. A preliminary study is then conducted to confirm and evaluate the need, followed by a proposal of how the need may be satisfied. Pertinent questions include: Is the need significant enough to justify the proposed project? Will the need still exist by the time the project is completed? What are the alternate means of satisfying the need? What are the economic, social, environmental, and political impacts of the need?

2. Process Work: This is the preliminary analysis done to determine what will be required to satisfy the need. The work may be performed by a consultant who is an expert in the project field. The preliminary study often involves system models or prototypes. For technology-oriented projects, artist's conception and scaled-down models may be used for illustrating the general characteristics of a process. A simulation of the proposed system can be carried out to predict the outcome before the actual project starts.

3. Engineering and Design: This involves a detailed technical study of the proposed project. Written quotations are obtained from suppliers and subcontractors as needed. Technology capabilities are evaluated as needed. Product design, if needed, should be done at this time.

4. Cost Estimate: This involves estimating project cost to an acceptable level of accuracy. Levels of around -5% to +15% are common at this level of a project plan. Both the initial and operating costs are included in the cost estimation. Estimates of capital investment and of recurring and nonrecurring costs should also be contained in the cost estimate document. Sensitivity analysis can be carried out on the estimated cost values to see how sensitive the project plan is to the estimated cost values.

5. Financial Analysis: This involves an analysis of the cash flow profile of the project. The analysis should consider rates of return, inflation, sources of capital, payback periods, breakeven point, residual values, and sensitivity. This is a critical analysis since it determines whether or not and when funds will be available to the project. The project cash flow profile helps to support the economic and financial feasibility of the project.

6. Project Impacts: This portion of the feasibility study provides an assessment of the impact of the proposed project. Environmental, social, cultural, political, and economic impacts may be some of the factors that will determine how a project is perceived by the public. The value added potential of the project should also be assessed. A value added tax may be assessed based on the price of a product and the cost of the raw material used in making the product.

7. Conclusions and Recommendations: The feasibility study should end with the overall outcome of the project analysis. This may indicate an endorsement or disapproval of the project. Recommendations on what should be done should be included in this section of the feasibility report.

📐 Formula: Cost Estimate Accuracy: -5% to +15% → The acceptable range of accuracy for project cost estimates at the feasibility study level.

9.5 Elements of a Feasibility Assessment:

As a first step, a feasibility assessment should define the business idea, be it a new project, product or service. The project or business idea feasibility can then be determined. The feasibility needs to account for the current circumstances of the proponent. For example, for a business intender it should take into account personal readiness, skills, resources, knowledge and goals. For established businesses, linkages to existing lines of business, customers, suppliers, employees and other stakeholders need to be accounted for.

A feasibility report should have the following structure:

1. Executive Summary: Provides a quick overview of the main points of the assessment, helping to form a picture of the proposal along with the recommendations. It should be concise and include the major findings covered in the main body of the report.

2. Need Analysis: Provides context to the business proposition. It analyzes the justification of the idea, with a study of possible alternatives. It links the business idea to the current circumstances and helps to inform evaluation of the business idea.

3. Engineering: Description of the technical aspects of the business idea, including any changes needed to be made to existing processes or the need to add items to existing range of products and services.

4. Advantages and Disadvantages: Advantages and disadvantages of the business idea compared to alternatives, such as competing products; or for a new concept, its relevance to current practices, and to unmet or potential demand.

5. Market for the Product Offerings: States the number of customers, expected frequency and size of average purchase, and any reduction in costs across the business arising from the new product or service. Any assumptions about customer purchase behavior should be identified. Research should focus on customers, products and services, competition, mapping, costing, suppliers, location, resources, and staff.

• Customers: You need to be clear about the type of customer you will target and why they will respond to your offering. Identify target market segments or groups.
• Products and Services: Create a list showing the products/services you will be offering to each segment and how much customers will pay.
• Competition: List competitors, note their perceived strengths and weaknesses, and understand why they are competition. Price should not be the only answer; whole of life value, product features, distribution, promotion strategies, and after sales options may all be part of the purchase decision.
• Map: Obtain a map and define market boundaries, your location, access routes, competitors, suppliers, and demographic information.
• Costing: Assess how long it will take to produce or obtain products/services, work out the cost of that time, and determine costs for buying, assembling, or producing them. This approach should account for all costs over and above existing activity.
• Suppliers: Identify preferred and alternative suppliers; collect catalogues and price lists.
• Location: Identify site, whether rented, owned or at home, and consider advantages and disadvantages.
• Resources: Assess assets and equipment required, cost of acquiring them, and alternative methods of acquisition such as outright purchase versus hire purchase or leasing.
• Staff: Determine what staff you need, what skills they require, and what you need to pay them.

6. Financial analysis: Work out the profits from a given level of operations, the capital required, and how the capital will be found to commence operating.

7. Risk analysis of the Preferred Solution: Risk analysis may take the form of basic break-even analysis, i.e., the level of business operation that will ensure that the business does not incur a loss. Sophisticated analysis may consider various business scenarios based on assumptions made in costing and market analyses.

8. Comparative Analysis: Comparative analysis of alternatives should reflect the objectives of the project. Decision making may be based on maximizing profit or minimizing loss for various business scenarios. Some alternatives may be riskier with higher financial payoffs under certain scenarios and potential losses under other scenarios, while some may be less risky with low financial profits or losses under a wide variety of circumstances.

9. Recommendations: Recommendations of the preferred alternative with an associated plan of action; or a decision not to proceed. Possible plans of action include going back to the drawing board, developing more promising alternatives, further research to minimize possibility of failure, or moving forward to develop a detailed business plan.

⭐ Key Takeaways

A feasibility study is fundamentally a decision-making tool that determines project viability by analyzing market, organizational/technical, and financial issues, serving as a crucial risk management step before committing significant resources. The study must be distinguished from a business plan — the feasibility study comes first and provides the foundation for developing the business plan, which is created later as a blueprint for operations. The scope of feasibility analysis encompasses seven critical elements: need analysis, process work, engineering and design, cost estimation (typically with -5% to +15% accuracy), financial analysis, project impacts assessment, and conclusions with recommendations. A comprehensive feasibility report must include nine components: executive summary, need analysis, engineering, advantages/disadvantages, market analysis (covering customers, products, competition, mapping, costing, suppliers, location, resources, and staff), financial analysis, risk analysis (including break-even analysis), comparative analysis of alternatives, and final recommendations. The feasibility study should be an objective evaluation conducted by someone without vested interest, and negative results are equally valuable to decision-makers as positive outcomes.

🧠 Quick Revision Questions

1. What are the three major areas that a feasibility study examines, and why is this considered a "first cut" analysis?
2. What is the key difference between a feasibility study and a business plan in terms of timing and purpose?
3. What is the acceptable level of accuracy for cost estimates in a feasibility study, and what is sensitivity analysis used for?
4. List the nine structural elements required in a comprehensive feasibility assessment report.
5. Why should a feasibility study not be conducted merely to secure financing or to support a predetermined desire for project success?

📘 Lecture 10 — Project Feasibility (Contd.)

📖 Overview: This lecture continues the exploration of project feasibility, focusing on the characteristics of a feasibility study, what bankers look for in such studies, and a detailed value-chain-based feasibility assessment process. It provides a practical framework for evaluating technical, operational, and economic viability before committing major resources to a project.

🗂️ Topics Covered

This lecture covers the key characteristics and objectives of a feasibility study, including the critical role of user involvement and the typical checklist items. It then examines the feasibility study from a banker's perspective, detailing what lenders need to see, such as an executive summary and financial package blueprint. The core of the lecture is the Feasibility Assessment Process, which uses a value chain approach to evaluate technical and economic feasibility across all stages: from input sourcing and procurement, through operations and production, warehousing and delivery, to sales and marketing, non-market factors, data collection, customer service, and finally the decision recommendation with cost/revenue projections and sensitivity analysis.

📝 Lecture Summary

10.1 Characteristics of a Feasibility Study:

The feasibility study phase provides a firmer basis for deciding whether to undertake a project by considering the technical aspects of conceptual alternatives. Its purpose is to plan project development activities, estimate time, staffing, and equipment needs, and identify probable costs and consequences. The objective is to provide management with predictable results of implementing a specific project in the form of a feasibility study report, which is used to decide whether to proceed with the costly development and implementation phases.

User involvement during the feasibility study is critical. The user must supply effort and information and judge the impact of alternative approaches. The primary user must be highly qualified and intimately familiar with the organization's workings. Improper technical or operating decisions made during this step may go undetected and could result in the termination of a valid project or the continuation of an infeasible one.

A typical feasibility study checklist includes summary-level items (evaluate alternatives, market potential, cost effectiveness, producibility, technical base) and detail-level items (specific problem determination, analysis of state-of-the-art technology, assessment of in-house capabilities, test validity of alternatives, quantify unknowns, conduct trade-off analysis, prepare initial goals and preliminary cost estimates).

The end result of the feasibility study is a management decision to terminate the project or approve its next phase. This decision is especially critical because later phases require a major commitment of resources. Once a project is deemed feasible and approved, it must be prioritized with other approved projects given limited resources.

10.2 The Feasibility Study - What Bankers Like to See in Them:

A cardinal rule in banking is to borrow from a lender who understands your business. A feasibility study is often done with an eye towards explaining the project to potential financiers. Bankers can have different requirements than group members. The feasibility study should contain the following information:

🔑 Definition — Executive Summary: Short, complete, and to the point. It must allow the banker to understand the project basics. It should contain: project purpose, repayment possibility, projected financial returns (revenues, costs, net income), and economic benefits (ROI and IRR).

🔑 Definition — Financial Package Blueprint: Clearly shows what resources the group wants from the bank and allows calculation of potential project risk. It should contain: characteristics of assets to be financed, expected rate of conversion to cash-liquidity, risk evaluation data (internal and external risks), evaluation of economic consequences (net reserves covering capital cost), financial forecast (three years of projected cash flows, operating statements, balance sheets), and documentation supporting assumptions.

10.3 The Feasibility Assessment Process:

Feasibility studies should encompass at least two assessments: technical feasibility (physical, technical, technological dimensions) and economic feasibility (economic viability within its defined domain). The value chain approach allows these two assessments to be embedded into a single initiative, facilitating understanding of the domain's effects on different stages from input sourcing to customer support. It also facilitates appreciation of resources, technology, customer expectations, and infrastructure required for success.

💡 Why this matters: The value chain approach provides a systematic way to identify bottlenecks and ensure all critical aspects of a project are evaluated before committing resources.

10.3.1 Input Sourcing and Procurement:

The feasibility assessment begins at the input sourcing and procurement stage. The technical dimension encompasses the availability of required inputs in appropriate levels of quality and quantity, including evaluation of cycles and trends, physical movement of inputs from origination to processing facilities, and assessment of different supply sources. If specific human resources and technologies are required, their availability is assessed.

The economics of input sourcing emanates from the technical assessment. The objective is to determine the range of prices typical in the domain over a reasonable period, not just a single price. Price trends and cycles can be matched against quantity and quality trends to provide insights into potential bottlenecks in the input sourcing and procurement function.

10.3.2 Operations and Production:

This stage transforms inputs into outputs and generally absorbs the largest share of investment capital. The objective of technical feasibility assessment is to determine if the envisaged technology is suitable for the desired quantity and quality of product. It also seeks to determine if equipment and associated technologies are at the appropriate operational scale.

Because of the specialized knowledge required, professionals with required experience must be recruited. You must encourage them to provide the full range of knowledge about available technologies and equipment. You need to assess the physical layout of equipment and its impact on operational efficiency. Professionals should also provide insights into how different technologies compare regarding people requirements, skill levels, and operational inputs (electricity, gas, maintenance protocols, etc.).

The best sources of economic data are equipment suppliers. Primary data can be collected by providing a detailed product description to potential suppliers in a Request for Quote (RFQ) offer. The principal advantage of using an RFQ is to improve knowledge of alternative solutions. Given the rate of technical obsolescence, capital investments should maximize longevity given technical and economic efficiency considerations. You should also consider strategic alliances with companies having existing processing capacity.

Unbiased, knowledgeable people should be hired to review RFQ responses. Arrange for suppliers to make presentations so you can ask necessary questions.

10.3.3 Warehousing, Storage and Delivery:

The feasibility analysis should assess the implications of warehousing, storage, and delivery systems. It should assess alternative sources of warehousing and storage (owning, renting, strategic alliance). The assessment should focus not only on physical facilities but also on management technologies of warehouse and storage facilities management. Product tracking systems that maximize space utilization and turnover are critical. Available infrastructure to support physical movement of products to warehouses and customers must also be assessed.

The economics of physical buildings, location, infrastructure, and technologies are brought to bear on technical options. The best sources of technical and economic information are suppliers of warehousing and storage services. The accuracy of data supplied depends on the clarity and precision of input information.

10.3.4 Sales and Marketing:

Marketing and sales provide direct insight into the project's potential market and the Structure, Conduct and Performance (SCP) characteristics of industry players. This assessment bridges intra-firm feasibility dimensions with extra-firm feasibility dimensions.

The conceptual backbone for SCP is the assessment of demand and supply conditions and behavior of other firms in the industry. Supply and demand conditions should cover size and scope economies, seasonality and trends, availability of substitutes, industry growth rates, and demand elasticities.

Industry structure refers to the number and size of firms in the industry. Industry conduct describes pricing behavior, price discovery mechanisms, product distribution, promotional initiatives, research and development intensity, and legal tactics. Industry performance assesses profitability of firms in the industry, requiring information on prices, product quality, technical progress, and capacity utilization.

10.3.5 Non-Market Factors:

A technically and economically feasible project can fail when confronted with government policies and/or regulations. Feasibility studies should assess existing and/or planned regulatory initiatives that impinge on the project. Environmental regulations and their technical and economic compliance effects must be analyzed. Similarly, policies targeted to the industry of interest and changes in these policies need assessment. The results form the backdrop for assessing feasibility and help position the product within the context of existing market conditions.

10.3.6 Data Collection:

Information on industry structure and performance may be obtained from government statistics (number of firms, employees, wages, value of shipments, gross margins). Specific industries collect their own statistics and commission reports. Interviews with industry experts can be a major information source. Significant information may be obtained from industry news and industry-specific publications. Academic publications and government documents also provide important insights on SCP situations.

For agricultural value-added initiatives, secondary data can suffice for input sourcing and procurement. In special cases, primary data collection may be necessary through formal surveys or interviews. Effective collection of primary data can be expensive and time consuming. An alternative when secondary data is not neatly available is to pull them together from different sources, ensuring measurements and definitions are similar.

10.3.7 Customer Service and Support:

The final step in the value chain framework is finding out what customer needs are not being satisfied. The purpose is to determine if the proposed project's offering can make a difference. Results provide input into the project's product differentiation index and allow identification of appropriate placement and promotional options. Customer service research allows the project to develop market segments and refocus other components.

Information can be obtained from reviewing consumer and industry publications. Direct information may be obtained through focus group interviews, surveys, and/or interviews. While these can be expensive, they are worthwhile if technical and economic assessments are supportive. The process is iterative, using information from one stage to dig deeper into earlier stages.

10.3.8 The Decision Recommendation:

The purpose of a feasibility study is to make a decision about whether to proceed with a business opportunity. The emphasis on recommendations is economic or financial. The easiest approach is to gather all information, identify items requiring capital expenditure, estimate those expenditures, identify types of people and skills required, determine wages and benefits, and identify other project-related costs. Then, using production capacity, projected market share growth rates, and estimated market size with price information, develop a projected revenue or sales statement. All assumptions driving projections must be specifically defined.

10.3.9 Cost and Revenue Projections:

Cost and revenue projections allow development of the net cash flow emanating from the business over the projected time frame. This statement can be subjected to capital investment analysis by selecting a reasonable discount rate and estimating Net Present Value (NPV) and/or Internal Rate of Return (IRR).

🔑 Definition — Net Present Value (NPV): The difference between the present value of cash inflows and the present value of cash outflows over a period of time. 📐 Formula: NPV = Σ(Cash Flow / (1 + r)^t) - Initial Investment → A positive NPV implies an economically feasible project.

🔑 Definition — Internal Rate of Return (IRR): The discount rate that makes the NPV of all cash flows equal to zero. 📐 Formula: 0 = Σ(Cash Flow / (1 + IRR)^t) - Initial Investment → If IRR exceeds the required rate of return, the project is economically feasible.

10.3.10 Sensitivity Analysis:

The project cash flow should be subjected to the full range of sensitivity analysis under a range of prices. This provides the full range of conditions supporting feasibility. The wider the band of feasible outcomes from varying critical assumptions, the more confident you can be about viability. If the band of feasibility is narrow, the project's viability is more susceptible to uncertain shifts.

These possibilities may be divided into three blocks: worst case, normal case, and best case scenarios. Sensitivity analysis must be conducted for different scenarios (e.g., best price with worst demand conditions) to provide insights into critical bottlenecks.

10.4 Conclusion:

The purpose of a feasibility study is to assess the viability of a business proposition technically, operationally, and economically. The value chain framework has the unique advantage of laying out the project in its logical configuration from input procurement to customer service. The advantage is revealed in exposing bottlenecks along the value chain. The iterative nature allows the analyst to revisit previous steps when new information suggests the need.

The report should cover input sourcing, operations, warehousing, storage and delivery (logistics aspects), and marketing, sales and customer service (external domain). Pulling all information together into financial units, the analyst can build projections and estimate NPV and/or IRR. A project returning a positive NPV is deemed feasible. If the required rate of return is lower than the estimated IRR, the project is feasible.

⭐ Key Takeaways

The feasibility study is a critical decision-making tool that evaluates technical, operational, and economic viability before major resources are committed. The value chain approach provides a comprehensive framework that systematically assesses each stage from input sourcing to customer service, uncovering potential bottlenecks and ensuring all critical factors are considered. Bankers and financiers have specific requirements for feasibility studies, including a clear executive summary and financial package blueprint that demonstrate repayment ability and risk assessment. The ultimate decision hinges on financial metrics: a positive Net Present Value (NPV) or an Internal Rate of Return (IRR) exceeding the required rate of return indicates economic feasibility. Sensitivity analysis over worst, normal, and best-case scenarios is essential to understand how robust the project's viability is to changes in critical assumptions.

🧠 Quick Revision Questions

1. What are the two main types of feasibility that should be assessed in a feasibility study?
2. What are the key elements a banker wants to see in the executive summary of a feasibility study?
3. How does the value chain approach help in assessing project feasibility?
4. What is the primary advantage of using a Request for Quote (RFQ) for operations and production assessment?
5. What does a positive Net Present Value (NPV) indicate about a project's feasibility?

📘 Lecture 11 — Project Selection

📖 Overview: This lecture introduces the critical process of project selection, where organizations choose which projects to implement given limited resources. It covers the criteria for choosing project selection models, the nature of numeric and non-numeric models, and the fundamental decision-making framework that separates successful organizations from failing ones. Understanding these concepts is essential because poor project selection can mean the difference between organizational survival and failure.

🗂️ Topics Covered

This lecture begins with an introduction to project selection as the process of choosing projects to implement, explaining why it is vital for organizational success. It then covers project decisions, the nature of risk and uncertainty in these decisions, and the use of decision-aiding models. The lecture presents criteria for choosing project selection models including realism, capability, flexibility, ease of use, cost, and easy computerization. It examines the nature of project selection models, distinguishing between numeric and non-numeric types, and concludes with detailed explanations of five non-numeric models: Sacred Cow, Operating Necessity, Competitive Necessity, Product Line Extension, and Comparative Benefit Model.

📝 Lecture Summary

Introduction

Project selection is the process of choosing a project or set of projects to be implemented by the organization. Since projects require substantial investment in money and resources, both of which are limited, it is vital that selected projects provide good returns on resources and capital invested. This requirement must be balanced with the need for an organization to move forward and develop. The high level of uncertainty in the modern business environment has made this area of project management crucial to continued success, with the difference between choosing good projects and poor projects literally representing the difference between operational life and death.

Because a successful model must capture every critical aspect of the decision, more complex decisions typically require more sophisticated models. "There is a simple solution to every complex problem; unfortunately, it is wrong." This creates a major challenge for tool designers. Project decisions are often high-stakes, dynamic decisions with complex technical issues—precisely the kinds of decisions that are most difficult to model:

• Project selection decisions are high-stakes because of their strategic implications. The projects a company chooses can define the products it supplies, the work it does, and the direction it takes in the marketplace. Project decisions can impact every business stakeholder including customers, employees, partners, regulators, and shareholders. A sophisticated model may be needed to capture strategic implications.
• Project decisions are dynamic because a project may be conducted over several budgeting cycles, with repeated opportunities to slow, accelerate, re-scale, or terminate the project. Also, a successful project may produce new assets or products that create time-varying financial returns and other impacts over many years.
• Project decisions produce many different types of impacts on the organization. For example, a project might increase revenue or reduce future costs. It might impact how customers or investors perceive the organization. It might provide new capability or learning important to future success. Making good choices requires understanding all of the ways that projects add value.

💡 Why this matters: The high-stakes, dynamic, and multi-impact nature of project decisions means that simple models will fail to capture critical elements, potentially leading to disastrous choices.

Project Decisions

Project decisions often entail risk and uncertainty. The significance of a project risk depends on the nature of that risk and on the other risks the organization is taking. A more sophisticated model is needed to correctly deal with risk and uncertainty.

Project selection is the process of evaluating individual projects or groups of projects, and then choosing to implement some set of them so that the objectives of the parent organization will be achieved. This same systematic process can be applied to any area of the organization's business in which choices must be made between competing alternatives. Examples include:

• A manufacturing firm choosing which machine to adopt in a part-fabrication process
• A television station selecting which syndicated comedy show to rerun
• A construction firm selecting the best subset of potential projects on which to bid
• A hospital finding the best mix of beds for a new wing

Each project will have different costs, benefits, and risks. Rarely are these known with certainty. Choosing a number of different projects, a portfolio, is even more complex than selecting a single project.

To deal with these problems, we use decision aiding models. We need such models because they abstract the relevant issues about a problem from the plethora of detail in which the problem is embedded. This process of carving away the unwanted reality from the bones of a problem is called modeling the problem. The idealized version of the problem that results is called a model.

The model represents the problem's structure, its form. Models may be quite simple to understand, or they may be extremely complex. Introducing more reality into a model tends to make the model more difficult to manipulate. If input data are not known precisely, we often use probabilistic information; that is, the model is said to be stochastic rather than deterministic.

🔑 Definition — Model: An explicit statement of our image of reality. It is a representation of the relevant aspects of the decision with which we are concerned. It represents the decision area by structuring and formalizing the information we possess about the decision and, in doing so, presents reality in a simplified organized form. A model provides us with an abstraction of a more complex reality. (Cooke and Slack, 1991)

When project selection models are seen from this perspective, the need for them arises from the fact that it is impossible to consider the environment within which a project will be implemented in its entirety. The challenge for a good project selection model is to balance the need to keep enough information from the real world to make a good choice with the need to simplify the situation sufficiently to make it possible to come to a conclusion in a reasonable length of time.

Criteria for Choosing Project Model

When a firm chooses a project selection model, the following criteria based on Souder (1973) are most important:

1. Realism: The model should reflect the reality of the manager's decision situation, including the multiple objectives of both the firm and its managers. Without a common measurement system, direct comparison of different projects is impossible. The model should take into account the realities of the firm's limitations on facilities, capital, personnel, and so forth. The model should also include factors that reflect project risks, including technical risks of performance, cost, and time as well as market risks of customer rejection and other implementation risks.

2. Capability: The model should be sophisticated enough to deal with multiple time periods, simulate various situations both internal and external to the project (for example, strikes, interest rate changes), and optimize the decision. An optimizing model will make the comparisons that management deems important, consider major risks and constraints on the projects, and then select the best overall project or set of projects.

3. Flexibility: The model should give valid results within the range of conditions that the firm might experience. It should have the ability to be easily modified, or to be self-adjusting in response to changes in the firm's environment; for example, tax laws change, new technological advancements alter risk levels, and the organization's goals change.

4. Ease of Use: The model should be reasonably convenient, not take a long time to execute, and be easy to use and understand. It should not require special interpretation, data that are difficult to acquire, excessive personnel, or unavailable equipment. The model's variables should relate one-to-one with those real-world parameters the managers believe significant to the project. Finally, it should be easy to simulate the expected outcomes associated with investments in different project portfolios.

5. Cost: Data gathering and modeling costs should be low relative to the cost of the project and must surely be less than the potential benefits of the project. All costs should be considered, including the costs of data management and of running the model.

6. Easy Computerization: It should be easy and convenient to gather and store the information in a computer database, and to manipulate data in the model through use of a widely available, standard computer package such as Excel, Lotus 1-2-3, Quattro Pro, and like programs. The same ease and convenience should apply to transferring the information to any standard decision support system.

💡 Why this matters: These six criteria form the checklist against which any project selection model should be evaluated before adoption. A model that fails on any criterion may lead to poor decisions.

The Nature of Project Selection Models

There are two basic types of project selection models: numeric and nonnumeric. Both are widely used. Many organizations use both at the same time, or they use models that are combinations of the two. Nonnumeric models do not use numbers as inputs. Numeric models do, but the criteria being measured may be either objective or subjective. The qualities of a project may be represented by numbers, and subjective measures are not necessarily less useful or reliable than objective measures.

Two critically important facts must never be forgotten:

• Models do not make decisions—people do. The manager, not the model, bears responsibility for the decision. The manager may "delegate" the task of making the decision to a model, but the responsibility cannot be abdicated.
• All models, however sophisticated, are only partial representations of the reality they are meant to reflect. Reality is far too complex for us to capture more than a small fraction of it in any model. Therefore, no model can yield an optimal decision except within its own, possibly inadequate, framework.

A model should evaluate potential projects by the degree to which they will meet the firm's objectives. To construct a selection/evaluation model, it is necessary to develop a list of the firm's objectives, which should be generated by the organization's top management. The list should go beyond typical clichés about "survival" and "maximizing profits." Other objectives might include maintenance of share of specific markets, development of an improved image, expansion into a new line of business, decrease in sensitivity to business cycles, maintenance of employment for specific categories of workers, and maintenance of system loading at or above some percent of capacity.

When the list of objectives has been developed, each item should be weighted to reflect different degrees of contribution each element makes in accomplishing a set of goals. The probable contribution of each project to each of the goals should then be estimated. If the estimated level of goal achievement is sufficiently large, the project is selected; if not, it is rejected.

A major consulting firm (Booz, Allen, and Hamilton, 1966) argued that the primary cause for the failure of Research and Development (R and D) projects is insufficient care in evaluating the proposal before the expenditure of funds. Careful analysis of a potential project is a sine qua non (essential condition) for profitability.

Types of Project Selection Models

Of the two basic types of selection models (numeric and nonnumeric), nonnumeric models are older and simpler and have only a few subtypes:

Non-Numeric Models:

1. The Sacred Cow: In this case, the project is suggested by a senior and powerful official in the organization. Often the project is initiated with a simple comment such as, "If you have a chance, why don't you look into..." followed by an undeveloped idea. The immediate result is the creation of a "project" to investigate whatever the boss has suggested. The project is "sacred" in the sense that it will be maintained until successfully concluded, or until the boss personally recognizes the idea as a failure and terminates it.

2. The Operating Necessity: If a flood is threatening the plant, a project to build a protective dike does not require much formal evaluation. If the project is required to keep the system operating, the primary question becomes: Is the system worth saving at the estimated cost of the project? If the answer is yes, project costs will be examined to make sure they are kept as low as is consistent with project success, but the project will be funded.

3. The Competitive Necessity: Using this criterion, a firm undertakes a project because it is needed to maintain the company's competitive position in the market. For example, many business schools restructure their undergraduate and MBA programs to stay competitive with more forward-looking schools. Investment in an operating necessity project takes precedence over a competitive necessity project, but both types may bypass more careful numeric analysis used for less urgent projects.

4. The Product Line Extension: In this case, a project to develop and distribute new products is judged on the degree to which it fits the firm's existing product line, fills a gap, strengthens a weak link, or extends the line in a new, desirable direction. Sometimes careful calculations of profitability are not required. Decision makers can act on their beliefs about what will be the likely impact on total system performance.

5. Comparative Benefit Model: For this situation, assume an organization has many projects to consider but they are not easily comparable (e.g., potential new products, changes in production methods, computerization of records, creating a daycare center). The organization has no formal method of selecting projects, but members of the selection committee think some projects will benefit the firm more than others. The concept of comparative benefits is widely adopted for selection decisions on all sorts of projects. Most United Way organizations use this concept to make decisions about which social programs to fund. Senior management examines all projects with positive recommendations and attempts to construct a portfolio that best fits the organization's aims and its budget.

⭐ Key Takeaways

Project selection is a high-stakes, dynamic process that requires models to abstract reality while balancing simplification with sufficient complexity for good decision-making. The six critical criteria for choosing a project selection model are realism, capability, flexibility, ease of use, cost, and easy computerization. Models do not make decisions—people do, and all models are only partial representations of reality. There are two fundamental types of project selection models: numeric (using numbers as inputs) and nonnumeric (not using numbers as inputs). The five non-numeric models are Sacred Cow, Operating Necessity, Competitive Necessity, Product Line Extension, and Comparative Benefit Model—each with specific applications and levels of urgency. The primary cause for project failure is often insufficient care in evaluating the proposal before expenditure of funds.

🧠 Quick Revision Questions

1. What are the six criteria for choosing a project selection model according to Souder (1973)?
2. What is the fundamental difference between numeric and nonnumeric project selection models?
3. In the Sacred Cow model, what determines when a project is terminated?
4. How does an Operating Necessity project differ from a Competitive Necessity project in terms of priority?
5. Why is it critically important to remember that "models do not make decisions—people do"?

📘 Lecture 12 — Project Selection (Contd.)

📖 Overview: This lecture continues the discussion of project selection models, focusing on both non-numeric and numeric approaches. It covers the Q-Sort model for ordering projects, various profitability-based numeric models including payback period, average rate of return, discounted cash flow (NPV), and internal rate of return (IRR). The lecture also introduces the concept of project proposals, their types, and related procurement documents like RFPs, RFQs, and RFIs, which are essential for initiating and evaluating projects in organizational contexts.

🗂️ Topics Covered

The lecture covers the Q-Sort model as a non-numeric project selection technique, followed by detailed explanations of numeric profitability models: payback period, average rate of return, discounted cash flow (NPV), internal rate of return (IRR), and profitability index. It also discusses advantages and disadvantages of profit-profitability models, introduces the real options approach, and provides a comprehensive overview of project proposals including types (internal, external, solicited, unsolicited), the Request for Proposal (RFP) process, and variations like RFQ and RFI.

📝 Lecture Summary

12.1 Types of Project Selection Models (Continued):

Non-Numeric Models: Q-Sort Model

The Q-Sort model is a straightforward technique for ordering projects. First, projects are divided into three groups—good, fair, and poor—according to their relative merits. If any group has more than eight members, it is subdivided into two categories (e.g., fair-plus and fair-minus). When all categories have eight or fewer members, the projects within each category are ordered from best to worst based on relative merit.

The rater may use specific criteria or general overall judgment to rank each project. This process can be carried out by one person or by a committee. If a committee handles the task, individual rankings can be developed anonymously, and the set of anonymous rankings can be examined by the committee for consensus. Rankings rarely vary strikingly because committee members rarely differ widely on what is appropriate for the parent organization.

Projects can be selected in order of preference, though they are usually evaluated financially before final selection. While it is easy to dismiss nonnumeric models as unscientific, they should not be discounted casually as they are clearly goal-oriented and directly reflect the primary concerns of the organization. The sacred cow model has an added feature—sacred cow projects are visibly supported by top management, and full support by top management is an important contributor to project success.

Numeric Models: Profit/Profitability

A large majority of firms using project evaluation and selection models use profitability as the sole measure of acceptability.

1. Payback Period: The payback period for a project is the initial fixed investment in the project divided by the estimated annual net cash inflows from the project. The ratio gives the number of years required for the project to repay its initial fixed investment.

📐 Formula: Payback Period = Initial Fixed Investment / Annual Net Cash Inflows

📌 Example: Assume a project costs $100,000 to implement and has annual net cash inflows of $25,000. Then: Payback Period = $100,000 / $25,000 = 4 years.

This method assumes that cash inflows will persist at least long enough to pay back the investment, and it ignores any cash inflows beyond the payback period. The method also serves as an inadequate proxy for risk—the faster the investment is recovered, the less the risk to which the firm is exposed.

2. Average Rate of Return: The average rate of return is the ratio of the average annual profit (either before or after taxes) to the initial or average investment in the project. Because average annual profits are usually not equivalent to net cash inflows, the average rate of return does not usually equal the reciprocal of the payback period.

📐 Formula: Average Rate of Return = Average Annual Profit / Initial or Average Investment

📌 Example: Using the same $100,000 project, assume average annual profits are $15,000. Then: Average Rate of Return = $15,000 / $100,000 = 15%.

Neither payback period nor average rate of return is recommended for project selection. The major advantage of these models is their simplicity, but neither takes into account the time-value of money. Unless interest rates are extremely low and the rate of inflation is nil, failure to reduce future cash flows or profits to their present value will result in serious evaluation errors.

3. Discounted Cash Flow (Net Present Value - NPV): Also referred to as the Net Present Value (NPV) method, the discounted cash flow method determines the net present value of all cash flows by discounting them by the required rate of return (also known as the hurdle rate, cutoff rate, etc.).

📐 Formula: NPV = Σ [Rt / (1 + k + pt)^t] - A0, where: Rt = expected cash inflow in period t, k = required rate of return, pt = predicted rate of inflation during period t, and A0 = initial investment.

📌 Example: Using a $100,000 investment with net cash inflow of $25,000 per year for 8 years, a required rate of return of 15%, and an inflation rate of 3% per year:

• Present value of inflows = $117,280
• Present value of outflow = -$100,000
• Net present value = $17,280

Because the net present value is positive, the project is deemed acceptable.

Detailed Example - PsychoCeramic Sciences, Inc. (PSI): PSI is considering installing a new marketing software package. The investment requirements include:

• $125,000 upfront to Pottery Software Corporation
• $100,000 to modify and install the software
• $90,000 to integrate into the overall information system

Delivery and installation takes one year; integration requires an additional year. Scheduled software updates require $15,000 every second year beginning in the fourth year (not updated in the last year). Projected additional profits start at $50,000 in the first year of operation, peak at $120,000 in the second year, then gradually decline. Project life is 10 years with a salvage value of $35,000. The company has a 12% hurdle rate and expects 3% inflation.

The Net Present Value analysis shows a positive NPV, so the project can be accepted. (The project would have been rejected if the hurdle rate were 14%). The total inflow is $759,000, or $75,900 per year on average. The required investment is $315,000. Assuming straight line depreciation of $31,500 per year, the payback period would be: $315,000 / ($75,900 + $31,500) = 2.93 years.

💡 Why this matters: The NPV method properly accounts for the time value of money, inflation, and provides a clear go/no-go decision based on whether the net present value is positive.

4. Internal Rate of Return (IRR): The Internal Rate of Return is the discount rate that equates the present values of expected cash inflows and expected cash outflows.

📐 Formula: Σ [Rt / (1 + k)^t] = Σ [At / (1 + k)^t], where At is expected cash outflow in period t, Rt is expected inflow for period t, and k is the internal rate of return (found by trial and error).

5. Profitability Index: Also known as the benefit-cost ratio, the profitability index is the net present value of all future expected cash flows divided by the initial cash investment. If this ratio is greater than 1.0, the project may be accepted.

6. Other Profitability Models: These variations fall into three general categories: a) Those that subdivide net cash flow into the elements that comprise the net flow. b) Those that include specific terms to introduce risk into the evaluation. c) Those that extend the analysis to consider effects on other projects or activities.

12.1.1 Advantages of Profit-Profitability Numeric Models:

• Undiscounted models are simple to use and understand.
• All use readily available accounting data to determine cash flows.
• Model output is in terms familiar to business decision makers.
• With few exceptions, model output is on an absolute profit/profitability scale allowing absolute go/no-go decisions.
• Some profit models account for project risk.

12.1.2 Disadvantages of Profit-Profitability Numeric Models:

• These models ignore all non-monetary factors except risk.
• Models without discounting ignore the timing of cash flows and the time-value of money.
• Models that reduce cash flows to present value are strongly biased toward the short run.
• Payback-type models ignore cash flows beyond the payback period.
• The internal rate of return model can result in multiple solutions.
• All are sensitive to errors in input data for early years of the project.
• All discounting models are nonlinear, and effects of changes or errors are generally not obvious.
• All depend on determining cash flows, but it is not clear how cash flow is properly defined for evaluating projects.

12.1.3 Profit-Profitability Numeric Models – An Overview:

In general, net present value models are preferred to internal rate of return models. The commonly seen phrase "Return on Investment" (ROI) does not denote any specific method of calculation—it usually involves NPV or IRR calculations but is also used for undiscounted average rate of return models and (incorrectly) payback period models.

The payback period model, occasionally using discounted cash flows, is one of the most commonly used models for evaluating projects. Managers generally feel that insistence on short payout periods tends to minimize risks associated with outstanding monies over time.

Real Options: A project selection model based on the notion that when one invests, one foregoes the value of alternative future investments (the opportunity cost). A project may have greater net present value if delayed to the future because uncertainties will be reduced. The real options approach acts to reduce both technological and commercial risk.

12.2 Introduction to Project Proposal:

A Project Proposal is the initial document that converts an idea or policy into details of a potential project, including outcomes, outputs, major risks, costs, stakeholders, and an estimate of resource and time required. A proposal is an offer or bid to do a certain project for someone. What makes a proposal a proposal is that it asks the audience to approve, fund, or grant permission to do the proposed project.

A proposal should contain information that enables the audience to decide whether to approve the project, approve hiring you to do the work, or both. To write a successful proposal, put yourself in the place of your audience and think about what information that person would need to feel confident having you do the project.

Proposals are different from feasibility reports. A feasibility report studies the merits of a project and recommends for or against it. A proposal asks management for approval to go ahead with the project.

12.3 Types of Project Proposals:

1. Internal Proposal: Written to someone within your organization (a business, government agency, etc.). With internal proposals, you may not have to include certain sections or as much information.

2. External Proposal: Written by a separate, independent consultant proposing to do a project for another firm. It can be a proposal from one organization or individual to another such entity.

3. Solicited Proposal: The recipient in some way requested the proposal. Typically, a company will send out Requests for Proposals (RFPs) through the mail or publish them in news sources. Proposals can also be solicited at a local level, such as when a boss asks an employee to write up a proposal.

4. Unsolicited Proposal: The recipient has not requested proposals. With unsolicited proposals, you sometimes must convince the recipient that a problem or need exists before you can begin the main part of the proposal.

12.3.1 Request for Proposal (RFP):

A Request for Proposal (RFP) is an invitation for suppliers, through a bidding process, to submit a proposal on a specific product or service. An RFP typically involves more than just price. Other requested information may include:

• Basic corporate information and history
• Financial information (can the company deliver without risk of bankruptcy)
• Technical capability
• Product information such as stock availability and estimated completion period
• Customer references

In the military, an RFP is often raised to fulfill an Operational Requirement (OR). In civilian use, RFP is usually part of a complex sales process known as enterprise sales. RFPs often include specifications of the item, project, or service. Generally, RFPs are sent to an approved supplier or vendor list. Bidders return proposals by a set date and time. The proposals are used to evaluate suitability as a supplier, vendor, or institutional partner. Discussions may be held, and selected bidders may be asked to submit their Best and Final Offer (BAFO).

12.3.2 RFP Variations:

Request for Quotation (RFQ): Used where discussions are not required with bidders (mainly when specifications are already known), and price is the main or only factor in selecting the successful bidder. RFQ may also be used as a step prior to going to a full-blown RFP to determine general price ranges.

12.3.3 Request for Information (RFI):

A Request for Information (RFI) is a proposal requested from a potential seller or service provider to determine what products and services are potentially available in the marketplace to meet a buyer's needs and to know the capability of a seller. RFIs are commonly used on major procurements. An RFI is not an invitation to bid, is not binding on either party, and may or may not lead to an RFP or RFQ.

⭐ Key Takeaways

Project selection models fall into two main categories: non-numeric (like Q-Sort and sacred cow) and numeric profitability models (payback period, average rate of return, NPV, IRR, and profitability index). The Q-Sort model organizes projects into good, fair, and poor groups based on relative merit. Payback period and average rate of return are simple but fail to account for the time value of money. Discounted cash flow (NPV) is preferred over IRR because it properly accounts for the time value of money and avoids multiple solution problems. A project proposal is a formal document asking for approval to undertake a project, and it differs from a feasibility report. Proposals can be internal/external and solicited/unsolicited, with RFPs being formal invitations for suppliers to bid on specific products or services.

🧠 Quick Revision Questions

1. What is the Q-Sort model and how does it categorize projects?
2. How is payback period calculated, and what are its major limitations?
3. What is the formula for Net Present Value, and how is the inflation rate incorporated?
4. What distinguishes a project proposal from a feasibility report?
5. What are the differences between an RFP, RFQ, and RFI in the procurement process?

📘 Lecture 13 — Project Proposal

📖 Overview: This lecture provides a comprehensive overview of project proposals, covering their key characteristics, preparation strategies, and the specific activities involved in developing them. It details the essential components of a typical Engineering, Procurement and Construction (EPC) proposal and discusses necessary modifications to standard proposal formats to meet specific owner requirements. Understanding this lecture is critical for successfully initiating, structuring, and winning project bids.

🗂️ Topics Covered

This lecture begins by outlining the seven key characteristics of a project proposal, including its high-priority, short-duration nature and the need to adhere to owner specifications. It then details the preparatory work for future proposals, such as establishing a data bank and pre-writing standard sections. The specific proposal effort process is explained, covering steps from preliminary assignments to final delivery. The typical contents of an Engineering, Procurement and Construction (EPC) proposal are broken down, from the introduction to qualifications. Finally, the lecture discusses the necessity of modifying standard proposals to comply with specific owner formats.

📝 Lecture Summary

13.1 Characteristics of a Project Proposal:

A project proposal is a high-stakes, time-sensitive undertaking. These projects are high priority, short duration efforts that must meet the owner's schedule, often under heavy workload. The proposal must adhere to the owner's specifications for payment methods, format, and preferred project location, though contractors may suggest alternatives. The owner may also have preferences for the construction labor arrangement. A successful proposal requires forming a cross-functional team from sales, project management, and technical support. These proposal projects are normally costed against corporate overhead, making them tightly budgeted and closely monitored by senior management.

🔑 Definition — Proposal Project: High priority, short duration efforts that must be completed to the owner's schedule, regardless of other demands.

13.2 Preparation for Future Proposals:

To manage the repetitive nature and tight budgets of proposals, companies should collect information in advance. This includes identifying a proposal project manager—someone with verbal skills and tolerance for tight schedules and criticism. A dedicated proposal publication staff with editing and graphic art skills should be in place. Essential pre-built resources include a technical information data base of past projects, standard scope of services that can be customized, and comprehensive definitions for cost estimate levels. Work plans for basic project types and a data bank of standard commercial terms and overhead costs are also vital. Finally, qualification material—such as past project data, personnel resumes, and descriptions of support areas like project controls and quality assurance—should be updated frequently and maintained in standard formats.

🔑 Definition — Proposal Publication Staff: Individuals with skills in editing, word processing, reproduction, and graphic art to manage the production of proposal materials.

13.3 Proposal Effort for Specific Proposals:

Effort begins as soon as there is a positive indication the company will be on the bid list. Early steps include making preliminary assignments for the proposal project manager, the proposed project manager, and technical staff. A preliminary proposal plan, schedule, and budget should be developed. A rigorous assessment of the company's strengths and weaknesses regarding the project's technical aspects must be made, with immediate actions planned to boost capability. Finally, when the formal Request for Proposal (RFP) is received, it is reviewed, and a bid/no bid decision is made.

🔑 Definition — Preliminary Proposal Plan: A document that defines the outline of the proposal and the preliminary assignment of work.

13.4 Proposal Effort:

Once the decision to bid is confirmed, the proposal effort becomes a structured process. First, the assignment of team members is finalized. The proposal manager then calls a kick-off meeting to assign tasks, review technical and legal considerations, and set schedules. A preliminary review of the proposal text is conducted on typed drafts to check for omissions. A final review is submitted to operations management and legal, with all major changes flagged for quick approval. The process concludes with publication and signoff, followed by the delivery of the proposal to the owner.

📌 Example: A proposal for a new chemical plant. After the bid decision is confirmed, the project manager holds a kick-off meeting. At this meeting, the lead engineer is assigned to write the "Scope of Services," the scheduler to create the "Work Plan," and the controller to prepare the "Cost Estimates," each with a deadline for their draft.

13.5 Typical Engineering Procurement and Construction (EPC) Proposal Contents:

The standard contents of a cost-reimbursable EPC proposal are structured to provide a complete picture. The Introduction and Summary outlines the RFP conditions and the contractor's general approach. The Project Description summarizes the project from the RFP and any additional site visit information. The Scope of Services details all services the contractor will provide and all deliverables. The Work Plan and Schedule shows the interrelationship of project activities. The Project Organization describes the team structure and responsibilities, often with an organizational chart. The Estimates, Hours, and Costs section presents all direct and indirect cost estimates. The Compensation section finalizes commercial terms, including burdens, contingencies, and fees. Finally, the Qualifications section builds the owner's confidence by presenting relevant, accurate, and forceful examples of the contractor's past performance and capabilities.

🔑 Definition — Work Plan and Schedule: A section of the proposal that presents the project work plan in response to the owner's objectives, often in a graphic form showing the interrelationship of activities.

13.6 Modifications to the Standard Proposal:

Many owners have a very specific format for proposals. When this is the case, the contractor must depart from its standard proposal format. It is best to follow the specified format exactly, as this simplifies the proposal evaluation process for the owner's office and demonstrates responsiveness.

💡 Why this matters: Even with a well-developed standard proposal, failing to comply with an owner's specific format can lead to disqualification, regardless of the proposal's technical merit. Adhering to the owner's request is a fundamental sign of professionalism.

🔑 Definition — Owner's Specified Format: A unique format for a proposal requested by an owner, which must be followed by the contractor to simplify the owner's evaluation process.

⭐ Key Takeaways

A project proposal is a distinct, high-priority, and short-duration project in itself, requiring a dedicated team and tight budget controls that are monitored by senior management. To be efficient, a company must prepare in advance by building a robust data bank of reusable information, including standard scopes, work plans, and qualification material. The specific proposal effort follows a clear, sequential process, beginning with preliminary assignments and a bid/no-bid decision, and proceeding through a kick-off meeting, text reviews, and final publication and delivery. The standard EPC proposal must include eight essential sections, from the introduction and scope of services to cost estimates, compensation, and qualifications. Finally, while a standard proposal structure is a necessary foundation, it must always be modified to comply with any specific format required by the owner to ensure a fair evaluation.

🧠 Quick Revision Questions

1. What are the seven key characteristics of a project proposal?
2. What are the three most important items to prepare in advance for future proposals to improve efficiency and quality?
3. List the six steps in the specific proposal effort process, starting from the decision to bid.
4. What are the eight typical sections of an Engineering, Procurement and Construction (EPC) proposal?
5. Why is it important to follow a specific format if an owner requires one, rather than using the contractor's standard proposal format?

📘 Lecture 14 — Project Proposal (Contd.)

📖 Overview: This lecture continues the discussion on project proposals, focusing on the common sections found in proposals, how to organize winning proposals, various proposal formats, and practical tips for writing and presenting proposals effectively. It provides a comprehensive guide for creating persuasive and professional proposals that stand out to clients.

🗂️ Topics Covered

This lecture covers the ten common sections found in proposals, including introduction, background, benefits, work description, methodology, schedule, qualifications, costs, conclusions, and special sections. It then explains the logical organization of winning proposals with a step-by-step sequence, followed by various proposal formats like cover letter, memo, business letter, and memo proposals. The lecture concludes with key ingredients for winning proposals and ten practical tips for writing and presenting proposals effectively.

📝 Lecture Summary

Common Sections in Proposals

A review of sections commonly found in proposals is presented. It is important to note that not every section must be included, nor do they have to be in the order presented, and other information may be required.

1. Introduction: The introduction must be planned carefully to indicate that the document is a proposal, refer to previous contact or sources of information, provide a brief motivating statement to encourage reading, and give an overview of the proposal's contents. It should be brisk and to the point.

2. Background on the Opportunity: This section discusses what has brought about the need for the project, such as the problem or opportunity for improvement. Even if the audience knows the problem, writing this section demonstrates your particular view. For unsolicited proposals, this section is almost a requirement to convince the audience the problem exists.

3. Benefits and Feasibility of the Proposed Project: This section discusses the advantages or benefits of doing the project, acting as an argument for approval. It also discusses the likelihood of the project's success, such as exploring the return on investment. In unsolicited proposals, this section is particularly important for "selling" the project.

4. Description of the Proposed Work (Results of the Project): This section describes the finished product of the proposed project, including the written document, its audience and purpose, an outline, length, graphics, and binding. Other work like training seminars or ongoing services should also be included.

5. Method, Procedure, Theory: This section explains how the work will be done if approved, acting as an additional persuasive element showing a sound approach. It covers the technical background relating to procedures or technology, giving the writer a chance to demonstrate expertise and build confidence.

6. Schedule: Most proposals include a section showing the projected completion date and key milestones. For large projects, the timeline includes dates for progress reports. If specific dates cannot be given, time spans for each phase should be cited.

7. Qualifications: This section provides a summary of the proposing individual's or organization's qualifications, acting as a mini-resume. It lists work experience, similar projects, references, training, and education to show familiarity with the project.

8. Costs, Resources Required: This section details the costs of the project, whether internal or external. For external projects, it lists hourly rates, projected hours, equipment costs, supplies, and the total cost. For internal projects, it lists hours, equipment, supplies, and assistance from others.

9. Conclusions: The final section brings readers back to focus on the positive aspects of the project after showing them the costs. It urges them to get in touch, reminds them of benefits, and makes one last plug for the proposer as the right choice.

10. Special Project-Specific Sections: Some proposals may require other sections not discussed above. Always ask what else the audience needs to understand the project, the need for it, the benefits, the proposer's role and qualifications, and what is needed for approval.

Organization of Winning Proposals

The proposal is essentially a sales or promotional document. The basic steps are:

1. Introduce the proposal, telling the readers its purpose and contents.
2. Present the background – the problem, opportunity, or situation.
3. State what you propose to do about the problem.
4. Discuss the benefits of doing the proposed project.
5. Describe exactly what the completed project would consist of.
6. Discuss the method and theory behind the approach.
7. Provide a schedule, including major milestones.
8. Briefly list your qualifications for the project.
9. List the costs of the project and resources needed.
10. Conclude with a review of the benefits and urge acceptance.

🔑 Definition — Story Board: A technique employing modules organized for each strategic message intended for the proposal. Each module is composed of a topical sentence, a theme expressing the strategic message (400-800 words), and graphics or artwork to illustrate the theme. This technique permits early organization, continuous management overview, and produces balanced content.

The overall logic is to get the audience concerned about a problem, excited about how you will fix it, show good qualifications, then hit them with costs, and come back to the good points.

Format Of Proposals

Various formats are available, using memorandum format for internal proposals and business letter format for external proposals.

• Cover Letter With Separate Proposal: A brief cover letter announces the proposal and outlines its contents, with the proposal proper attached. The letter may get detached, so the proposal repeats much of the content.
• Cover Memo with Separate Proposal: Similar to the cover letter format, but uses a memo for internal proposals.
• Business-Letter Proposal: The entire proposal is within a standard business letter, including headings and special formatting.
• Memo Proposal: The entire proposal is within a standard office memorandum, including headings and special formatting.

In competitive bid situations, price, schedule, financial stability, quality of experience, resources, and financing are relevant. Contract awards are often made on a negotiated basis, where interpersonal relationships and the written word in the proposal are crucial.

The seven key ingredients of a winning proposal are: i) Message: Understanding the project, the owner's real wants, and how to satisfy them. ii) Response: Complete and direct response to the Request for Proposal (RFP) or bidding documents. iii) Disclosure: Comprehensive documentation of all relevant company experience. iv) Creativity: Something unique or innovative to set the proposer apart. v) Price: Usually a significant factor in competitive proposals. vi) Financing: An important consideration, often required; bids are adjusted by financing terms. vii) Style: Well composed, concisely written, logically organized, properly referenced, and attractively presented.

Typical evaluation criteria for RFPs may include a point distribution:

• Qualification of proposed personnel, particularly the project manager: Up to 50%
• Experience on similar projects: Range of 25-35%
• Proposed work plan and approach: Range of 25-35%

📐 Formula: Evaluation Criteria Points → Points are awarded in selected categories to determine the winning proposal. If criteria are specified, every effort should be made to achieve the maximum possible score.

Some Tips for Writing and Presenting Proposals

Tried and tested tips to encourage proposal writing and improve success rates.

1. Ask Questions: Before starting, make sure you know exactly what you are proposing. Ask potential clients meaningful questions for clarification. Include an educated guess with your questions and make it clear your price is based on correct guesses.

2. Summarize the Project: Take all received information and summarize it briefly in your own words. This helps clarify the concept in your mind and gives the client confidence that you understand their needs.

3. Break Down the Project into a Nice “To Do” List: Follow the summary with a solid "To Do" list listing everything requested and your standard work. This gives the client a strong sense of competence and helps ensure nothing is missed.

4. Split the Project into Phases: Split the project into clearly defined phases, starting with a minimum of three (e.g., Initial First Draft, Bug Squashing and Customizing, Finalization). Pricing each phase individually is useful for isolating features requiring additional time and energy.

5. Give Your Clients a Timeline: Let clients know approximately how long the project will take. Be generous (overestimate) and strive to finish ahead of time. Account for waiting time between drafts.

6. Estimate Your Time Involved: Give an estimate of time involved for most project types. For large projects with high dollar amounts, detail the hours involved in each step of the to-do list.

7. Use the Multiple Choice Price Strategy: Calculate predicted time and your hourly rate, then offer both the total hourly rate and a discounted flat rate. Most clients will choose the flat rate and be happy with the freedom to choose.

8. Offer a Satisfaction Guarantee: Let clients know you are committed to working until they are fully satisfied. A solid guarantee gives clients extra confidence and helps close the deal.

9. End With a Call to Action: Let clients know exactly what they need to do to get started, including where to send payment if required upfront.

10. Write and Format Professionally: Proofread for misspellings and grammatical errors. Use spacing between paragraphs and divide sections with subheadings. For extra points, put the proposal on a password-protected page within your website.

Two additional tips include pre-screening clients through your website with clear processes and prices, and responding quickly to prospective and active clients.

⭐ Key Takeaways

The most critical elements for exam preparation are understanding the ten common sections in proposals and their strategic order, particularly how to organize a winning proposal as a persuasive sales document that logically moves from problem identification through benefits, qualifications, costs, and conclusion. Students must memorize the seven key ingredients of a winning proposal (Message, Response, Disclosure, Creativity, Price, Financing, Style) and the typical evaluation criteria point distribution. The various proposal formats, especially using memorandum for internal and business letter for external proposals, along with practical tips like the multiple choice price strategy and satisfaction guarantee, are essential for constructing effective proposals.

🧠 Quick Revision Questions

1. What are the ten common sections found in proposals, and what is the strategic logic behind their organization in a winning proposal?
2. List and explain the seven key ingredients of a winning proposal.
3. What are the four main proposal formats, and which format should be used for internal versus external proposals?
4. Describe the "story board" technique and its components. What are its benefits for proposal preparation?
5. What is the multiple choice price strategy, and how does offering a satisfaction guarantee help close the deal?

📘 Lecture 15 — Project Planning

📖 Overview: This lecture introduces the fundamental concepts and techniques of project planning, emphasizing its role as a roadmap from idea to accomplishment. It covers the essential elements of a systematic plan, the required information for effective planning, and the early-stage documentation a project manager must prepare to ensure project success.

🗂️ Topics Covered

The lecture covers the introduction to project planning as an iterative process, the core components and requirements of project planning including the statement of work and work breakdown structure, the detailed plan of execution and its role in communication and scheduling, the specific information required from planning execution, early-stage documentation like coordination procedures and early work schedules, and concludes with an example of common activities in each project phase using the construction of a house.

📝 Lecture Summary

15.1 Introduction

Planning is done to facilitate later accomplishment. Project planning is a complicated process, and planning acts as a map of this process. This map must have sufficient detail to determine what must be done next but be simple enough that workers are not lost in a welter of minutiae. Almost all project planning techniques lead to plans that contain the same basic elements, differing only in how they approach the planning process. At its best, planning is tortuous and an iterative process yielding better plans from not-so-good plans, with improvement taking place in fits and starts.

15.2 Project Planning

To do successful project management, it must utilize effective planning techniques, and the quantitative and qualitative tools for project planning must be identified. A systematic plan is required in which the entire company is considered as one large network that is further subdivided into smaller ones. The first step in total program scheduling is to understand the project objectives, which may include developing expertise in a given area, becoming competitive, modifying an existing facility, or keeping key personnel employed.

🔑 Definition — Statement of Work (SOW): A narrative description of the work to be accomplished, including the objectives of the project, a brief description of the work, the funding constraint if one exists, and the specifications and schedule.

Once the objectives are clearly defined, four questions must be considered: i) Which functional divisions will assume responsibility for accomplishment of these objectives and the major-element work requirements? ii) The required corporate and organizational resources available? iii) What are the major elements of the work required to satisfy the objectives, and how are these elements interrelated? iv) What are the information flow requirements for the project?

Unless all necessary information becomes available at project initiation, effective total program planning cannot be accomplished. These information requirements are:

• The statement of work (SOW)
• The project specifications
• The milestone schedule
• The work breakdown structure (WBS)

A schedule is a "gross" schedule and includes such things as the start date, end date, major milestones, and written reports (data items).

15.3 Planning of Execution

A detailed, written, “Plan of Execution (P of E)” for a project is drawn up once project viability has been established and the decision to proceed has been made. This plan must show: a) Who is to do what b) When c) How d) Major decisions requirements

It is essential that the project objectives must be clearly tied to the overall mission of the firm. Senior management defines a firm’s intent in undertaking the project, the scope of the project, and the project's desired results. In this regard, the Plan of Execution:

• Becomes a vehicle for communication with all stakeholders
• Becomes a prerequisite for detailed scheduling of work
• Helps documentation for preparation of “cost estimates”

Project management plans are more comprehensive than either management plans or project plans. The project management plan is a combination of two plans: the traditional management plan, which describes operational management systems and approaches, and the project plan, which includes the work breakdown structure (WBS), logic, schedules, and cost estimates.

15.4 Information Required From Planning of Execution

Following information is required:

1. Type of project
2. Its capacity and location(s)
3. Scope of work to be performed
4. Preliminary cost estimation
5. Site visitation report
6. Preliminary schedule of major objectives
7. Pertinent contract requirements
8. Special design and/or construction requirements
9. Climate restrictions
10. Environmental study, feasibility study reports, etc
11. Proposal document

The basis for the Project Manager’s planning endeavors for the planning of execution includes existing documents, the client’s inquiry, the proposal (as modified/amended in negotiation period), and the contract and preliminary work plans (during proposal preparation). Before execution planning, the project manager is required to provide the complete scope definition of work. Planning of Execution provides the basis to schedules, detailed cost estimation, control budget, and quality and performance assurance program. It leads to develop Work Breakdown Structure and integrates work schedule costs into a trackable and controllable program. During this phase, performance baselines are also estimated during project planning.

15.5 Early Stage Documentation by Project Manager

This includes:

1. Coordination Procedure (CP): Also known as Job Instructions, it includes administrative procedures in projects.
2. Early Work Schedule (EWS): This helps in tracking activities requiring immediate action and cannot wait for the release of formal schedules. Early Work Schedule (EWS) contains: a) Running list of activities started early b) Name of responsible individuals c) Completion date of an activity.

15.5.1 Emphasis Placed on Early Planning

Planning does not stop with the initial plan. It is a continuous process which is fine-tuned whenever necessary. Many events can potentially adversely affect or disrupt plan targets. In this regard, many times, corrective actions will be required to restore the integrity of the schedule and the budget.

💡 Why this matters: Early planning is not a one-time event; it requires continuous monitoring and adjustment to correct course deviations before they cause major project failure.

15.6 Example of Building House to Common “Activities in Each Phase” of Project Planning

1. Definition Phase: Problem defined in request document. Example: House needs heating, plumbing, lighting, storage, etc.
2. Analysis Phase: Produces functional specifications (deliverable). Example: Location of ventilators, air conditioner, outlet for phone, etc.
3. Design Phase: System proposed to solve problem; system divided into functional components; components are interconnected. Expectation: Rooms, ventilation, wiring, etc.
4. Programming Phase: Actual work conducted to bring system into being. Expected: Building of house.
5. System Test Phase: Brings pieces together and tests them as a whole. House Example: Test plumbing, electricity, roof, etc.
6. Acceptance Phase: Customer tests complete system for acceptance/payment. Minor problems are fixed (e.g., house buyers ask for repairs to cracked plaster or an outlet). Major problems require negotiation (e.g., two fireplaces vs. one built).
7. Operations, Installation and Use: House buyer moves in and lives in the house. Problems developed/found upon use are fixed during the warranty period. Not included in this phase are maintenance, upgrades, and extensions.

⭐ Key Takeaways

Project planning is an iterative, continuous process that creates a roadmap from idea to accomplishment, requiring a systematic plan that subdivides the entire company into networks. Key information requirements for planning include the Statement of Work, project specifications, milestone schedule, and Work Breakdown Structure, while the Plan of Execution serves as a communication tool defining who does what, when, and how. Early documentation like Coordination Procedures and Early Work Schedules is critical for tracking immediate actions before formal schedules are released, and performance baselines are established during planning. Effective planning requires constant monitoring and corrective action to restore schedule integrity and budget when disrupted by unforeseen events. Finally, a project progresses through distinct phases—definition, analysis, design, programming, system test, acceptance, and operations—each with specific deliverables and expectations, as demonstrated by the house-building example.

🧠 Quick Revision Questions

1. What are the four essential information requirements that must be available at project initiation for effective total program planning?
2. What four key elements must a detailed, written "Plan of Execution (P of E)" show?
3. What are the two specific components of early-stage documentation that a project manager must prepare?
4. According to the house-building example, what type of problem requires negotiation during the Acceptance Phase?
5. What is the Statement of Work (SOW), and what key elements does it include?

📘 Lecture 16 — Project Planning (Contd.)

📖 Overview: This lecture continues the discussion on project planning, focusing on the general planning process, the crucial role of initial project coordination, and a detailed project planning checklist. It explains the core components of a plan, how to align project objectives with the firm's mission, and the specific planning needs for different operational areas.

🗂️ Topics Covered

The lecture covers the nine major components of the planning phase (objective, program, schedule, budget, forecast, organization, policy, procedure, standard), the logic and questions behind effective planning, procedures to assist project managers, and the process of initial project coordination. It also details the specific planning considerations for outside clients and provides a comprehensive project planning checklist for construction, procurement, engineering, quality control, and financial planning.

📝 Lecture Summary

16.1 Steps in General Planning Process:

In simple terms, planning is determining what needs to be done, by whom, and by when, in order to fulfill one's assigned responsibility. There are nine major components of the planning phase: Objective (a goal to be achieved), Program (the strategy to be followed), Schedule (a plan for when activities will be done), Budget (planned expenditures), Forecast (a projection of future events), Organization (design of positions and responsibilities), Policy (a general guide for decision making), Procedure (a detailed method for carrying out a policy), and Standard (a level of acceptable performance).

Forecasting what will happen may not be easy, especially if predictions of environmental reactions are required. Planning is customarily defined as strategic (5+ years), tactical (1-5 years), or operational (6 months to 1 year). Forecasting requires an understanding of strengths and weaknesses in areas like competition, marketing, R&D, production, finance, personnel, and management structure.

Because of their uniqueness, policies, procedures, and standards can vary from project to project. Policies are predetermined general courses or guides based on principles such as being supplementary to superior policies, definable, understandable, flexible, and stable. Procedures can be drastically different from project to project, even for the same activity.

Planning varies at each level of the organization. At the working group or functional level, planning must include agreement on purpose, assignment of responsibilities, and coordination. At the organizational or project level, planning must include recognition of group conflict and assignment of group responsibilities.

The logic of planning requires answers to questions like: "Where are we?", "Where would we like to be?", "What might prevent us from getting there?", and "Are we on course?". One of the most difficult activities is to keep the planning on target.

🔑 Definition — Planning: Determining what needs to be done, by whom, and by when, in order to fulfill one's assigned responsibility.

🔑 Definition — Policy: A general guide for decision making and individual actions, based on principles like being definable, understandable, flexible, and stable.

📌 Example: The signing off of manufacturing plans may require different signatures on two selected projects even though the same end-item is being produced, illustrating how procedures can differ drastically from project to project.

💡 Why this matters: Understanding the nine components and the logical flow of planning ensures that all aspects of a project are considered before action is taken, reducing the risk of failure.

16.2 Initial Project Coordination:

It is crucial that a project's objectives be clearly tied to the overall mission of the firm. Senior management should define the firm’s intent, outline the scope, and describe the project’s desired results. Without a clear beginning, project planning can easily go astray. An initial coordinating meeting, attended by senior management, is vital to symbolize top management’s commitment.

At the beginning of this meeting, the project is discussed in sufficient detail so potential contributors develop a general understanding of what is needed. The outcome must be that technical objectives are established, basic areas of performance responsibility are accepted, and tentative schedules and budgets are spelled out.

After the meeting, these preliminary plans are reviewed by groups and combined into a composite project plan. This composite plan is approved by each participating group, the project manager, and then by senior organizational management. Once senior management has endorsed it, any further changes must be made by processing a formal change order.

It is generally the responsibility of the project manager to gather necessary approvals and assure that any changes incorporated into the plan at higher levels are communicated to, and approved by, units that have already signed off. Violation of this procedure is considered a betrayal of trust.

🔑 Definition — Project Plan (Master Plan/Baseline Plan): The final, approved result of the planning procedure, after all approvals from groups, project manager, and senior management.

📌 Example: In a firm designing a line of children's clothing, changes were made at a higher level without communicating to the functional units. This betrayal of trust was so severe that two chief designers resigned and took jobs with competitors.

16.2.1 Outside Clients:

When a project is to deliver a product/service (often referred to as project's deliverables) to an outside client, the fundamental planning process is unchanged, except that specifications cannot be altered without the client's permission. A common planning problem is that marketing has promised deliverables that engineering may not know how to produce on a schedule that manufacturing may be unable to meet. This results when functional areas are not involved in the planning process when the original proposal is made.

Two objections to early participation by engineering and manufacturing are raised by marketing. First, salespeople are expected to be knowledgeable about all technical aspects. Second, it is expensive to involve technical talent so early in the sales process. However, the rejoinder is that when a product/service is complex, it is appropriate to treat the sale like a project. It is usually cheaper, faster, and easier to do things right the first time.

🔑 Definition — Deliverables: The product(s) or service(s) that a project is intended to deliver to a client.

📌 Example: A firm might sell a complex system that must be installed in a larger, more complex system. In this case, the sale itself should be treated as a project, requiring careful planning from all functional areas from the start.

16.3 Project Planning Checklist:

These are described below for different areas of operations:

Construction Planning: Includes facility turnover sequence, temporary facilities, tool and equipment requirements, labor availability and productivity, work week and productivity impact, climatic effects on field work, field engineering assistance required, extent of subcontracting, and field organization and staffing.

Procurement Planning: Includes procurement sources (equipment, materials), home office versus field procurement, long lead time items, and logistical planning.

Engineering Planning: Includes source(s) of technology, codes, specifications and standards, utilization of consultants, early work, requisitioning priorities, drawing priorities, vendor data requirements, utilization of scale models, manpower requirements, approval requirements, organization and staffing, and utilization of prefabricated modules.

Quality Control Planning: Includes audit of design and equipment for conformance to specifications, checking of calculations and drawings, shop inspection of equipment, certification of materials and welding procedures, receiving and inspection of equipment and materials, jobsite storage and environmental protection, and construction inspection.

Financial Planning: Includes cash flow requirements, progress payments and billing frequency, and impact of financial sources.

📌 Example: In construction planning, a project manager must consider the sequence in which different parts of a facility will be turned over to the client (facility turnover sequence) and whether temporary offices are needed on site.

⭐ Key Takeaways

The most critical points from this lecture are: planning is a multi-component process encompassing objectives, programs, schedules, budgets, forecasts, organization, policies, procedures, and standards. Effective initial coordination, symbolized by a kick-off meeting with senior management, is essential to align the project with the firm's mission and secure top-management commitment. Any changes to an approved plan must be formally processed and communicated to all affected parties to maintain trust. When dealing with outside clients, it is crucial to involve all relevant functional areas (engineering, manufacturing) in the planning process from the start to prevent unrealistic promises. Finally, a comprehensive project planning checklist tailored to specific areas like construction, procurement, and engineering helps ensure no critical detail is overlooked.

🧠 Quick Revision Questions

1. List the nine major components of the general planning phase.
2. What are the three typical time horizons for planning (strategic, tactical, operational)?
3. What is the key output of the initial project coordination meeting, and what must it include?
4. Why is it considered a "betrayal of trust" to change an approved project plan without informing the contributing units?
5. Name three specific items that a project manager should consider when creating a "Procurement Planning" checklist.

📘 Lecture 17 — Project Planning (Contd.)

📖 Overview: This lecture continues the discussion of project planning by examining the essential elements that constitute a comprehensive project plan. It details each component from overview to potential problems, and then explores the critical role of systems integration in ensuring project success. Understanding these elements is vital for creating a robust, actionable plan that guides the project from initiation to completion.

🗂️ Topics Covered

The lecture covers the nine core elements of a project plan: Overview, Introduction, General Approach, Contractual Aspects, Schedules, Resources, Personnel, Evaluation Methods, and Potential Problems. It then provides a detailed discussion on key parts of a plan including Introduction/Overview, Mission and Objectives, Work Scope, and Planning Basis. Finally, it addresses Systems Integration, its three major objectives (Performance, Effectiveness, and Cost), and its impact on project success.

📝 Lecture Summary

Elements of a Project Plan

The process of developing a project plan varies from organization to organization. However, any project plan must contain the following elements:

Overview: This is a short summary of objectives and scope of the project. It is directed to top management and contains a statement of goals of the project; a brief explanation of their relationship to the firm’s objectives, a description of the managerial structure that will be used for the project, and a list of major milestones in the project schedule.

Introduction: This contains a more detailed statement of general goals noted in the overview section. The statement should include profit and competitive aims as well as technical goals.

General Approach: This section describes both managerial and technical approaches to the work. The technical discussion describes the relationship of the project to available technologies. For example, it might note that this project is an extension of work done by the company for an earlier project. The subsection on managerial approach takes note of any deviation from routine procedure – for instance, the use of subcontractors for some parts of the work.

Contractual Aspects: This critical section of the plan includes a complete list and description of all reporting requirements, customer-supplied resources, liaison arrangements, advisory committees, project review and cancellation procedures, proprietary requirements, any specific management agreements (for example, use of subcontractors) as well as technical deliverables and their specifications, delivery schedules, and specific procedures for changing any of the above. Completeness is a necessity in this section. If in doubt about whether an item should be included or not, the wise planner will include it.

Schedules: This section outlines various schedules and lists all milestone events. Estimated time for each task should be obtained from those who will do the work. The project master schedule is constructed from those inputs. The responsible person or department head should sign off on the final, agreed-on schedule.

Resources: There are two primary aspects to this section. First is the budget. Both capital and expense requirements are detailed by task, which makes this the project budget. One-time costs are separated from recurring project costs. Second, cost monitoring and control procedures should be described. In addition to usual routine elements, monitoring and control procedures must be designed to cover special resource requirements for the project, such as special machines, test equipment, laboratory usage or construction, logistics, field facilities, and special materials.

Personnel: This section lists expected personnel requirements of the project. Special skills, types of training needed, possible recruiting problems, legal or policy restrictions on work force composition, and any other special requirement, such as security clearances, should be noted here. (This reference to “security” includes the need to protect trade secrets and research targets from competitors as well as the need to protect national security). It is helpful to time-phase personnel needs to project who is needed and in what numbers. These projections are an important element of the budget, so personnel, schedule, and resources sections can be crosschecked with one another to ensure consistency.

Evaluation Methods: Every project should be evaluated against standards and by methods established at the project's inception. This section contains a brief description of the procedure to follow in monitoring, collecting, storing, and evaluating the history of the project.

Potential Problems: Sometimes it is difficult to convince planners to make a serious attempt to anticipate potential difficulties. One or more such possible disasters—such as subcontractor default, technical failure, strikes, bad weather, sudden required breakthroughs, critical sequences of tasks, tight deadlines, resource limitations, complex coordination requirements, insufficient authority in some areas, and new, complex, or unfamiliar tasks—are certain to occur. The only uncertainties are which ones will occur and when. The timing of these disasters is not random. There are times, conditions, and events in the life of every project when progress depends on subcontractors, or weather, or coordination or resource availability, and plans to deal with unfavorable contingencies should be developed early in the project's life cycle. Some project managers disdain this section of the plan on the grounds that crises cannot be predicted. Further, they claim to be very effective firefighters. It is quite possible that when one finds such a project manager, one has discovered an arsonist. No amount of current planning can solve current crises, but preplanning may avert some.

These are the elements that constitute a project plan and are the basis for more detailed planning of budgets, schedules, work plans, and general management of the project. Once this basic plan is fully developed and approved, it is disseminated to all interested parties.

Introduction/Overview

The project management plan introduction/overview includes an introduction both to the specific project and to the project management plan document itself. Some background information may be included to set the stage or provide perspective on the information that follows, such as how the project was initiated, who the customer or sponsor is, how the project is funded, or other factors that are important to those who read the plan. Introductions are always short, allowing the reader to move into the plan quickly. Additional external or historical information can be referenced or included in the Appendix. External factors, such as general or specific economic trends, constraints, or opportunities; political or governmental conditions; population demographics; or internal organizational factors, should be discussed.

Mission and Objectives

The purpose or mission of the project is stated in one or two paragraphs, followed by a set of concrete objectives. The mission statement is all-encompassing, establishing why the project exists. Mission statements can be general or specific. They also reference the customer if the project is being performed under contract or for a third party. Project objectives are outlined as specific goals to be accomplished and to which status they can be applied. For instance, objectives for a small construction project might include a good location; a modern energy-efficient economic design; a fully furnished facility; a complete set of project documents; compliance with all laws, codes, and requirements; a standard profit margin; and a completion date.

Planning becomes straightforward when objectives are defined for key areas. Objectives can be established for every aspect of the project, including scope of work, organization, management, systems, environment, safety, and overall completion of the project (i.e., final cost and schedule dates). Established objectives in the following areas facilitate detailed planning, systems development, and work performance:

• Technical objectives
• Schedule objectives
• Cost objectives
• Organizational/personnel-related objectives
• Quality objectives
• Environmental safety and health objectives
• Contracting/procurement objectives
• Management system objectives

Well-defined objectives enhance the reliability of subsequent planning. Once objectives are stated in concise terms, they allow for the development of the project scope of work and the work breakdown structure (WBS).

💡 Why this matters: Clear mission and objectives provide the foundation for all subsequent planning activities. They ensure everyone understands the project's purpose and the specific, measurable targets that will define its success.

Work Scope

The work scope section of the project management plan demonstrates how well the project is understood. It includes narrative descriptions of all elements of the project's scope of work. It clearly identifies the products or services to be provided to the customer. The statement of work (SOW) contains enough information to allow development of the Work Breakdown Structures (WBS), schedules, and cost estimates, as well as assignment of responsibilities.

This section can address the project phases and include special plans associated with those phases, such as the Research and Development plan, engineering/design plans, construction plan, manufacturing plan, facility start-up plan, or transition plan. It may also describe the systems management activities, including systems engineering and integration, to ensure a project life cycle perspective. In other words, it shows that the activities necessary to ensure that the design and final products meet customer requirements are all planned and managed properly and can be integrated and operated as intended, and that start up, transition, operation, and completion activities are also planned and managed properly. To simplify preparation, the work scope can be prepared in outline form, which can then be used to develop the Work Breakdown Structure (WBS). Often the Work Breakdown Structure (WBS) and work scope are prepared in parallel, with the resultant narrative description of the work called a Work Breakdown Structure (WBS) dictionary.

Planning Basis

The planning basis section provides for the documentation of key approaches, assumptions, requirements, and other factors considered during preparation of the project management plan. The following topics are addressed in this section:

1. Project Deliverables/End Products: A list of all products, documents, and services to be delivered to the customer over the life of the project is required.

2. Requirements: Requirements are specifications or instructions that must be followed during project performance. They may include technical requirements, facilities requirements, data requirements, management requirements, or special instructions. Technical requirements may include codes, standards, laws, engineering or design specifications, models, or examples for mandatory or recommended compliance on the project. When there are mandatory requirements, such as laws, these must be identified and listed, or project performers run the risk of noncompliance and legal prosecution. Facilities requirements include an initial assessment of types, amount, and quality of facilities needed for the project, along with related utilities, furniture, and equipment. This provides initial bases for estimating quantities and costs associated with those resources. Overlooking facilities issues during project planning leads to schedule slippages, cost overruns, unhappy project participants, and untold headaches for the project managers. For small projects, facility requirements may not be a big issue; for larger projects, they can be critical. Functional and operational requirements spell out what the system, facility, or product being produced is intended to do. They provide the basis for the engineering, design, and planning of the system, facility, or product. Where functional and operational requirements exist, listing or identifying them greatly simplifies and facilitates the design process. Mandatory data requirements, management directives, or special instructions are also identified and documented during the planning process.

3. Constraints: Constraints may include known technical limitations, financial ceilings, or schedule "drop dead" dates. Technical constraints may be related to state-of-the-art capabilities, interface requirements with other systems, or user-related issues (e.g., software that must run on certain types of personal computers). Financial and schedule constraints can be introduced by the customer and lead-time associated with procured hardware or funding/budgetary limits.

4. Approaches/Strategies: The approach or strategies to be utilized can have a major impact on subsequent planning. For instance, if all project work is to be performed within the parent (host) organization with minimum subcontract support, that approach impacts planning of resources and organizational issues. If work is to be "fast-tracked" by overlapping design and construction activities, or by performing more work in parallel, then that approach can be described. Communication of strategies to project participants can be done effectively by devoting several paragraphs to that topic in this section of the project management plan.

5. Key Assumptions: Every project is planned under some degree of uncertainty. Therefore, assumptions are required to estimate work scope, schedule durations, resource requirements, and cost estimates. Assumptions are also required when defining the management strategies, systems, and procedures to be utilized. Major assumptions are to be documented because they can have a significant impact on planning and estimating. This is true on all projects, regardless of size. Large projects, which involve numerous participants and major complexities, generally depend on more key assumptions during project planning than smaller projects. The major reason for documenting key assumptions is to provide the project manager with a basis for revising plans when the assumptions are changed (that is, when a customer changes his or her mind).

6. Specifically Excluded Scope: This subject may be needed to limit the scope of work. It highlights specific and relatively obvious issues, such as documentation, training, or follow-on support, which customers often assume but which cost money and have not been included in the project plan. Clarification of these scoping questions saves headaches later, in some cases even avoiding litigation.

💡 Why this matters: The planning basis section captures all the foundational information and decisions that underpin the project plan. Documenting assumptions, constraints, and exclusions is critical for managing expectations and providing a baseline for future changes.

Systems Integration

Systems integration (sometimes called systems engineering) plays a crucial role in the performance aspect of a project. This phrase is used here to include any technical specialist in the science or art of the project who is capable of performing the role of integrating the technical discipline to achieve the customer's objectives, and/or integrating the project into the customer's system. As such, system integration is concerned with three major objectives:

1. Performance: This is what the system does. It includes system design, reliability, quality, maintainability, and reparability. Obviously, these are not separate, independent elements of the system, but are highly interrelated qualities. Any of these system performance characteristics is subject to over-design as well as under-design but must fall within design parameters established by the client. If the client approves, we may give the client more than specifications require simply because we have already designed to some capability and giving the client an over-designed system is faster and less expensive than delivering precisely to specification. At times, esthetic qualities of the system may be specified, typically through the requirement that the appearance of the system must be acceptable to the client.

2. Effectiveness: The objective is to design individual components of the system to achieve desired performance in an optimal manner. This is accomplished through the following guidelines:

   • Require no component performance specifications unless necessary to meet one or more system requirements.
   • Every component requirement should be traceable to one or more system requirements.
   • Design components to optimize system performance, not the performance of the subsystem. It is not unusual for clients to violate any or all of these seemingly logical dicta. Tolerances specified to far closer limits than any possible system requirement, superfluous "bells and whistles," and "off the shelf" components that do not work well with the rest of the system are so common they seem to be taken for granted by both client and vendor. The causes of these strange occurrences are probably associated with some combination of inherent distrust between buyer and seller, desire to over-specify in order "to be sure," and the feeling that "this part will do just as well." These attitudes can be softened and replaced with others that are more helpful to the process of systems integration.

3. Cost: Systems integration considers cost to be a design parameter, and costs can be accumulated in several areas. Added design cost may lead to decreased component costs, leaving performance and effectiveness otherwise unchanged. Added design cost may yield decreased production costs and production cost may be traded off against unit cost for materials. Value engineering (or value analysis) examines all these cost tradeoffs and is an important aspect of systems integration. It can be used in any project where relevant cost tradeoffs can be estimated. It is simply the consistent and thorough use of cost/effectiveness analysis.

Systems integration plays a major role in the success or failure of any project. If a risky approach is taken by systems integration, it may delay the project. If the approach is too conservative, we forego opportunities for enhanced project capabilities or advantageous project economies. Good design will take all these tradeoffs and avoid locking the project into a rigid solution with little flexibility or adaptability in case problems occur later on or changes in the environmental demand changes in project performance or effectiveness.

🔑 Definition — Systems Integration (Systems Engineering): The role of integrating technical disciplines to achieve the customer's objectives and/or integrating the project into the customer's system. 📐 Formula (Guidelines for Effectiveness): Design components to optimize system performance, not subsystem performance. 📌 Example: A client might specify a component with tolerances far tighter than any possible system requirement. A systems integrator must identify this as unnecessary "over-specification" and work with the client to relax the tolerance, reduce costs, and improve component availability, all while maintaining overall system performance.

⭐ Key Takeaways

The nine core elements of a project plan (Overview, Introduction, General Approach, Contractual Aspects, Schedules, Resources, Personnel, Evaluation Methods, and Potential Problems) provide a comprehensive and mandatory framework for any project. A well-defined mission statement and a set of concrete, measurable objectives covering technical, schedule, cost, quality, and other areas are foundational for reliable subsequent planning and the development of the WBS. The planning basis section is critical for documenting key assumptions, constraints, and specifically excluded scope to manage expectations and provide a baseline for future revisions. Systems integration is a crucial technical and managerial function with three key objectives: performance, effectiveness, and cost, and its approach can determine the project's success or failure by balancing risk and conservatism.

🧠 Quick Revision Questions

1. What are the nine essential elements of a project plan as described in this lecture?
2. Why is it critical to include a section on "Potential Problems" in a project plan, and what is the risk of not planning for contingencies?
3. List at least five of the eight types of project objectives that should be established to facilitate detailed planning.
4. What is the primary purpose of documenting "Key Assumptions" in the Planning Basis section of the project plan?
5. What are the three major objectives of systems integration, and explain how value engineering relates to one of them?

📘 Lecture 18 — Project Planning (Contd.)

📖 Overview: This lecture continues the discussion on project planning, focusing on the systematic process of sorting out project activities and outcomes. It explains the objectives and reasons for planning, and details the role of policies, procedures, and standards in projects. This is crucial for establishing a structured foundation for project execution, monitoring, and control.

🗂️ Topics Covered

This lecture covers the method for sorting out project activities using hierarchical action plans, including the Gozinto chart. It then details the objectives and reasons for project planning, such as reducing uncertainty and improving efficiency. Finally, it defines policies, procedures, and standards, and categorizes planning into strategic, tactical, and operational levels.

📝 Lecture Summary

18.1 Sorting Out Project

To manage project details, we must know exactly what is to be done, by whom, and when. All activities must be precisely delineated and coordinated. The process begins by listing major activities in general order (between 2 and 20), and then breaking each into subtasks (also 2 to 20). It is vital that all items in a list are at the same level of task generality. A common problem is mixing outcomes (events) and tasks (activities) in planning.

The proposed method is a hierarchical planning system. First, goals are specified, which helps identify required activities and outcomes. Each activity has an outcome (event), and these can be decomposed into sub-activities. The project action plan contains all planning information in one document.

The actual form of an action plan is not fixed; it can vary by organization. A tree diagram, called a Gozinto Chart (after the invented mathematician Professor Zepartzat Gozinto), can represent the hierarchical plan and is similar to a Bill of Materials in MRP.

🔑 Definition — Action Plan: A document that contains all planning information, including activity details, responsibilities, timeframes, and resources. 📐 Formula: [Hierarchical breakdown] → [Major Activities] → [Subtasks] → [Elemental Work Packages] 📌 Example (College Career Day - Partial Action Plan): Objective 1 (Contact Organizations) includes steps like 'Print forms' (Secretary, 6 weeks), 'Contact organizations' (Program Manager, 15 weeks, precedes 1.A), and 'Collect display information' (Office Manager, 4 weeks, precedes 1.B). Objective 2 (Banquet) includes 'Select guest speaker' (Program Manager, 14 weeks) and 'Organize food' (Program Manager, 3 weeks, precedes 1.b, resource: Caterer).

The importance of planning is highlighted by Slevin's strategic factors for project success: a clearly defined Project Mission, Top Management Support, and a detailed Project Schedule or Plan.

📌 Example (Tabular Action Plan for Ajax-Instat Merger): Step 1: 'Ajax management advised of changes,' Due Date: 24/7, Responsible: Bob, Precedent: -. Step 6: 'Visit Ajax management and plan to discuss merger of operations,' Due Date: 1/8, Responsible: Smith, Precedent: 4,5.

The planning process involves developing a project mission statement and detailed specifications from technical requirements. Responsibility for first-level tasks is delegated, and team members develop second-level action plans. This continues until tasks are perceived as "units" or "packages" of work.

18.2 Objectives and Reasons of Project Planning

One main objective is to completely define all work required so it is identifiable to each participant. This is a necessity because: if the task is well understood, work can be preplanned; if not, more knowledge is gained during execution, leading to changes; and the more uncertain the task, the more information must be processed. Without proper planning, projects can start off "behind the eight ball."

There are four basic reasons for project planning:

• To eliminate or reduce uncertainty
• To improve efficiency of the operation
• To obtain a better understanding of the objectives
• To provide a basis for monitoring and controlling work

Planning reasons can be involuntary (e.g., organizational complexity, environmental fluctuations) or voluntary (e.g., securing efficient operations). Planning is decision-making based on futurity, which allows an organization to set goals. The alternative, decision-making based on history, leads to reactive, crisis-driven management.

18.3 Policies, Procedures and Standards

🔑 Definition — Policy: A deliberate plan of action to guide decisions and achieve rational outcomes. 🔑 Definition — Procedure: A specification of a series of actions that have to be executed in the same manner to always obtain the same result in the same circumstances. 🔑 Definition — Standard: The process of establishing a technical specification among competing entities to bring benefits without hurting competition, or a mechanism for optimizing the use of scarce resources.

18.3.1 Categories of Planning

Strategic Planning produces fundamental decisions that shape and guide what an organization is, does, and why. It requires broad information gathering and an emphasis on future implications. Top-level managers engage in this, clarifying the mission and setting long-term goals (more than one year).

Tactical Plans are developed by middle managers to interpret the general, long-term goals set by top management. These plans can be accomplished within one year or less and provide specific ideas for implementing the strategic plan. 💡 Why this matters: Tactical plans translate the broad vision of strategic planning into concrete departmental actions.

Operational Plans are implemented by supervisors and are short-term, dealing with day-to-day work. They set standards, form schedules, secure resources, and support tactical plans. Examples include budgets, schedules, and identifying resource needs. These plans include policies, procedures, methods, and rules.

Policies, procedures, and standards vary from project to project due to uniqueness. Every project manager can establish project policies within broad limits set by top management, including guidelines for planning, scheduling, controlling, and communications.

⭐ Key Takeaways

The lecture provides a structured, hierarchical method for sorting out a project into manageable activities and work packages, which is essential for clear assignment and coordination. The four primary reasons for project planning—reducing uncertainty, improving efficiency, clarifying objectives, and providing a basis for control—are the theoretical core for why planning is a non-negotiable function. You must distinguish between the three categories of planning: strategic (long-term, mission-focused), tactical (mid-term, departmental), and operational (short-term, daily execution). Finally, understand that policies, procedures, and standards are formal guidelines that must be established for a project, but they must align with top management's overall directives.

🧠 Quick Revision Questions

1. What is the recommended range for the number of major activities in a project plan, and why is this range considered practical?
2. Explain the difference between an "outcome" (or event) and a "task" (or activity) in the context of project planning.
3. List the four basic reasons for project planning as described in the lecture.
4. Define a "Gozinto Chart" and explain how it relates to the concept of a hierarchical planning system.
5. What are the three categories of planning, and which level of management is primarily responsible for each?

📘 Lecture 19 — Project Planning (Contd.)

📖 Overview: This lecture focuses on identifying and analyzing strategic project variables that influence the success or failure of a project plan. It explains the importance of monitoring the internal, external, and competitive environments, and how upper-level management must remain involved in strategic planning to ensure effective decision-making and resource allocation.

🗂️ Topics Covered

This lecture covers the identification of strategic project variables, the three environments (internal, external, competitive), the guidelines for strategic project planning, the process of defining environmental variables, and the necessity of communication between top management and the project office. It also discusses the challenges of implementing top-management participation and the need for variable classification to establish priorities and anticipate the unexpected.

📝 Lecture Summary

19.1 Identifying Strategic Project Variables:

The project manager must continually monitor the external environment to develop a well-structured program that can withstand pressure, especially for long-range or strategic projects. Environmental factors are integral to planning. The project manager must identify and evaluate these strategic variables regarding the future posture of the organization and constraints on existing resources.

Strategic project planning is performed at the horizontal hierarchy level, with final approval by upper-level management. There are three basic guidelines:

• Upper-level management must maintain close involvement with project teams, especially during the planning phase.
• Successful strategic planning must define the authority, responsibility, and roles of the strategic planning personnel.
• Strategic project planning is a job for managers, not for them.

To ensure success, all members of the horizontal team must be aware of strategic variables that can influence the plan's success or failure. Analysis begins with the environment, subdivided into three areas:

• Internal Environment: Includes management skills, resources, wage and salary levels, government freeze on jobs, minority groups, layoffs, and sales forecasts.
• External Environment: Includes legal, political, social, economic, and technological factors.
• Competitive Environment: Includes industry characteristics, company requirements and goals, competitive history, present competitive activity, competitive planning (e.g., return on investment, market share, size and variety of product lines), and competitive resources.

Once environmental variables are defined, the planning process continues with: identification of company strengths and weaknesses, understanding personal values of top management, identification of opportunities, definition of product market, identification of competitive edge, establishment of goals/objectives/standards, and identification of resource deployment.

At the program level, complete identification of all strategic variables is not easily obtainable. Internal (operating) variables are readily available to program personnel due to the organizational structure. However, external variables are normally tracked under the perceptive eyes of top management. This presents a challenge: those in the horizontal hierarchy often focus more on the current operational plan than external factors, becoming isolated from the environment and losing insight into rapidly changing external variables. Proper identification requires communication channels between top management and the project office.

🔑 Definition — Strategic Variables: Factors in the internal, external, and competitive environments that can influence the success or failure of a project plan.

🔑 Definition — Horizontal Hierarchy: The level within an organization where strategic project planning is performed, involving cross-functional team members.

💡 Why this matters: A project manager must balance operational focus with awareness of external trends. Without communication channels to top management, the project team can become insulated and miss critical shifts in the external environment.

It is essential that top-management support is available for identifying strategic planning variables so effective decision-making can occur at the program level. However, participation from top management has been difficult to implement. Many top-level officers view this as a relinquishment of power and choose to retain strategic variable identification for themselves.

Importantly, the systems approach to management does not attempt to decrease top management's role in strategic decision-making. The maturity, intellect, and wisdom of top management cannot be replaced. Ultimately, decision-making will always rest at upper levels, regardless of the organizational structure.

Therefore, identification and classification of strategic variables are necessary to establish relative emphasis, priorities, and selectivity among alternatives, to anticipate the unexpected, and to determine program restraints and limitations. Universal classification systems do not exist because of the varied nature of organizations and projects. However, variables can be roughly categorized as internal and external, as shown in Table 19.1 (Strategic Planning Variables in the Tire Industry).

🔑 Definition — Systems Approach to Management: A management philosophy that does not reduce top management's role in strategic decisions but emphasizes integrated thinking across the organization.

💡 Why this matters: Even with distributed planning teams, final strategic decisions remain with top management. The goal is to improve communication, not to transfer power.

⭐ Key Takeaways

A project manager must continually monitor the internal, external, and competitive environments to identify strategic variables that can affect project success. Strategic planning is done at the horizontal hierarchy level, but requires close involvement and final approval from upper-level management. Communication channels between top management and the project office are critical for identifying external variables, as project teams often become isolated after the program begins. The systems approach does not replace top management's decision-making role, but emphasizes their continued participation. Finally, variable classification helps establish priorities, anticipate unexpected events, and define program limitations, though no universal classification system exists.

🧠 Quick Revision Questions

1. What are the three subcategories of the environment analyzed when identifying strategic project variables?
2. What is the primary challenge associated with tracking external variables at the program level?
3. Why might top-level officers resist participating in the identification of strategic planning variables?
4. According to the lecture, what is the purpose of identifying and classifying strategic variables?
5. What is the role of the horizontal hierarchy in strategic project planning?

📘 Lecture 20 — Project Planning (Contd.)

📖 Overview: This lecture continues the discussion on project planning, focusing on how planning occurs at two levels: corporate cultural approaches using life-cycle phases and individual approaches. It explains the responsibilities of key players in the planning process and identifies common problems encountered when setting project objectives, providing practical insights for effective project management.

🗂️ Topics Covered

This lecture covers life-cycle phases and their benefits for project control and uniformity, detailing specific phases like conceptualization and feasibility with their key activities and purposes. It also examines the distinct responsibilities of project managers, line managers, and senior management in the planning process, concluding with an analysis of typical problems in objective setting and the need for prioritization.

📝 Lecture Summary

Life-Cycle Phases:

Project planning takes place at two levels: the corporate cultural approach and the individual's approach. The corporate cultural approach breaks the project down into life-cycle phases, which is not an attempt to restrict the project manager but to provide a methodology for uniformity in project planning. Many companies and government agencies prepare checklists of activities for each phase to ensure consistency, while the project manager can still exercise his own planning initiatives within each phase.

The second benefit of life-cycle phases is control. At the end of each phase, there is a meeting between the project manager, sponsor, senior management, and even the customer to assess accomplishments and get approval for the next phase. These meetings, called "critical design reviews," "on-off ramps," or "gates," are used to firm up budgets and schedules for follow-on phases. Life-cycle phase decision points eliminate the problem where project managers ask for funds for the whole project before the true scope is known.

Types of decisions made at end-of-phase review meetings include:

• Proceed with the next phase based on an approved funding level
• Proceed to the next phase but with a new or modified set of objectives
• Postpone approval based on a need for additional information
• Terminate project

The lecturer provides an example of a company utilizing the following life-cycle phases:

• Conceptualization: This phase includes brainstorming and common sense, involving two critical factors: (1) Identify and define the problem, and (2) Identify and define potential solutions. All ideas are recorded and none are discarded. The brainstorming session works best with no formal authority present and for no more than thirty to sixty minutes; sessions over sixty minutes may produce ideas resembling science fiction.
• Feasibility: This phase considers the technical aspects of conceptual alternatives and provides a firmer basis for deciding whether to undertake the project. Its purpose is to plan project development and implementation activities, estimate probable elapsed time, staffing, and equipment requirements, and identify probable costs and consequences. The objective is to provide management with predictable results and generalized project requirements in a feasibility study report.
• Preliminary planning (or "defining the requirements"): This is the phase where the effort is officially defined as a project. Considerations include general scope of work, objectives and related background, contractor's tasks, end-item performance requirements, references, data items, support equipment, customer-furnished property, documentation, schedule of performance, and exhibits.

Responsibilities of Key Players:

Planning does not simply happen by itself; successful companies have employees who fully understand their roles in the planning process. Good up-front planning may not eliminate changes, but can reduce the number of changes required. Successful planning requires that project, line, and senior management are in agreement with the plan.

The responsibilities of the major players are:

1. Project manager will define: goals and objectives, major milestones, requirements, ground rules and assumptions, time, cost, and performance constraints, operating procedures, administrative policy, and reporting requirements.
2. Line manager will define: detailed task descriptions to implement objectives, requirements, and milestones, detailed schedules and manpower allocations to support budget and schedule, and identification of areas of risk, uncertainty, and conflict.
3. Senior management (project sponsor) will: act as the negotiator for disagreements between project and line management, provide clarification of critical issues, and provide a communication link with the customer's senior management.

Problems in Objective Setting:

It is not possible to satisfy all objectives every time. At this point, management must prioritize the objectives as to which are strategic and which are not. Typical problems with developing objectives include:

• Project objectives/goals are not agreeable to all parties.
• Project objectives are too rigid to accommodate changing conditions.
• Insufficient time exists to define objectives well.
• Objectives are not adequately quantified.
• Objectives are not documented well enough.
• Efforts of client and project personnel are not coordinated.
• Personnel turnover is high.

⭐ Key Takeaways

The most critical point for an exam is understanding that life-cycle phases provide methodology for uniformity and control in project planning, with end-of-phase review meetings serving as decision points for proceeding, modifying, postponing, or terminating projects. Students must remember the specific phases described (conceptualization, feasibility, and preliminary planning) along with their distinct purposes, especially that brainstorming should last no more than thirty to sixty minutes and that feasibility studies provide a firmer basis for decisions. The responsibilities of key players are essential knowledge: project managers define goals and constraints, line managers define detailed tasks and schedules, and senior management acts as negotiator and communication link. Finally, students should be able to list and explain the common problems in objective setting, particularly the need to prioritize strategic objectives when it is impossible to satisfy all objectives every time.

🧠 Quick Revision Questions

1. What are the two levels at which project planning takes place according to the corporate cultural approach?
2. List the three types of decisions that can be made at an end-of-phase review meeting.
3. What are the two critical factors involved in the conceptualization phase, and what is the recommended time duration for a brainstorming session?
4. What are the three primary responsibilities of a line manager in the planning process?
5. Name at least four of the seven typical problems in objective setting discussed in this lecture.

📘 Lecture 21 — Project Planning (Contd.)

📖 Overview: This lecture continues the discussion on project planning by focusing on the Statement of Work (SOW) — a critical document that narratively describes the work required for a project. It explains the importance of clear SOW preparation, common causes of misinterpretation that lead to costly scope creep, and provides detailed guidelines and checklists for creating effective SOWs.

🗂️ Topics Covered

The lecture covers two main topics: first, The Statement of Work (SOW), including its definition, who prepares it for internal versus external projects, the distinction between proposal SOW and Contract Statement of Work (CSOW), and common misinterpretation causes; second, Guidelines for Preparing SOW, which provides 12 specific preparation guidelines followed by a comprehensive 16-point checklist for SOW writers.

📝 Lecture Summary

21.1 The Statement of Work (Sow):

The Statement of Work (SOW) is a narrative description of the work required for the project. Its complexity is determined by the desires of top management, the customer, and/or user groups. For internal projects, the SOW is prepared by the project office with input from user groups because user groups tend to write in overly scientific terms. The project office, having skilled writers, prepares the SOW and submits it to user groups for verification and approval.

For external projects (competitive bidding), the contractor may prepare the SOW for the customer who lacks trained preparers. The contractor submits the SOW to the customer for approval. It is also common for the project manager to rewrite a customer's SOW so line managers can price out the effort.

🔑 Definition — Statement of Work (SOW): a narrative description of the work required for the project

In a competitive bidding environment, there are two SOWs — the SOW used in the proposal and a "Contract Statement of Work" (CSOW) . Similarly, there may be a proposal "Work Breakdown Structure" (WBS) and a "Contract Work Breakdown Structure" (CWBS) . Special care is needed to discover all discrepancies between SOW/WBS and CSOW/CWBS, or additional costs may be incurred. A good proposal does not guarantee mutual understanding. For large projects, fact-finding is usually required before final negotiations to ensure agreement on the SOW, required work, proposed work, cost basis, and related elements.

💡 Why this matters: Misunderstandings between the proposal SOW and the signed Contract SOW can lead to unbudgeted work and financial losses.

SOW preparation is not easy. Three examples illustrate costly misinterpretations:

• A SOW requiring "a minimum of fifteen tests" — contractor priced 20 tests "to play it safe," but customer demanded another 15 tests after inconclusive results, causing a $40,000 cost overrun.
• The Navy's SOW stating prototype must be tested in "water" — contractor used a swimming pool, but the Navy meant the Atlantic Ocean, costing $1 million to transport equipment.
• A SOW requiring transport using "aerated" boxcars — contractor used open-top boxcars (air from above), but customer wanted aeration from below; goods were ruined by rain, leading to a court case.

Common causes of SOW misinterpretation include:

• Mixing tasks, specifications, approvals, and special instructions
• Using imprecise language ("nearly," "optimum," "approximately")
• No pattern, structure, or chronological order
• Wide variation in size of tasks
• Wide variation in how to describe details of the work
• Failing to get third-party review

Misinterpretations lead to creeping scope (also called "creeping elegance"). The best control is a good upfront requirements definition, though not always possible. In aerospace, defense, and MIS industries, creeping scope had become a way of life. An example showed a project manager refusing scope changes once requirements were defined, instead putting all change requests into a follow-on enhancement project that was later neither funded nor approved.

21.2 Statement of Work (Sow) Preparation Guidelines:

Guideline 1: Every SOW exceeding two pages should have a table of contents conforming to the Contract Work Breakdown Structure (CWBS) coding structure. Items in the SOW should rarely be absent from the CWBS, though it is not absolutely necessary to restrict items to those cited.

Guideline 2: Clear and precise task descriptions are essential. The writer must consider varied readers (lawyers, buyers, engineers, cost estimators, accountants, specialists). A good SOW states precisely the product or service desired. Clarity affects contract administration since it defines scope — work outside that scope means new procurement with increased costs.

Guideline 3: Avoid ambiguity by considering how writing affects readers. Spell out all government obligations. For government approval actions, set a time limit. For Government-Furnished Equipment (GFE) or services, state the nature, condition, and delivery time if feasible.

🔑 Definition — Government-Furnished Equipment (GFE): equipment and/or services provided by the government to the contractor for use in performing the contract

Guideline 4: Any provision taking control of work from the contractor, even temporarily, may relieve the contractor of responsibility.

Guideline 5: Use active terminology rather than passive. Say "the contractor shall conduct a test" rather than "a test should be conducted." Use the mandatory term "shall" for firm requirements, not the permissive "should."

Guideline 6: Limit abbreviations to common usage. Provide a list of all pertinent abbreviations and acronyms at the beginning of the SOW. When first using a term, spell it out and show the abbreviation or acronym in parentheses.

Guideline 7: When defining a division of responsibilities between contractor and other agencies, include a separate SOW section to delineate such responsibilities.

Guideline 8: Include procedures for when immediate decisions cannot be made (e.g., "as approved by the contracting officer" or "the contractor shall submit a report each time a failure occurs").

Guideline 9: Do not over-specify. Depending on work nature and contract type, specify required results or end-items and let the contractor propose the best method.

Guideline 10: Describe requirements in sufficient detail for clarity and practical application. For every deliverable hardware, report, or immediate action, do not say "as necessary" — specify who makes the judgment (contractor or government). For expensive services like technical liaison, provide a ceiling (e.g., a level of effort or man-hour pool).

Guideline 11: Avoid extraneous material and requirements that add unnecessary cost. Screen out unnecessary data requirements; specify only what is essential and when. Recommend specifying data requirements separately in a data requirements appendix.

Guideline 12: Do not repeat detailed requirements already in applicable documents — incorporate them by reference. If amplification, modification, or exceptions are needed, make specific reference to applicable portions and describe the change.

A checklist is provided for SOW writers:

1. Is the SOW (with preliminary CWBS) specific enough for a contractor to tabulate manpower and resources needed for each SOW task element?
2. Are specific duties stated so the contractor knows what is required and the contracting officer's representative can verify compliance?
3. Are all parts written so there is no question about what the contractor is obligated to do and when?
4. When referencing other documents, is the proper document described, properly cited, and cross-referenced to applicable SOW task elements?
5. Are any specifications or exhibits applicable? If so, are they properly cited and referenced?
6. Are directions clearly distinguishable from general information?
7. Is there a time-phased data requirement for each deliverable item? Does elapsed time specify calendar or work days?
8. Are proper quantities shown?
9. Have headings been checked for format and grammar? Is the numbering system cross-referenced with CWBS?
10. Have appropriate procurement regulations been followed?
11. Has extraneous material been eliminated?
12. Can SOW task/contract line items be summarized to discrete third-level CWBS elements?
13. Have all data requirements been specified separately in an appendix or equivalent?
14. Have all extraneous data requirements been eliminated?
15. Are security requirements adequately covered if required?
16. Has its availability to contractors been specified?

Finally, there should be a management review of the SOW preparation interpretation. During development, the project manager should hold frequent reviews with project and functional specialists to ensure technical and data requirements conform to guidelines. The CWBS/SOW matrix should analyze completeness. After incorporating comments, a final team review produces a draft SOW for functional and project managers. A final draft is prepared and reviewed with the program manager, contracting officer, or higher management. The final review includes a briefing on the total Request for Proposal (RFP) package. Concurrence from other program offices or government agencies should be obtained.

📐 Key Framework: CWBS/SOW Matrix → a tool to analyze the Statement of Work for completeness by cross-referencing each SOW element with the Contract Work Breakdown Structure

⭐ Key Takeaways

The Statement of Work is the foundational document defining project work scope; internal SOWs are prepared by the project office while external SOWs may be prepared by contractors for customers. Misinterpretations of SOW language — caused by imprecise terms, mixing tasks and instructions, or lacking structure — lead to costly creeping scope and financial losses. To prevent this, SOW writers must use active mandatory language ("shall"), avoid ambiguity, specify responsibilities clearly, and never over-specify or add extraneous requirements. A final management review using the CWBS/SOW matrix is essential to ensure completeness and alignment with the contract structure before the Request for Proposal is released.

🧠 Quick Revision Questions

1. Who typically prepares the Statement of Work for internal company projects, and why?
2. What are the two different SOWs that exist in a competitive bidding environment?
3. List at least four common causes of SOW misinterpretation.
4. What is the recommended term to use for firm requirements: "shall" or "should"?
5. What is the purpose of the CWBS/SOW matrix during the SOW review process?

📘 Lecture 22 — WORK BREAKDOWN STRUCTURE

📖 Overview: This lecture introduces the Work Breakdown Structure (WBS), a fundamental planning tool in project management that breaks work into manageable, independent, integratable, and measurable elements. It explains the six-level indented structure, characteristics of each level, work packages, and the critical role of WBS in cost control, scheduling, and responsibility assignment.

🗂️ Topics Covered

The lecture covers the introduction to Work Breakdown Structure and its importance as a common framework for planning, budgeting, and tracking. It then examines characteristics of various WBS levels (levels 1-6), work package characteristics and their role as the critical management level. Guidelines for contractor-developed WBS are discussed, followed by criteria for developing WBS. The lecture addresses WBS decomposition problems including the risks of excessive detail and the use of "hammock" activities. It concludes with practical uses of WBS for cost control and scope management.

📝 Lecture Summary

22.1 Introduction

To successfully accomplish contract and corporate objectives, a plan is required that defines all effort, assigns responsibility, and establishes schedules and budgets. The detailed planning is established in accordance with company budgeting policy before contractual efforts begin. In planning a project, the project manager must structure work into small elements that are manageable (specific authority can be assigned), independent (minimum interfacing with other elements), integratable (total package can be seen), and measurable in terms of progress.

After project requirements definition, the first major planning step is developing the Work Breakdown Structure (WBS). A WBS is a product-oriented family tree subdivision of the hardware, services, and data required to produce the end product. It is structured according to how work will be performed and reflects how costs and data will be summarized and reported. Preparation of WBS also considers scheduling, configuration management, contract funding, and technical performance parameters. It is the single most important element because it provides a common framework from which: total program can be described as a summation of subdivided elements; planning can be performed; costs and budgets can be established; time, cost, and performance can be tracked; objectives can be linked to company resources; schedules and status-reporting procedures can be established; network construction and control planning can be initiated; and responsibility assignments can be established.

The WBS acts as a vehicle for breaking work down into smaller elements, providing greater probability that every major and minor activity will be accounted for.

The most common WBS is the six-level indented structure:

• Level 1: Total program (composed of a set of projects)
• Level 2: Project level
• Level 3: Task level
• Levels 4-6: Lower levels for detailed control

The summation of activities and costs at each level must equal the total at the next higher level. Program management becomes synonymous with the integration of activities, and the project manager acts as the integrator using WBS as the common framework.

WBS provides the basis for: responsibility matrix, network scheduling, costing, risk analysis, organizational structure, coordination of objectives, and control (including contract administration).

22.2 Characteristics of Various Levels of the Work Breakdown Structure (WBS)

The upper three levels of WBS are normally specified by the customer (if part of Request for Proposal/Request for Quotation) as summary levels for reporting. The lower levels are generated by the contractor for in-house control. Each level serves a vital purpose: Level 1 is used for authorization and release of all work, budgets are prepared at level 2, and schedules are prepared at level 3.

Generalized characteristics for these levels include:

• The top three levels of WBS reflect integrated efforts and should not be related to one specific department. Effort required by departments should be defined in subtasks and work packages.
• The summation of all elements in one level must be the sum of all work in the next lower level.
• Each element of work should be assigned to one and only one level of effort (e.g., foundation construction of a house should be in one project, not extended over multiple levels).
• The level at which the project is managed is generally called the work package level, though work packages can exist at any level below level one.
• WBS must be accompanied by a description of scope of effort, otherwise only those who issue it will fully understand what work must be accomplished. It is common to reproduce the customer's statement of work as the description.
• It is best policy for the project manager to allow all line managers to assess risks in the WBS, as they are usually the recognized experts.

Project managers typically manage at the top three levels and prefer to provide status reports at these levels. Some companies try to standardize the top three levels for every project, with differences only in levels 4-6. This works well for companies with similar projects but is often impossible for companies with diverse projects.

A work package is the critical level for managing WBS, though line managers typically supervise and perform work packages with status reporting provided to the project manager at higher levels. Work packages are natural subdivisions of cost accounts and constitute the basic building blocks used by the contractor in planning, controlling, and measuring contract performance. A work package is simply a low-level task or job assignment that describes work to be accomplished by a specific performing organization or group of cost centers and serves as a vehicle for monitoring and reporting progress.

🔑 Definition — Work Package: The generic term used to identify discrete tasks that have definable end results. Ideal work packages are 80 hours and less than 2-4 weeks, though this may not be possible on large projects.

Work package documentation need not contain complete, stand-alone descriptions; supplemental documentation may augment descriptions. However, descriptions must permit cost account managers and work package supervisors to understand and distinguish one work package from another.

The cost account intersection occurs where the WBS and organizational structure meet, as shown in Figure 22.3. Short-term work packages are desirable for evaluation of accomplishment. This is not intended to force arbitrary cutoffs, but work packages should be natural subdivisions planned according to how work will be done. With short work packages, little assessment of work-in-process is required; evaluation is based mainly on work package completions. Longer work packages make assessment more difficult and subjective unless subdivided by objective indicators like discrete milestones with pre-assigned budget values.

In setting up WBS, tasks should: have clearly defined start and end dates; be usable as a communications tool where results can be compared with expectations; be estimated on "total" time duration, not when tasks must start or end; and be structured to minimize project office control and documentation.

22.3 Characteristics of Work Package

For large projects, planning will be time phased at the work package level of WBS. The work package has the following characteristics:

• Represents units of work at the level where work is performed
• Clearly distinguishes one work package from all others assigned to a single functional group
• Contains clearly defined start and end dates representative of physical accomplishment
• Specifies a budget in terms of dollars, man-hours, or other measurable units
• Limits work to relatively short periods to minimize work-in-process effort

📐 WBS Numbering System Example: A simple WBS numbering system follows the work breakdown: 01-03-00 represents project 3 of program 01, while 01-03-02 represents task 2 of project 3. This numbering system is not standard; each company may have its own system depending on how costs are controlled.

📌 Example: Table 22.1 shows a WBS for New Plant Construction and Start-Up where the first number (01) represents the total program, the second number represents the project, and the third identifies the task.

The preparation of WBS is not easy. WBS is a communications tool providing detailed information to different management levels. If it does not contain enough levels, integration of activities may prove difficult. If too many levels exist, unproductive time will be spent. Each major work element should be considered by itself. WBS establishes the number of required networks for cost control. On many programs, the customer establishes the WBS.

22.4 Guidelines for WBS by Contractor

When a contractor is required to develop a WBS, certain guidelines must be considered:

• Complexity and technical requirements of the program (statement of work)
• Program cost
• Time span of the program
• Contractor's resource requirements
• Contractor's and customer's internal structure for management control and reporting
• Number of subcontracts

Applying these guidelines serves to identify the complexity of the program. These data must then be subdivided and released with detailed information to different organizational levels. WBS should follow specified criteria because although the program office prepares WBS, the actual work is performed by the doers, not the planners. Both doers and planners must be in agreement on what is expected.

22.5 Criteria for Developing Work Breakdown Structure (WBS)

Following is a sample listing of criteria for developing WBS:

• WBS and work description should be easy to understand
• All schedules should follow the WBS
• No attempt should be made to subdivide work arbitrarily to the lowest possible level; the lowest level should not have a ridiculous cost compared to other efforts
• Since scope can change during a program, maintain flexibility in the WBS
• WBS can act as a list of discrete and tangible milestones so everyone knows when milestones are achieved
• Level of WBS can reflect the "trust" you have in certain line groups
• WBS can be used to segregate recurring from nonrecurring costs
• Most WBS elements (at the lowest control level) range from 0.5 to 2.5 percent of the total project budget

22.6 Work Breakdown Structure (WBS) Decomposition Problems

There is a common misconception that WBS decomposition is an easy task. In WBS development, the top three levels (management levels) are usually roll-up levels. Preparing templates at these levels is becoming common practice. However, at levels 4-6, templates may not be appropriate for the following reasons:

• Breaking work down to extremely small work packages may require creating hundreds or thousands of cost accounts and charge numbers. This could increase management, control, and reporting costs to a point where costs exceed benefits. While a typical work package may be 200-300 hours and approximately two weeks in duration, consider a large project with more than one million direct labor hours.
• Breaking work down to small work packages can provide accurate cost control if, and only if, line managers can determine costs at this level of detail. Line managers must have the right to tell project managers that costs cannot be determined at the requested level of detail.
• WBS is the basis for scheduling techniques like Arrow Diagramming Method (ADM) and Precedence Diagramming Method (PDM). At low WBS levels, interdependencies between activities can become so complex that meaningful networks cannot be constructed.

🔑 Definition — Hammock Activity: An activity that encompasses several activities where exact cost identification cannot be accurately determined. For example, "management support" or "project office" includes overall project management, data items, management reserve, and possibly procurement. The advantage is that charge numbers are under direct control of the project manager.

Another misconception is that work packages should be approximately 80 hours and less than two weeks to a month. While this may be true on small projects, it would necessitate millions of work packages on large jobs, which is impractical even if line managers could control packages of this size.

Cost analysis down to the fifth level is advantageous from a cost control viewpoint. However, the cost to prepare data to each lower level might increase exponentially, especially if the customer requires data in a specified format not part of the company's standard operating procedures. Level-5 work packages are normally for in-house control only. Some companies bill customers separately for each level of cost reporting below level 3.

WBS can be subdivided into sub-objectives with finer divisions of effort as we go lower. By defining sub-objectives, we add greater understanding and clarity of action for individuals who will complete the objectives. When work is structured, understood, easily identifiable, and within individual capabilities, there will be high confidence the objective can be reached.

WBS can also structure work for objectives like lowering cost, reducing absenteeism, improving morale, and lowering scrap factors. In such cases, the lowest subdivision becomes an end-item or sub-objective, not necessarily a work package as described.

💡 Why this matters: Understanding the balance between sufficient detail for control and excessive detail that creates management overhead is critical for effective WBS design.

22.7 Uses of Work Breakdown Structure (WBS)

Once WBS is established and the program is "kicked off," it becomes very costly to add or delete activities or change reporting levels because of cost control. Many companies do not give careful forethought to the importance of a properly developed WBS and ultimately risk cost control problems downstream.

One important use of WBS is that it serves as a cost control standard for any future activities that may follow on or be similar. A common mistake is combining direct support activities with administrative activities. For example, a department manager for manufacturing engineering may provide administrative support (attending team meetings) throughout the program. If this administrative support is spread over each project, a false picture is obtained of actual hours needed to accomplish each project. If one project is canceled, support man-hours for the total program would be reduced when, in fact, the administrative and support functions may be constant regardless of the number of projects and tasks.

WBS accompanying customer Requests for Proposals (RFPs) often contains much more scope of effort than existing funding will support. This is done intentionally by the customer hoping a contractor may be willing to "buy in." If the contractor's price exceeds customer funding, eliminating activities from WBS must reduce scope of effort. By developing a separate project for administrative and indirect support activities, the customer can easily modify costs by eliminating direct support activities of the canceled effort.

Finally, the usefulness and applicability of WBS varies. Many companies and industries have been successful in managing programs without WBS, especially on repetitive-type programs.

⭐ Key Takeaways

The Work Breakdown Structure is the single most important planning element in project management, providing a common framework for defining all work, assigning responsibility, and establishing budgets and schedules. The six-level indented structure works from total program (level 1) down to work packages (levels 4-6), with the critical management point being the work package level where actual work is performed and controlled. Work packages should have clear start/end dates, budgets, and be short-term (ideally 80 hours, 2-4 weeks) to minimize work-in-process assessment problems. Proper WBS development requires balancing sufficient detail for control against the risk of creating excessive cost accounts that increase management costs beyond benefits. The WBS must remain flexible as scope changes, and careful forethought is essential since modifying WBS after program kickoff is very costly.

🧠 Quick Revision Questions

1. What are the four characteristics that project work elements should have, and why is each important for project control?
2. Explain the six-level indented structure of WBS: what does each level represent, and who typically specifies the upper three levels versus the lower levels?
3. What is a work package, what are its key characteristics, and why are short-term work packages (80 hours, 2-4 weeks) desirable?
4. What problems can arise when decomposing WBS to extremely detailed work packages at levels 4-6, and how do "hammock activities" help address these problems?
5. Why is it important to separate direct support activities from administrative activities when developing WBS, and what cost control risk arises if they are combined?