Documentos de Académico
Documentos de Profesional
Documentos de Cultura
Project management is about creating an environment conducive to getting critical projects done!
Mrs. Shubhashri Waghmare
Project Charter
What must be done?
o o o
What are the required resources? What are the constraints? What are the short and long term implications?
Why do it? When must it be done? Where must it be done? Who does what?
o o o
Who is behind the project? Who is funding the project? Who is performing the work of the project?
Project Charter
Who What Where Why When
Project Charter
Project Goal & Objective Sponsor Stakeholders Timeline Resources required Deliverables Decision making Assumptions Risks Business process changes Project manager Project team Budget Signatures
Organizational Structure
Organization Structure
Created on the basis of arrangement of activities in the organization Three types of structural forms in the organization 1. Functional Structure 2. Divisional Structure 3. Adaptive Structure
Functional Structure
Organizational structure that is based on the functions of the units and sub-units of activities. Every organization has specialized functions and they constitute as separate units of the organization. The entire activities that are connected with such functions are placed in the same unit. The increase in volume of activity results in addition of number of persons under each manager at various levels. It also results in the increase of sub-units that are created at lower levels in each unit. functional specialization in each unit. It leads to operational efficiency of the persons engaged in the organization. gets the benefit of specialized operations.
Divisional Structure
suited for large enterprise. It works effectively to those large enterprises that deal in multiple products serving many distinct markets. The division of organization takes place into small business units that are entrusted with business related to difficult products or different market territories. All the divisional managers are given authority and autonomy to run all function relating to their respective products or marketing segments or regional markets. Each division contributes planned profits to the organization but works as independent business. Managers head the functional units while divisional managers take the final authority. Divisional managers are provided with opportunities to take initiative in matters that are within their jurisdiction. Its demerits are that it involves heavy financial costs due to the duplication of supporting functional u nits for the divisions.
Adaptive Structure
Designed as to cope with the unique nature of undertaking and the situations in the organization. There are two types of adaptive structure : a) Project organization b) Matrix organization
Project Organization
Suitable when an organization undertakes specialized work for a particular period as one time operation. To deal with such situations organizations develops a unit which is specially designed to accomplish such project works without disturbing the routine jobs of the organization. The organizations engage their existing employees on deputation basis to deal with a particular project and then that particular executive resumes to his parent department after the completion of the project. The advantage of such organizations is that it does not disturb the regular work of the organization. It enables the better control over the project activities because the managers enjoy the authority to function the projects effectively. But at times these organizations spoil the stability of the various departments as the personnel are shifted for the sake of the project and thus disrupt the basic functioning of the parent department.
Mrs. Shubhashri Waghmare
Matrix organization
Aims to combine the advantages of autonomous project organization and functional specialization. Structure functional departments are having full time specialized workers to accommodate and are capable of handling more than one project at a time. This is found suitable as the organization is most of the time engaged in the project activities and the managers are also more in number and can accomplish the project work effectively. It provides for the flexible system of working as it adapts the changes quickly. The demerit of such organizations is that the employees are engaged in dual jobs and are burdened with more work which affects the unity of command at times in the organization.
Project Planning
WBS.
This is a technique to analyse the content of work and cost by breaking it down into its component parts. It is produced by : Identifying the key elements Breaking each element down into component parts Continuing to breakdown until manageable work packages have been identified. These can then be allocated to the appropriate person.
work breakdown structure for the recruitment of a new person to fill a vacant post.
Project Crashing
The process of accelerating a project is referred as crashing. Crashing a project relates to resource commitment; the more resources expended, the faster the project will finish. There are several reasons to crash a project:
1.Initial schedule was too optimistic 2.Market needs change and the project is in demand earlier than anticipated 3.The project has slipped considerably behind schedule 4.There are contractual late penalties
Project Crashing
Principal methods for crashing o Improving existing resources productivity o Changing work methods o Increasing the quantity of resources Increasing the quantity of resources is the most commonly used method for project crashing. There are 2 approaches: o Working current resources for longer hours (overtime, weekend work) o Adding more personnel
Project Crashing
Fully expedited (no expense is spared)
Project Crashing
In analyzing crash options, the goal is to find the point at which time and cost trade-offs are optimized. Various combinations of time-cost trade-offs for crash options can be determined by using the following formula:
Example
SUPPOSE: NORMAL ACTIVITY DURATION = 8 WEEKS NORMAL COST = Rs.14,000 CRASHED ACTIVITY DURATION = 5 WEEKS CRASHED COST = Rs.23,000 THE ACTIVITY COST SLOPE = 23,000 14,000 OR Rs.9,000 = Rs.3,000 per week 853 Cease crashing when the target completion time is reached the crash cost exceeds the penalty cost
Example
Normal Crashed Activity Duration Cost Duration Cost A 4 days Rs.1,000 3 days Rs.2,000 B 5 days Rs.2,500 3 days Rs.5,000 C 3 days Rs.750 2 days Rs.1,200 D 7 days Rs.3,500 5 days Rs.5,000 E 2 days Rs.500 1 day Rs.2,000 F 5 days Rs.2,000 4 days Rs.3,000 G 9 days Rs.4,500 7 days Rs.6,300
a) Calculate the per day costs for crashing each activity b) Which are the most attractive candidates for crashing? Why?
Example
Activity Per Day Cost A Rs.1,000 B Rs.1,250 C Rs.450 D Rs.750 E Rs.1,500 F Rs.1,000 G Rs.900
1.I can shorten this project by 1 day at a cost of Rs.400. Should I do it?
1.Time Limited: The project must be finished by a certain time, using as few resources as possible. But it is time, not resource usage, that is critical
1.Resource Limited: The project must be finished as soon as possible, but without exceeding some specific level of resource usage or some general resource constraint
Resource Loading
Resource loading describes the amounts of individual resources an existing schedule requires during specific time periods The loads (requirements) of each resource type are listed as a function of time period Resource loading gives a general understanding of the demands a project or set of projects will make on a firms resources
Resource Loading
The project manager must be aware of usage flow for each input resource throughout the life of the project. It is the project managers responsibility to ensure that the required resources, in the required amounts, are available when and where they are needed.
0A4 Res = 6
11 F 12 Res = 6
A B C D E F
6 2 2 7 3 6
4 1 3 4 2 1
0 4 4 5 9 11
0 0 4 0 0 0
4 5 11 9 11 12
1. Produce a table that shows the duration, early start, late finish, slack, and resource(s) required for each activity.
Mrs. Shubhashri Waghmare
6 Resources 4
A 2 C 2 4 B
D E 6 8 10 12 Project Days
Mrs. Shubhashri Waghmare
Resource imbalance
14
6 Resources 4
A 2 C 2 4 B
C F E
6 8 10 12 Project Days
Mrs. Shubhashri Waghmare
14
Resource Planning
The nature of the project and the organization will affect resource planning
How difficult will it be to do specific tasks on the project? Is there anything unique in this projects scope statement that will affect resources? o What is the organizations history in doing similar tasks? o Does the organization have or can they acquire the people, equipment, and materials that are capable and available for performing the work?
o o
Cost Estimating
An important output of project cost management is a cost estimate There are several types of cost estimates and tools and techniques to help create them It is also important to develop a cost management plan that describes how cost variances will be managed on the project
Estimating Projects
Estimating
The process of forecasting or approximating the time and cost of completing project deliverables o The task of balancing the expectations of stakeholders and the need for control while the project is implemented
o
Types of Estimates
Top-down (macro) estimates: analogy, group consensus, or mathematical relationships o Bottom-up (micro) estimates: estimates of elements of the work breakdown structure
o
Organization Culture
Quality of Estimates
People
Padding Estimates
TYPES OF ESTIMATES
1. Preliminary 2. Unit price 3. Assembly or Conceptual Cost
4. Detailed estimate
2 Million dollars building
Accuracy within 20% 15% 10% 5% Preliminary Unit Price Assembly Detailed Time 5min 1hour 1day 3 weeks
Each phase of a project life cycle requires a different type of estimate--each estimate requires different types
Preliminary Estimate .
Advantageous
o o
Allows a quick determination of the feasibility of a project A quick screening on alternatives, etc. (e.g., should it be a concrete building or a steel building !).
1. Ranking alternatives 2. Evaluate economics and financial feasibility 3. As a check on more detailed estimates
Purpose:
Cost Management
states that when many items are produced (or tasks are performed) repetitively, the unit cost of those items decreases in a regular pattern as more units are produced (or more tasks performed)
Reserves
Cost Estimating
After developing a good resource requirements list, PMs and their teams must develop several estimates of the costs for these resources Project managers must take cost estimates seriously if they want to complete projects within budget constraints Its important to know the types of cost estimates, how to prepare cost estimates, and typical problems associated with IT cost estimates
Mrs. Shubhashri Waghmare
It is important to provide supporting details (assumptions, project scope, WBS, etc) used in computing estimates so that it will be easier to prepare updates as needed or similar estimates on other Mrs. Shubhashri Waghmare projects.
Cost Estimating
Rough Order of Magnitude (ROM) estimate provides an estimate of what a project will cost. Also referred to as a ballpark estimate, a guesstimate, a swag, or a broad gauge. Done very early in a project, often three or more years prior to project completion, or even before a project is officially started to help PMs make project selection decisions. Accuracy is typically -50 percent to +100 percent, meaning the projects actual costs could be 50 percent below the ROM estimate or 100 percent above.
o
A ROM estimate that actually cost Rs.100,000 would range between Rs. 50,000 to Rs.200,000. The accuracy range is often much wider for IT projects.
Cost Estimating
A budgetary estimate is used to allocate money into an organizations budget. o Many organizations develop budgets at least two years into the future. Budgetary estimates are made one to two years prior to project completion. o The accuracy of budgetary estimates is typically -10% to +25% A budgetary estimate that actually costs Rs.100,000 would range between Rs.90,000 to Rs.125,000.
Cost Estimating
A definitive estimate provides an accurate estimate of project costs (most accurate of the three types). Definitive estimates are used for making many purchasing decisions for which accurate estimates are required and for estimating final project costs. E.g, if a project involves purchasing 1000 personal computers from an outside supplier in the next three months, a definitive estimate would be required to aid in evaluating supplier proposals and allocating the funds to pay the chosen supplier. Definitive estimates are made one year or less prior to project completion Accuracy range is normally -5% to +10%
How similar the current and previous project are determines the accuracy of the estimate. Using a different language or hardware can skew the estimate
Bottom-up estimates or Activity Based Costing : involve estimating individual work items or activities and summing them to get a project total
o
The smaller the work items, the better the estimate but these estimates are usually time intensive and expensive to develop
For example, a model might provide an estimate of Rs.50 per line of code for a s/w development project based on the programming language, level of expertise of the programmers, size and complexity of the data involved, etc Some models may be simpler such as a Rs.10,000 ballpark estimate per workstation in a large office automation project based on history of similar projects during the same time period
Cost Budgeting
Cost budgeting involves allocating the project cost estimate to individual work items over time The WBS is a required input to the cost budgeting process since it defines the work items An important goal is to produce a cost baseline o A time-phased budget that project managers use to measure and monitor cost performance o Estimating costs for each major project activity over time provides management with a foundation for project cost control o Cost budgeting also provides info for project funding requirements at what point(s) in time will the money be needed
Cost Control
Project cost control includes: o Monitoring cost performance o Ensuring that only appropriate project changes are included in a revised cost baseline o Informing project stakeholders of authorized changes to the project that will affect costs Many organizations around the globe have problems with cost control
Cost Control
Performance review meetings can be a powerful tool to help control project costs o Knowing you have to report on your progress is an incentive for people to perform better Performance measurement is another important tool for cost control o There are many general accounting approaches for measuring cost performance but earned value management is a tool unique to project management
Was a WBS item completed or approximately how much of the work was completed Actual start and end dates Actual cost
More and more organizations around the world are using EVM to help control project costs
Rate of Performance
Rate of performance (RP) is the ratio of actual work completed to the percentage of work planned to have been completed at any given time during the life of the project or activity Brenda Taylor, Senior Project Manager in South Africa, suggests this term and approach for estimating earned value
o
For example, suppose the server installation was halfway completed by the end of week 1; the rate of performance would be 50% because by the end of week 1, the planned schedule reflects that the task should be 100% complete and only 50% of that work has been completed The EV would thus be Rs.5,000 after week 1 (Rs.10,000*50%)
Mrs. Shubhashri Waghmare
- VE numbers for cost and schedule variance indicate problems in those areas. If CV is negative - it means that performing the work cost more than planned If SV is negative - it means that it took longer than planned to perform the work CPI can be used to estimate the projected cost of completing the project based on performance to date (EAC) =1:the planned and actual costs are the same; < 1: over budget ; >1: under budget SPI can be used to estimate the projected time to complete the project =1: on schedule; < 1 behind schedule; > 1 ahead of schedule
Mrs. Shubhashri Waghmare
Risk Management
Mrs. Shubhashri Waghmare
Risk DEFINITION
Possibility of meeting danger or suffering harm. OXFORD dictionary Risk can be defined as a measure of the probability and consequence of not achieving a defined project goal.
PMBOK
Risk is the probability of an adverse outcome. (Graham and Weiner, 1995). Risk equals to the expected loss in a project. (Willis, 2007). Risk is the measure of probability & severity of adverse effects.
(Lowrance 1976).
Risk is defined as a set of scenarios, each of which has a probability and a consequence.
(Kaplan and Garrick 1981, Kaplan 1991).
Risk refers to situations with known probabilities for the randomness the decisionmaker is faced with.
(Knight 1921, Douglas 1983).
Mrs. Shubhashri Waghmare
WHAT is Risk?
Risk
Uncertain event that has a positive or negative effect. On at least one of the project objectives (scope, schedule, budget, quality).
Risk Management
The practice of dealing with project risk. It includes PLANNING for risk, ASSESSING risk, Developing risk response STRATEGIES, MONITORING risk throughout the project life cycle.
Simple Terminology: Risk Management is the identification of an unborn issue (a risk) that will have a negative impact on the project that must be eliminated with proactive planning, monitoring, and activities or tasks.
Risk Assessment
Risk Analysis
Risk Prioritization
Risk Management
Risk Mgmt Planning
Risk Control
Organizational Risk Management Policy: Predefined approaches to risk analysis and resolution that needs tailoring to a particular project. Defined roles and responsibilities: Predefined roles, responsibilities, and authority levels for decision making will influence planning. Stakeholder Risk Tolerance: Different organizations and different individuals have different tolerances for risk. Policies or historical actions may communicate this. Planning Meetings: Project teams hold risk management planning meetings to develop the plan.
Risk Identification
The process of determining which risks might affect the project and document the characteristics.
** Risk identification is an iterative process **
Inputs
1. 2. 3. 4. Risk management plan Project planning outputs Risk categories Historical information
Output
1. 2. 3. Risks Triggers Inputs to other processes
INPUTS Risk Management Plan: See previous slide Project Planning Outputs: Items to be reviewed, but not limited to: project charter, WBS, product description, schedule and cost estimates, resource plan, procurement plan, assumption and constraints. Risk Categories: Risks that may affect a project for better or worse can be identified and organized into risk categories. Categories include: o Technical, quality, and performance risks o Project Management risks o Organizational Risks cost, time, and scope o External risks shifting legal or regulatory environment, labor issues, natural events. Historical Information: Information on prior projects may be available to help leverage lessons learned.
Risk Analysis
Quantitative: The process of measuring the probability and consequences of risks and estimating their implications for project objectives.
Determine the probability of achieving a specific project objective. o Quantify the risk exposure for the project, and determine the cost and schedule contingency reserves that may be needed. o Identify risks requiring the most attention by quantifying their relative contribution to project risks. o Identify realistic and achievable cost, schedule, and scope targets.
o
Qualitative: The process of performing a qualitative analysis of risks and conditions to prioritize their effects on project objectives.
Mrs. Shubhashri Waghmare
Scope Scope Reduction Minor areas of Major Areas Scope Reduction Project end item
scope affected of scope affected unacceptable to is not meeting client business need
Quality Quality Only very Quality Reduction Quality Reduction Project end item
Degradation small demanding Apps requires client unacceptable to is useless affected approval client
Risk Resolution
DEFINITION: The process of developing procedures and techniques to reduce threats to the project objectives.
Inputs 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. Risk Management Plan List of prioritized risks Risk ranking of the project Prioritized list of quantified risks Probabilistic analysis of the project Probability of achieving the cost and time objectives List of potential resolutions Risk thresholds Risk owners Common risk causes Trends in qualitative and quantitative risk analysis results Output 1. 2. 3. 4. 5. 6. 7. Risk resolution plan Residual risks Secondary risks Contractual agreements Contingency reserve amounts needed Inputs to other processes Inputs to a revised project plan Tools & Techniques 1. 2. 3. 4. Avoidance Transference Mitigation Acceptance
Avoidance: Risk avoidance is changing the project plan to eliminate the risk or condition or to protect the project objectives from its impact. Transference: Risk transference is seeking to shift the consequences of a risk to a third party together with ownership of the resolution. (Financial risk is most common) Mitigation: Mitigation seeks to reduce the probability and or consequences of an adverse risk event to an acceptable threshold. Acceptance: This technique indicates that a project team has decided not to change the project plan to deal with a risk. Developing a contingency plan is a way to managing known risks. The contingency plan adopt contingency allowance or reserve that includes:
o o o
Inputs 1. 2. 3. 4. 5. Risk Management Plan Risk resolution plan Project communication Additional risk identification and analysis Scope Changes
Output 1. 2. 3. 4. 5. 6. Workaround plans Corrective action Project change request Updates to the task resolution plan Risk database Updates to risk identification checklist
Tools & Techniques 1. 2. 3. 4. Project Risk resolution audits Periodic project risk reviews Earned Value analysis Technical performance measurements Additional risk resolution planning
5.
Project Schedule > Risk Items get put into project WBS (as contingency) and Assigned Ownership
Project Size
Resource Hours Total estimated resource hours: <=5,000 > 5,000 and <=20,000 > 20,000 <= 4 months > 4 months and <=12 months > 12 months <= 4 participants > 4 and <= 12 participants > 12 participants Low Medium High Low Medium High Low Medium High
Notes
Notes
Team Size Maximum team size at any time during the project:
Notes
well defined and accepted named but not detailed not identified
Notes
well defined and accepted, and/or of strategic importance generally understood, but not quantified ill defined or not identified
Notes
Notes
committed to the project (understands value and is supportive) involved, but not committed skeptical or resistant
Notes
included in or approved for addition included, but not yet approved not yet part of the plan
Notes
Project Dashboard
Project Closure
Please refer the Last phase of Project management Life cycle.