π 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:
-
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.
-
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.
-
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
- What are the nine essential elements of a project plan as described in this lecture?
- 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?
- List at least five of the eight types of project objectives that should be established to facilitate detailed planning.
- What is the primary purpose of documenting "Key Assumptions" in the Planning Basis section of the project plan?
- 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
- What is the recommended range for the number of major activities in a project plan, and why is this range considered practical?
- Explain the difference between an "outcome" (or event) and a "task" (or activity) in the context of project planning.
- List the four basic reasons for project planning as described in the lecture.
- Define a "Gozinto Chart" and explain how it relates to the concept of a hierarchical planning system.
- 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
- What are the three subcategories of the environment analyzed when identifying strategic project variables?
- What is the primary challenge associated with tracking external variables at the program level?
- Why might top-level officers resist participating in the identification of strategic planning variables?
- According to the lecture, what is the purpose of identifying and classifying strategic variables?
- 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:
- 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.
- 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.
- 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
- What are the two levels at which project planning takes place according to the corporate cultural approach?
- List the three types of decisions that can be made at an end-of-phase review meeting.
- What are the two critical factors involved in the conceptualization phase, and what is the recommended time duration for a brainstorming session?
- What are the three primary responsibilities of a line manager in the planning process?
- Name at least four of the seven typical problems in objective setting discussed in this lecture.