Monday, May 19, 2014

Chapter 5 Developing the Schedule

Estimate Activity Resources

Resources include
People, materials, equipment, facilities

Influence on the durationimportant
Availability of the resources
Types of resources
Sufficient quantities of resources for the activity durations
Potential conflicts with other projects may cause
Involve person with expertise in resource estimate
Estimates influence costs

It is necessary to estimate the types and quantities of resources that will be required to perform each specific activity in a project.
Resources include people, materials, equipment, facilities, and so forth.
Having this information is essential in estimating how long it will take to perform each activity and the project as a whole.
A number of factors influence the duration of an activity:
Availability of the resources
Types of resources
Sufficient quantities of resources for the durations of the activities
Potential conflicts with other projects that may cause a delay
When estimating the types and quantities of resources required for each specific activity, it is valuable to involve a person who has expertise or experience with the activity.
Estimated activity resources will also be used later for estimating activity costs and determining the project budget.

Estimate Activity Durations

Duration must be the total elapsed time
Time for the work to be done plus any associated waiting time


Builds buy-in from the person and generates commitments
Avoids bias that may be introduced by having one person estimate the durations for all of the activities
The designated individual uses experience to estimate the durations
Historical data can be used as a guide



The estimated duration should be aggressive yet realistic.

Durations should not be too short to try to win the contract
Inflated estimated durations is not good practice
Project manager may not be able to negotiate shorter durations
Some activities will take longer and others shorter durations than planned
As the project progresses, level of confidence for accuracy increases

Once the types and quantities of resources are estimated for each activity, estimates can be made for how long it will take to perform the activities.
The estimated duration for each activity must be the total elapsed time—the time for the work to be done plus any associated waiting time.
The figure above depicts the activity estimated duration for varnishing floors.
It is a good practice to have the person who will be responsible for performing a specific activity estimate the duration for that activity.
Builds buy-in from the person and generates commitments
Avoids bias that may be introduced by having one person estimate the durations for all of the activities
It is important to designate an experienced individual to estimate the durations for all the activities for which the organization or subcontractor is responsible in large projects.
Historical data can be used as a guide in estimating the durations of similar activities.
Estimated duration should be aggressive yet realistic.
Inflating estimated durations in anticipation of the project manager negotiating shorter durations is not a good practice.
Throughout the performance of the project, some activities will take longer than their estimated duration, others will take less time than estimated, and a very few may conform to the estimated duration exactly.
At the beginning of the project, it may not be possible to estimate the durations for all activities with a high level of confidence.
The project team can progressively elaborate the estimated durations as more information is becomes available to allow for more accurate estimated durations.


Establish Project Start and Finish Times

Define the overall window for project completion
May not want to commit to a specific date
Project not start until customer has approved the contract
Delay in contract signing may impact project start
Set finish time as number of days from project start

It is necessary to select an estimated start time and a required completion time for the overall project. This is important in order to establish a basis from which to calculate a schedule using the estimated durations for the activities.
Define the overall window, or envelope, of time in which the project must be completed.
The contractor may not want to commit to completing the project by a specific date until the customer has approved the contract.
A delay in signing will likely impact the start date of the project.
The finish time should be stated as a number of days from the start of the project.

Total Slack

Sometimes called float
The difference between EF time of last activity and the project required completion time
Negative slack almost late
Lack of slack over the entire project
Amount of time an activity must be accelerated
Positive slack got plenty of time
Maximum amount of time that the activities on a particular path can be delayed without jeopardizing on-time completion

Total slack is sometimes called float.
It is the difference between EF time of last activity and the project required completion time.
Total slack is calculated for each of the activities by finding the difference between the EF time of the activity and the LF of the activity.
You also look at the difference between the ES and LS of the activity.
Negative slack indicates:
A lack of slack over the entire project
The amount of time an activity must be accelerated to complete the project by the required completion time
Positive slack indicates the maximum amount of time that the activities on a particular path can be delayed without jeopardizing completion of the project by the required completion time.
If the total slack is zero, the activities on the path do not need to be accelerated, but cannot be delayed.

Critical Path (what must be accomplished)

Longest path in the overall network diagram
Find which activities have the least amount of slack

The critical path is this longest path in the overall network diagram.
One way to determine which activities make up the critical path is to find which ones have the least amount of slack.

Incorporate Changes into Schedule

Changes may impact the schedule
Initiated by customer or project team
Result from
Early change may have less impact than later change
Manage requested changes
Estimate impact
Obtain customer approval
Revise project plan, schedule, and costs

Throughout a project, changes may occur that impact the schedule.
Changes might be initiated by the customer or the project team, or they might be the result of an unanticipated occurrence.
Changes requested early in the project may have less of an impact on schedule and budget than those requested later in the project.
When the customer requests a change, the contractor or project team should estimate the impact on the project schedule and budget and then obtain customer approval before proceeding.
If the customer approves the proposed revisions to the project schedule and budget, then any additional activities, revised estimated durations, and revised estimated resources and associated costs should be incorporated into the project schedule and budget.
With respect to the project schedule, changes can result in the addition or deletion of activities, re-sequencing of activities, changes to estimated durations for specific activities, or a new required completion time for the project.

Chapter 4 Defining Scope, Quality, Responsibility, and Activity Sequence



Defining Scope, Quality, Responsibility, and Activity Sequence


Planning process is based on the project objective
§  Establishes what is to be accomplished
§  Often stated in the project charter or RFP
§  Is the tangible end product
Project objective includes
§  Expected benefits
§  Primary project end product or deliverable
§  Date required to be completed
§  Budget
Changes agreed upon by customer and contractor

The planning process is based on the project objective.
The project objective establishes what is to be accomplished.
Often the project objective is stated in the project charter or RFP.
It is the tangible end product that the project team or contractor must produce and deliver in order for the sponsor or customer to achieve the expected benefits from implementing the project.
The project objective should include the following elements:
Expected benefits that will result from implementation of the project and define success
Primary project end product or deliverable
Date by which the project is required to be completed
Budget within which the project must be completed
Situations can arise where the project objective needs to be modified as the project proceeds because of extenuating circumstances or new information. The project manager and the customer must agree on all changes to the project objective. Any such changes might affect the remaining work scope, deliverables, completion date, and final cost.

Project Scope
Defines what needs done
Includes
§  Items contained in project charter, RFP, proposal
§  More detail
Establishes common understanding of scope with stakeholders


Project Scope Document

Usually contains
§  Customer requirements
§  Statement of Work
§  Deliverablesimportant
§  Acceptance Criteria
§  Work Breakdown Structuresuper important)(task from point A to B
Establishes baseline
Change control system to avoid scope creep  control

The project scope defines what needs to be done.
A project scope document includes many of the items contained in the project charter, RFP, or contractor’s proposal, but in much greater detail. The document is valuable for establishing a common understanding among project stakeholders regarding the scope of the project.
The project scope document usually contains the following sections:
Customer requirements define the functional or performance specifications for the project’s end product and other project deliverables.
It should also include or reference applicable technical specifications, standards, and codes that must be used and met regarding quality and performance of the project work and deliverables.
Statement of Work (SOW) defines the major tasks or work elements that will need to be performed to accomplish the work that needs to be done and produce all the project deliverables.
Deliverables are the products or outputs that the project team or contractor will produce and provide to the customer during and at the completion of the performance of the project.
Acceptance criteria for all project deliverables must be described in greater detail than what is stated in the project charter or request for proposal
Work Breakdown Structure (WBS) is a hierarchical decomposition of the project work scope into work packages that produce the project deliverables.
The agreed-upon project scope document establishes the baseline for any changes that may be made to the scope during the performance of the project.
A change control system needs to be established to define how changes will be documented, approved, and communicated. The project team or contractor must avoid scope creep, which is informally making changes to the project scope without appropriate approval.

Why should scope creep be avoided?

Increase cost and time
Informal changes to the project
No approvals for changes
Additional work that is not documented
May cause errors
May cause rework
Could make the project overtime and over budget

It is often said that some people think they never have enough time to do the work right the first time, but then must take the time later to redo it correctly—haste makes waste!
when speed up, you may make mistake and do it again

Clearly list quality standards
Have monitors in place to see if the work is meeting quality standards
Submit sample work to be sure work meets standards
If it means a higher quality product, determine the effects and costs of a later delivery

Create Work Breakdown Structure
Deliverable-oriented hierarchical decomposition I have bunch of task to do and have a order
Organize project work and deliverables (when do I need this done?)
Create logical groupings
Subdivide into more manageable components
§  Deliverable is output of work package
§  Resource requirements and durationsimportant can be assigned  define resource, money ,people
§  Accountability can be assigned
§  Project manager can monitor and control    need boss Admin
Graphic chart or indentured list

Once the project scope document has been agreed on and prepared, the next step in the planning phase is to create a detailed work breakdown structure (WBS)
This is a deliverable-oriented hierarchical decomposition of the project work scope into work packages, or activity groupings, that produce the project deliverables.
Creating a WBS is a structured approach for organizing all the project work and deliverables into logical groupings. This helps to subdivide the deliverables into more manageable components called work items, to help ensure that all tasks required to complete the project are identified and included in the baseline project plan.
The WBS should be deconstructed to a level that identifies individual work packages for each specific deliverable listed in the project scope document.
Dividing a project into work packages and work items helps a contractor increase the level of confidence that:
All the activities that need to be performed to produce the deliverable can be defined
The types and quantities of resources can be determined
The associated activity durations and costs can be reasonably estimated.
Work items should be broken down to the level at which a single organization (marketing communications, materials engineering, human resources, a subcontractor, etc.) or individual can be assigned responsibility and accountability for accomplishing the work package.
The WBS can be created using a graphic chart format or as a list.

WBS with Breakdown to Different Levelslack of duration



Graphic Chart


Indentured List
WBS
The top figure depicts the WBS for the consumer market study project example. This project is also the example used in the Microsoft Project appendices.
Have students examine the relationship between this figure and the entries in the Microsoft Project task list.
The bottom figure depicts an indentured list for the work breakdown structure.
For each of the work packages, the deliverable is listed.
This format is helpful for large projects where a diagram would become too large and unwieldy.

Planning for Information Systems Development

Definition
Computer-based system
§  Accepts data as input
§  Processes the data
§  Produces useful information
Examples
§  Computerized order entry
§  E-commerce
§  Automatic teller machines
§  Billing, payroll, and inventory

Process

Plan, execute, and control
Systems Development Life Cycle
§  Problem definition
§  System analysis
§  System design
§  System development
§  System testing
§  System implementation

Only one approach is having everybody create new.

Organization gets smarter; they bought order processing systems, etc

Outside company to create a system fit to you. You become only System testing and System implementation.

Outsourcing is cost effective that gives me 98% I want.

The Microsoft Project example will continue through chapters 4 – 8. It highlights the concepts for each chapter in the example. The Microsoft Project file for the example is available with the instructor materials.
An information system (IS) is a computer-based system that accepts data as input, processes the data, and produces useful information for users.
Information systems include computerized order entry systems, e-commerce systems, automatic teller machines, and billing, payroll, and inventory systems.
The development of an IS is a challenging process that requires extensive planning and control to ensure that the system meets user requirements and is finished on time and within budget.
A project management planning tool, or methodology, called the systems development life cycle (SDLC) is often used to help plan, execute, and control IS development projects.
It consists of the following steps:
Problem definition -- Data are gathered and analyzed and problems and opportunities are clearly defined.
System analysis -- The development team defines the scope of the system to be developed, interviews potential users, studies the existing system (which might be manual), and defines user requirements.
System design -- Several alternative conceptual designs are produced and evaluated. The best is selected for further design and development.
System development -- The actual system is brought into existence.
System testing – This step involves looking for logical errors, database errors, errors of omission, security errors, and other problems that might prevent the system from being successful.
System implementation -- The existing system is replaced with the new, improved, system and users are trained.


IS Example: Responsibility Assignment Matriximportant

Number means you cannot do 3 unless you finished 1 and 2.

Here we see the responsibility assignment matrix for the project, with the primary and secondary responsibilities for each task assigned.
Make sure that students note that all the tasks in the WBS appear in the responsibility assignment matrix.

Task List and Predecessors
This figure depicts a list of all tasks to be completed, with the immediate predecessor for each task listed to the right of the task.
Have the students examine the interdependencies of the tasks.

Project Management Information Systems
A wide variety of affordable project management information systems are available for purchase.
These systems allow the project manager and the project team to plan and control projects in a completely interactive mode.
Planning and testing different options for task durations, dependencies, constraints, resources, schedules, and costs can be completed in a project management information system.
Information systems help project managers to create reports, change management, network diagrams, and Gantt charts.
Project management information systems also interface with other software applications.

Appendix A contains information related to project management information systems.


Critical Success Factors

Plan the work and then work followthe plan
WBS, got resource, knew duration 

Participation builds commitment
Get people involved in it.

The project must have a clear objective

Major stakeholderleader of organization

Having a quality plan and monitor it.


Thursday, May 15, 2014

Additional Post for Chapter 3

Additional Post for Chapter 3


   By reading this chapter, I learnt some tips when creating a winning proposal. A good proposal is a selling document; it is not a technical report.

    The contractor must understand what the customer is looking for and provide the greatest value to them. The project must be complete within budget and on schedule.

    For proposal preparation, we need to consider some factors of content. From technology perspective, understanding the problem is the first step, and then provides solutions to determine the client's benefits. If I cannot meet the specific needs of customers, propose alternative options should be set as an exception.

    The management part of the proposal includes the description of work tasks, deliverable, and project schedule with Gantt chart to track. Then describe how to organize the work with suitable resources and equipment to perform the project.  In addition, we have to calculate labor, raw materials, outsources, equipment, facilities, and human resource costs.

    After the submission of the application, the customer will be determined by evaluating the optimal choice with proposal evaluation scorecard.

    Under normal circumstances, There are two type of contract, fixed-price contracts is less risky, cost reimbursable contracts could fit slightly to riskier projects.

Additional Post for Chapter 2

Additional Post for Chapter 2

    Those Possible Elements of Project Charter provide a conceptual basis for me to help sponsor approval to go forward with the project.


    The sample Project Charter and especially a sample of RFP shown in the text book are very useful to my learning process. The quality of an RFP is very important to successful project management because it clearly delineates the deliverable that will be required. It describes each of the proposal components in great detail and well organized. This must provides me a good guide since I learn each 12 step can be used in real workplace. Quite often the client has little idea about their needs, they lack of clear vision and blueprint of the whole project. RFP helps me obtain what the clients really want Instead of just oral taking.


    For soliciting proposals, I learnt customers must be careful not to provide information to only some of the contractors because it would give these contractors an unfair competitive advantage in preparing their proposals.

Monday, May 12, 2014

Chapter 3 Developing Project Proposals

Chapter 3 Developing Project Proposals

Building relationship with customers and partnersimportant

Customer gives you RFP
Why we need a good relationship with customer.
They ask to you to do another one, because they have trust on you.

Foundation for successful funding and opportunities
Requires good listening and constant learning
Frequent and regular contact, express appreciation for the client’s time
Trust is key and ethics are imperative
First impression is important
Problem solving and credibility grows with good performance
Partner with several key individuals in an organization

Generally speaking, customers (clients) and partner organizations prefer to work with people they know and trust.
Relationships establish the foundation for successful funding and contract opportunities.
Relationship building requires being proactive and engaged.
It requires face-to-face contacts; it cannot be done as effectively through e-mail or phone conversations. 
Relationship building requires being a good listener and a good learner. When you are with clients, ask questions and listen. Make the client feel good. Empathize with their issues, whether they are business or personal.
Contacts with potential clients should be frequent and regular– not just when there is a current opportunity for funding or just before they will be issuing a RFP. During contacts, do not focus on discussing potential contract opportunities.
After meeting with a client, always express your appreciation and thank them for making the time to meet with you.
Establishing and building trust is key to developing effective and successful relationships with clients and partners. One way to foster this is to be reliable and responsive. 
Ethical behavior in dealing with clients and partners is also imperative for building trust.
The first impression you make on a client is pivotal to developing a continuing and fruitful relationship.
Clients want to work with people who can solve problems, not with those who merely identify them.
Build credibility based on good performance.
Always put the client first. Clients want to be confident that any projects they undertake with the contractor will be successful, will involve a good working relationship with the contractor, and will help the clients achieve their business goals.
It is advisable not to rely on a good relationship with just one individual in a client or partner organization, but rather to build relationships with several key people in a client or partner organization, since key individuals may leave the organization while others become more influential.

Pre-RFP/Proposal Marketing

Begin developing the relationship before RFP is prepared
§  Can help client identify needs
§  Better position to win the contract
§  Develop a more clearly focused response to RFP
Pre-RFP and pre-proposal efforts are business development
§  No cost to the customer
§  Help build the relationship
Unsolicited proposals and uncompetitive contracts
§  Result of identified needs and problem solving
§  Eliminates preparation of an RFP and soliciting process

Contractors whose business depends on creating winning proposals in response to business or government RFPs should not wait until formal RFP solicitations are announced by customers before starting to develop proposals.
Contractors need to develop relationships with potential customers long before the customers prepare RFPs.
Contractors should maintain frequent contacts with past and current customers and initiate contacts with potential new customers.
A contractor who is familiar with a customer’s needs and requirements can prepare a better proposal in response to the customer’s RFP.
These pre-RFP or pre-proposal efforts by a contractor are considered marketing or business development and are performed at no cost to the customer.
In some cases, the contractor may prepare an unsolicited proposal and present it to the customer.
If the customer is confident that the unsolicited proposal will solve the problem at a reasonable cost, the customer may simply negotiate a contract with the contractor to implement the proposal, thus eliminating the preparation of an RFP and the subsequent competitive proposal process.
Whether the goal is winning a competitive RFP or obtaining a noncompetitive contract from a customer, a contractor’s pre-RFP/proposal efforts are crucial to establishing the foundation for eventually winning a contract from the customer to perform the project.

Decision to Develop a Proposal
Development is costly and time consuming (not for most business, they have a template, because you have done the similar work before)
Contractors must be realistic about their probability of winning a contract (salesman are liar)
Evaluate bid/no-bid decision
Many non-winning proposals hurt reputationYou got a lot of selective
May be hard to decide to no-bid an RFP

The development and preparation of a proposal can be costly and time-consuming.
Contractors interested in submitting a proposal must be realistic about the probability of being selected as the winning contractor.
Evaluating whether or not to go forward with the preparation of a proposal is sometimes referred to as the bid/no-bid decision.
Contractors need to be realistic about their ability to prepare proposals and about the probability of winning the contract because submitting a lot of non-winning proposals in response to RFPs can hurt a contractor’s reputation.
Sometimes the hardest thing for a contractor to do is to decide to no-bid an RFP.

Creating a winning proposal

Selling document
The best idea to solve the problem
Highlight unique factors
Emphasize benefits to the customer
Be simple and concise (really important)
Addresses requirements from RFP

Be realistic 

The proposal process can be highly competitive and a proposal is a selling document - not a technical report.
In the proposal, the contractor must convince the customer that the contractor is the best one to solve the problem.
The contractor should highlight the unique factors of its proposal that differentiate it from competing contractors.
The proposal should always emphasize the benefits to the customer.
Proposals should be written in a simple, concise manner.
Proposals must be specific in addressing the customer’s requirements as laid out in the RFP.
Proposals must be realistic, in terms of the proposed scope, cost, and schedule, in the eyes of the customer.

Proposal contents
Three sections
  Technical, management, cost
  Missing one is executive summarygive this to your boss

Detail level
  Depends on complexity of the project (certain level of detail)
  Requirements from the RFP

Bottom line is cost

The amount of detail the contractor includes will depend on the complexity of the project and the requirements stipulated by the RFP.

Technical Section
Understand the need
Proposed approach or solution
Benefits to the customer

The objective of this section is to convince the customer that the contractor understands the problem or need and can provide the least risky and most beneficial solution. The technical section should contain the following elements:
Understanding of the need—the contractor must show the customer that they thoroughly understand the problem to be solved.
Proposed approach or solution—the proposal should describe the approach or methodology that would be used in developing the solution.
Benefits to the customer—the contractor should state how the proposed solution or approach would benefit the customer and achieve the project’s success criteria or expected outcomes, including cost savings; reduced processing time; reduced inventory; better customer service; reduced errors; improved safety conditions; more timely information; reduced maintenance, etc.

Management Section
Description of work tasks
Deliverables
Project schedule
Project organization
Related experience
Equipment and facilities

The objective of the management section is to convince the customer that the contractor can do the proposed work and achieve the intended results. The management section should contain the following elements:
Description of work tasks—the contractor should define the major tasks that will be performed in carrying out the project.
Deliverables—the contractor should include a list of all deliverables that will be provided during the project (such as reports, drawings, manuals, and equipment).
Project schedule—the contractor should provide a schedule for performing the major tasks required to complete the project.
The task schedule can be given in any one of several formats: a list of tasks with their estimated start and completion dates, a Gantt chart, or a network diagram.
Project organization—the contractor should describe how the work and resources will be organized to perform the project.
An organization chart, resumes of the key people, and a responsibility matrix are often helpful.
Related experience—the contractor should provide a list of similar projects it has completed and the dollar value of those contracts.
Equipment and facilities—the contractor may want to provide a list of the equipment and special facilities it has in order to convince the customer that it possesses the necessary resources.

Cost Section(Bottom line
Include estimated costs
§  Labor
§  Materials
§  Equipment
§  Facilities
§  Subcontractors and consultants
§  Travel
§  Documentation
§  Overhead
§  Escalation
§  Contingency

§  Fee or profit

The objective of the cost section of the contractor proposal is to convince the customer that the contractor’s costs for the proposed project are realistic and reasonable. The cost section usually consists of tabulations of the contractor’s estimated costs for such elements as the following:
Labor—the estimated costs for the various classifications of people who are expected to work on the project
It might include the estimated hours and hourly rate for each person or classification.
Materials—the cost of materials the contractor needs to purchase for the project
Equipment— the cost of equipment that must be purchased to complete the project
Facilities—sometimes the contractor will have to rent special facilities or specialty space for the project team.
Subcontractors and consultants—when contractors do not have the expertise or resources to do certain project tasks, they may outsource some of the work to subcontractors or other consultants.
Travel—such as airfare, lodging, and meals if trips are required during the project
Documentation—some customers want the contractor to show separately the costs associated with the project documentation deliverables.
This would be the cost of printing manuals, drawings, reports, or the cost of DVDs.
Overhead—contractors will add a percentage to costs of the above items to cover the indirect costs of doing business (such as insurance, depreciation, accounting, general management, marketing, and human resources).
Escalation—for large projects that are expected to take several years to complete, the contractor needs to include the costs of escalation in wage rates and materials costs over the length of the project.
Contingency or management reserve—an amount the contractor may want to include to cover unexpected items that have been overlooked.
Fee or profit— all the above items are costs. The contractor must add an amount for its fee or profit.
The total cost plus the contractor’s fee is the contractor’s price for the proposed project.
Cost estimates should be reasonable and realistic. If possible, it is good practice to have the person who will be responsible for the major work tasks estimate the associated costs.

Pricing Considerations
Competition
Price
§  Not overpriced or underpriced
Factors
§  Reliability of cost estimates
§  Risk
§  Value of project to the contractor
§  Customer’s budget

§  Competition level

When contractors prepare a proposal, they are generally competing with other contractors. There are three main factors that contractors should consider when setting a price for a proposal: competition, prices compared to competitors, and other factors like risk and the customer’s budget.
Contractors need to be careful not to overprice the proposed project, or else the customer may select a lower-priced contractor.
They must be equally careful not to underprice the proposed project; otherwise, the contractor may lose money.
The contractor must consider the following items when determining the price for the proposed project:
Reliability of the cost estimates—the level of confidence that the total cost for the proposed project is complete and accurate
Risk - if the proposed project involves an endeavor that has not been undertaken before, it may be necessary to include a large amount of contingency funds.
Value of the project to the contractor—there may be situations in which the contractor is willing to live with a low price.
For example, in order to get a contract so it will not have lay off workers.
Customer’s budget—a proposal should not exceed what the customer has available.
Competition—if many contractors are expected to submit, it may be necessary to submit a price that includes only a small profit to increase the chances of winning the contract.

Simplified project proposal

Complex
Large number of pages
Defined sections
Charts and figures
Tables of information

Simplified
Statement of the customer’s need
AssumptionsI need that relative company help me, or need more information and resources
Project scope
Deliverable
Resources
Schedule
Price
Risks
Expected benefits

Sometimes a proposal is complex for a large multi-million dollar project. These proposals will be lengthy, with many defined sections, charts, figures and tables.
At other times, the proposal may not need to be complex. A simplified or basic proposal may be appropriate and sufficient.
All proposals should include the following elements as a minimum:
Statement of the customer's need— should clearly describe the contractor's understanding of the customer's need or problem and reference any information or data to support the need
Assumptions– state any assumptions that may affect the contractor’s scope, schedule, or price
Project scope— describe the contractor’s approach to addressing the customer’s need or solving the problem, define specifically what work tasks the contractor proposes to do, and outline how the contractor expects the customer to be involved throughout the project
Deliverables— list all the tangible products or items it will provide to the customer during the performance of the project
Resources— types of expertise and skills that the contractor will utilize on the project, including any key subcontractors, consultants, or suppliers
Schedule— list of key milestones with their target dates or cycle time from the start of the project in sufficient detail to demonstrate a well-thought-out plan
Price— indicate the bottom-line price to perform the project. Emphasize the value provided and not on how low, or “cheap,” the price is.
Risks—identify potential concern about any risks that have a high likelihood of occurrence or a high degree of potential impact. Try to demonstrate that the contractor has experience with these risks and outline a realistic approach to dealing with them in the project.
Expected benefits— pull together information from the preceding sections and make a case to justify the “value” of the proposal in terms of expected quantitative benefits, such as return on investment, payback, cost savings, an increase in productivity, reduced processing times, faster time-to-market, and so on.
The focus of the proposal should be on quality of the content—clear, concise, and convincing—rather than quantity or number of pages.
Many simplified project proposals range from 4 to 8 pages, and they are usually less than 20 pages.
It is appropriate to attach appendices for items such as resumes of key people who will be assigned to the project, back-up details for cost estimates, or a list of past related projects and associated references.

Proposal submission and follow-up

Submission
MUST be on time
Formatted properly easy to read
Sent in manner required Hard copies, email, Electronic form
Two sets by different delivery methods

Follow-up
Be proactive
Professional manner
Follow RFP guidelines

Proposals should be:
Submitted on time
Late or incomplete proposals are often not accepted
Formatted properly
In the manner specified
Possibly deliver two sets by different delivery methods
Depending on the dollar value of the proposal, some contractors have been known to hand-deliver the proposal or send two sets of proposals by different express mail services.
Contractors must continue to be proactive even after the proposal is submitted.
Any follow-up needs to be done in a professional manner and in accordance with the RFP guidelines.

Contracts

Agreement

Contract must be signed before starting work
Establishes communication
Agreement of deliverable for a certain price

Types
Fixed price
Price remains fixed
Low risk for customer
High risk for contractor
For well-defined projects with little risk

Cost-reimbursement (Flexibility, better for contractor)
Price for actual costs
High-risk for customer
Low risk for contractor

For higher risk projectslots more he didn’t tell you

Just because the contractor has been selected as the winner does not mean the contractor begins the work right away. Before the project can proceed, a contract must be signed between the customer and the contractor.
A contract is a vehicle for establishing good customer-contractor communications and arriving at a mutual understanding and clear expectations to ensure project success.
It is an agreement between the contractor, who consents to provide a product or service (deliverables), and the customer, who agrees to pay the contractor a certain amount in return.
The contract must clearly spell out the deliverables the contractor is expected to provide.
There are basically two types of contracts: fixed price and cost reimbursement.
In a fixed-price contract, the customer and the contractor agree on a price for the proposed work.
The price remains fixed unless the customer and contractor agree on changes.
This type of contract is low risk for the customer, since the customer will not pay more than the originally agreed-upon price.
This type of contract is high risk for the contractor because, if the cost of completing the project is more than originally planned, the contractor will make a lower profit than anticipated— or may even lose money.
Fixed-price contracts are most appropriate for projects that are well defined and entail little risk.
In a cost-reimbursement contract, the customer agrees to pay the contractor for all actual costs (labor, materials, and so forth), regardless of amount, plus some agreed-upon profit.
This type of contract is high risk for the customer, since contractor costs can overrun the proposed price.
In cost-reimbursement contracts, the customer usually requires that, throughout the project, the contractor regularly compare actual expenditures with the proposed budget and reforecast cost-at-completion.
This type of contract is low risk for the contractor because all costs will be reimbursed by the customer. The contractor cannot lose money on this type of contract.
Cost-reimbursement contracts are most appropriate for projects that involve a higher degree of risk.