π 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:
- Introduce the proposal, telling the readers its purpose and contents.
- Present the background β the problem, opportunity, or situation.
- State what you propose to do about the problem.
- Discuss the benefits of doing the proposed project.
- Describe exactly what the completed project would consist of.
- Discuss the method and theory behind the approach.
- Provide a schedule, including major milestones.
- Briefly list your qualifications for the project.
- List the costs of the project and resources needed.
- 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
- What are the ten common sections found in proposals, and what is the strategic logic behind their organization in a winning proposal?
- List and explain the seven key ingredients of a winning proposal.
- What are the four main proposal formats, and which format should be used for internal versus external proposals?
- Describe the "story board" technique and its components. What are its benefits for proposal preparation?
- 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:
- Type of project
- Its capacity and location(s)
- Scope of work to be performed
- Preliminary cost estimation
- Site visitation report
- Preliminary schedule of major objectives
- Pertinent contract requirements
- Special design and/or construction requirements
- Climate restrictions
- Environmental study, feasibility study reports, etc
- 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:
- Coordination Procedure (CP): Also known as Job Instructions, it includes administrative procedures in projects.
- 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
- Definition Phase: Problem defined in request document. Example: House needs heating, plumbing, lighting, storage, etc.
- Analysis Phase: Produces functional specifications (deliverable). Example: Location of ventilators, air conditioner, outlet for phone, etc.
- Design Phase: System proposed to solve problem; system divided into functional components; components are interconnected. Expectation: Rooms, ventilation, wiring, etc.
- Programming Phase: Actual work conducted to bring system into being. Expected: Building of house.
- System Test Phase: Brings pieces together and tests them as a whole. House Example: Test plumbing, electricity, roof, etc.
- 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).
- 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
- What are the four essential information requirements that must be available at project initiation for effective total program planning?
- What four key elements must a detailed, written "Plan of Execution (P of E)" show?
- What are the two specific components of early-stage documentation that a project manager must prepare?
- According to the house-building example, what type of problem requires negotiation during the Acceptance Phase?
- 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
- List the nine major components of the general planning phase.
- What are the three typical time horizons for planning (strategic, tactical, operational)?
- What is the key output of the initial project coordination meeting, and what must it include?
- Why is it considered a "betrayal of trust" to change an approved project plan without informing the contributing units?
- Name three specific items that a project manager should consider when creating a "Procurement Planning" checklist.