MPM340
RUNNINGHEADER:COFFEESHOPPROJECT 1
Quintessential’s Coffee Shop 28
MPM344-1501A-01
Project Risk Management
Quintessential’s Coffee Shop
Quesadra D. Goodrum
Instructor: Stephen Volz
1/12/2014
Table of Contents Section 1 2 Project Outline 2 Project Objectives 5 Project Deliverables 5 Project Milestones 5 Risk Management Justification 7 Letter to Project sponsor 7 Steps in developing our Risk Management Plan 8 Risk Identification/Risk Registrar 8 Risk Analyst- 8 Identify the triggers to identified risk 8 Risk resolution idea- 8 Risk resolution action plan- 8 Responsibility and accountability- 9 Flow Diagram 9 Projective Technical Requirements 9 Project limits and Exclusions 10 Section 2 11 Project Risks Identification 11 Identified Risk 11 Stakeholder Analysis 13 Risk Scoring Matrix 14 Risk Action 16 Risk Breakdown Structure 18 Probability Impact Graphs 18 Graph 3 -RBS Categorization 19 Section 3 22 TBD-PHASE3 Project Risks Responses Strategy 22 Section 4 23 TBD-Phase4 Project Risks Responsibility Plan 23 Section 5 24 TBD-Phase5 Project Risks WBS & Budget Updates 24 Final Audit 25 Post Project Review- Customer Review 25 References 27
Project Outline
In my initiation paper I introduce the word to Quintessential’s coffee shop. The essence of coffee with the world of technology; it will having both a social and meeting/study environment. This setting will allow residents and other customers to have the option of a quiet area for studying or to conduct a meeting or a social gathering. The project has several main benefits, which includes improving resident’s way of life while within the community, money savings, relaxed environment, and job opportunity. This coffee shop will promote a team cohesive environment, preparing for the training of future employees on the same team attributes promoting success while maintaining a cozy environment.
This functional organization project once complete will give the students and faculty in and around the Colorado Technical University Colorado Springs, CO Campus access to the world of coffee. The project will combine the essence of coffee with technology world; it will have both a social and meeting/study environment. This setting will allow students and other customers to have the option of a quite area for studying or to conduct a meeting or a social meeting. The project has several benefits, which includes improving students and faculties’ way of life while on campus, money savings, relaxed environment, and job opportunity. This coffee shop project will promote a team cohesive environment in order to in the future, training employees on the same team attributes to build success and maintain a cozy environment.
The tasks involved with construction are as follows:
· Risk Assessment
· Site evaluation
· Building Permits
· Contracting
· Plumbing
· Foundation
· Foundational check/inspection
· Framing
· Insulation
· Electrical/wiring
· Telephone wiring
· Installing Windows
· Code Inspection
· Installing siding exterior
· Installing drywall
· Completion of refrigeration unit
· Completion of Storage unit
· Build bathrooms
· Surface Parking lot
· Landscaping
· Install deliverables
· Building and coding inspection
· Final inspection
· Turn over for decoration
· Completion
Float and Slack are as follows:
· Site Evaluation and Risk Assessment can be ran concurrently
· Refrigeration and storage
· Storage can start at max 4 days later than refrigeration since the two will be ran in parallel to one another
· Phone fax and internet centers
· To compress the scheduled this will be built in parallel to one another
By compressing the scheduled and allowing time for float and slack it enables me to finish the project ahead of time and under projected budget. I made sure to not to allow too much slack for one task as to allow for a faster completion by not consuming all of the float and slack time I had available in the project.
Project Objectives
To construct an environment friendly, with up-to-date-technology coffee lounge close to Colorado Technical University Colorado Springs Campus, Co within 1 1/2 month at a cost not to exceed $250,000. 00.
Project Deliverables
· A 1,000 square-feet to include Counters, cooling cases, drive through window inserted-separate counter area, storage room, 2-bathroom finished building
· Central air and heat with thermostat
· Middle of room display shelves
· Phone and fax center capabilities
· Multi-user Internet capabilities
· Separate lounge area
· refrigeration
· Enclosed 30 spot parking lot
· Two doors
Project Milestones
· Building permits approval- September 26,2011
· Foundation checks –September 29, 2011
· Install deliverables – September 29, 2011
· Building and coding inspection- October 17, 2011
· Final inspection- October 31, 2011
· Turn over for decoration- November 1, 2011
Risk Management Justification
Letter to Project sponsor
Dear CTU Student Union President,
All successful projects include a detailed risk management plan and ensuring a smooth flow this coffee shops plan must include one. The inclusion of a risk management plan is essential in ensuring we stay on task with little to no obstacles and resistance. It will also ensure that we stay reasonably inside the projected budget for the project. So it is very important to develop and implement one at the initiation phase to every project you undertake. The risk management plan become critically essential to cut down unexpected risk and delays. The stronger the risk management plan the more problems it will decrease 70 percent 80 percent and even up to cutting down up to 90 percent of the projects risks.
Additional research has yielded information that concludes that a well thought out and designed risk management plan by 90 percent. This is conjunction with other project management methodology conclude that a risk management plan should be an essential element in diminishing the unexpected project risks that can sometimes occur.
Thus risk management planning should always be completed during the early begging stages of the project planning stage. This is primarily due to the fact that it is such a crucial element to the overall success of the project as well as beneficial to accurately and successfully completing other phases of the project management phase. The plan should identify and be a basis for establishing activities’ for the management of possible risks for the project and should be included in the project plan.
An important outcome of the cost and schedule risk analysis is the communication of high risk areas which have a high potential to affect the project cost and/or schedule. For this project, those risks are the building conditions for cost and delaying productivity for the schedule. These two risk items can be mitigated, reducing the risk of an increased project cost.
Sincerely,
Quesadra D. Goodrum PMP
Steps in developing our Risk Management Plan
Risk Identification/Risk Registrar –
Creation of a list of possible risk with the project
Risk Analyst-
Determining the level of potential probability for each risk.
Identify the triggers to identified risk-
Pin pointing causes of determined risk.
Risk resolution idea-
Determine was to resolve each risk.
Risk resolution action plan-
Developing plan to resolve each risk occurrence.
Responsibility and accountability-
Determining who is responsible for each task and or milestone completion
Flow Diagram
Projective Technical Requirements
· Building will meet structural and plumbing code 8582
· Building will meet electrical code 7625
· Fire/safety code 8583
· Accessibility code 2003ANSI A117.1
· Meet current energy code
· 75 ohm RF connection cable wall plate ready- 1
· Ethernet RJ-45 jack-1
· RJ-11 phone outlet jacks- 2
Project limits and Exclusions
· Decoration and framing will be covered by outside contractor.
· Owner responsible for subcontracting work
· Project manager reserves the right to hire outside contractors with owners approval
· Site work hours will be from 9.00a.m to 5.00 p.m., anytime over will be charged overtime
· Initial landscaping will be done under current project management contract, owner will be in charge of all other landscaping
· Updating building permits is owners responsibility
Customer and project manager will review and close out project making sure all deliveries are included and no future work is required.
Section 2
Project Risks Identification
Identified Risk
This is a time-constraint project and may require additional resources to be completed on time.
*1. Denial or delay in digging approval- This risk can alter the start date of the project.
*2. Coding failure-, this can change the start date of the project
*3. Infrastructure Damage- this will cause extra days of work and Project extension during the beginning.
*4. Equipment malfunction- resource that is assigned to the project has malfunctioned or broke at any time during the project
*5. Loss of resource- Resource assigned to the project has emergency and has to leave project at any time during the project
*6. Circumstances beyond the norm- things such as bad weather anytime during the project.
*7. Market decrease- The need for a business of this sort is no longer needed due to the fact the school has opened up a similar establishment on-campus, this can happen anytime during the project.
*8. Service network area has been changed- the service provider that was chosen as the internet provider no longer offers service in the local area at an affordable cost.
*9. Product quality failure- This can happen after installation of equipment and test. Which if fails adds extra days to the project when there are no resources available.
*10. Coding was not approved again-
|
Risk event |
Response: Accept, Reduce, Share, Transfer |
Contingency plan |
Trigger |
Who is Responsible |
|
Coding Failure |
Accept |
Fix coding Issue and get re-inspection done same day. |
Prior use building |
Quesadra |
|
Infrastructure Damage |
Reduce |
Hire additional resource to complete by Late finish date-parallel task. |
Used building, |
contractors |
|
Equipment Malfunction |
Accept |
Rent equipment from other local companies. |
Using older equipment due to cost |
Quesadra |
|
Loss of Resource |
Transfer, Accept |
Workers from other task that are complete or/and hire additional resource part-time.. |
Over exhaustion or family issue |
Quesadra |
|
Coding |
Accept |
Fix coding issues and re-inspect ASAP. |
Change in resource at the last minute |
contractors |
Project Risks Assessment
Stakeholder Analysis
|
Stakeholder |
Area of Interest |
Attitude (+/-) |
Power (+/-) |
Interest (+/-) |
Stakeholder Type |
|
Project Manager |
Project |
+ |
+ |
+ |
savior |
|
Project Scheduler |
project |
+ |
- |
- |
acquaintance |
|
Accountant |
budget |
- |
+ |
- |
Time bomb |
|
Administrator |
admin |
- |
- |
- |
tripwire |
|
Designer |
design |
+ |
- |
+ |
friend |
|
Contractor |
project |
|
|
|
irritant |
|
Sponsor |
project |
- |
+ |
+ |
saboteur |
|
Client |
project |
+ |
+ |
- |
Sleeping giant |
The overall status of the risk is active; this risk has a high probability of occurrence one or more of the project objectives negatively.
Risk Scoring Matrix
|
1. RISK SCORING MATRIX Defined Conditions for Risk Management Analysis |
|||||
|
Project Objective |
Relative or Numerical Scales |
||||
|
|
|
||||
|
|
Very Low - 1 |
Low - 2 |
Moderate - 3 |
High - 4 |
Very High - 5 |
|
Cost |
|
|
|
x |
|
|
Time |
|
|
|
|
x |
|
Scope |
|
|
x |
|
|
|
Quality |
|
|
|
x |
|
|
Risk |
Probability |
Cost |
Schedule |
Scope |
Quality |
Risk Score |
|
Coding Failure |
90% |
4 |
5 |
3 |
3 |
13.5 |
|
Infrastructure Damage |
60% |
2 |
5 |
5 |
4 |
9.6 |
|
Equipment Malfunction |
40% |
4 |
5 |
3 |
3 |
5.2 |
|
Loss of Resource |
40% |
3 |
4 |
3 |
2 |
4.8 |
|
Coding |
10% |
5 |
5 |
3 |
4 |
1.7 |
Cost risk is a high risk because this is a time-constraint project any delay will have to be corrected by an increase in resource to meet deadline.
Time- is the highest because all tasks have to be completed in the required time frame, which may cause overworking the workers and they may become exhausted and de-motivated.
Scope- is moderate because if the client thinks or see additional changes during the project, changing the scope will interfere with the completion date and also increase cost.
Quality- is a 4 because if the scope changes and time is adjusted and additional resources have to added, the client may have to compromise on the quality of some resources, which may not be a good decision.
Risk Action
|
Risk event |
Response: Accept, Reduce, Share, Transfer |
Contingency plan |
Trigger |
Who is Responsible |
|
Coding Failure |
Accept |
Fix coding Issue and get re-inspection done same day. |
Prior use building |
Quesadra |
|
Infrastructure Damage |
Reduce |
Hire additional resource to complete by Late finish date-parallel task. |
Used building, |
contractors |
|
Equipment Malfunction |
Accept |
Rent equipment from other local companies. |
Using older equipment due to cost |
Quesadra |
|
Loss of Resource |
Transfer, Accept |
Workers from other task that are complete or/and hire additional resource part-time.. |
Over exhaustion or family issue |
Quesadra |
|
Coding |
Accept |
Fix coding issues and re-inspect ASAP. |
Change in resource at the last minute |
contractors |
To mitigate the risk of the market conditions can be assessed during the engineering, of the project to determine the best contract acquisition date in relation to similar scoped projects. This will enable the PDT to reduce the risks associated with the market conditions. To reduce the risk of delaying productivity, detailed productivity studies of similar delays could be completed. After these studies are complete, the cost engineer will be able to more accurately calculate the delay production rate.
|
RBS Level 0 |
RBS Level 1 |
RBS Level 2 |
|
|
Technical Risk |
1.1 Scope Definition 1.2 Technical interface 1.3 Design 1.4Performance 1.5 Test and Acceptance |
|
|
Management Risk |
2.1 Project Management 2.2 communication 2.3 information 2.4 Quality |
|
Project Risk |
Commercial Risk |
3.1 Contractural terms 3.2 Supplers and Vendors 3.3subcontractors 3.4 Client stability 3.5 Joint Ventures |
|
|
External RisK |
4.1 Legislation 4.2 Environmental/ weather 4.3 Regulatory 4.4 political 4.5 Competition |
|
|
|
|
Risk Breakdown Structure
|
|
|
|
|
Probability- Impact Matrix Graph 1 |
|
|
|
|
|
|||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Negative |
|
|
|
|
|
Positive |
|
|
|
|
|
|
|
Impact |
|
|
|
|
|
Impact |
|
|
|
|
P |
VHI |
|
2 .09 |
|
|
|
|
|
2 .44 |
|
VHI |
P |
|
R |
0.90 |
|
|
|
|
|
|
|
|
|
0.90 |
R |
|
O |
HI |
|
|
|
|
|
|
|
|
|
HI |
O |
|
B |
0.70 |
|
|
|
|
|
|
|
|
|
0.70 |
B |
|
A |
MED |
|
|
T |
|
|
|
O |
1 .10 |
|
MED |
A |
|
B |
0.50 |
|
|
|
|
|
|
|
2 .26 |
|
0.50 |
B |
|
I |
LO |
2 .04 |
|
1 .10 |
|
|
|
|
|
2 .10 |
LO |
I |
|
L |
0.30 |
|
1 .10 |
|
1 .12 |
|
|
|
|
|
0.30 |
L |
|
I |
VLO |
1 .08 |
|
|
|
|
|
|
|
|
VLO |
I |
|
T |
0.10 |
VLO |
LO |
MED |
HI |
VHI |
VHI |
HI |
MED |
LO |
0.10 |
T |
|
Y |
|
0.05 |
0.10 |
0.20 |
0.40 |
0.80 |
0.80 |
0.40 |
0.20 |
0.10 |
|
Y |
|
|
|
|
Green |
|
|
Amber |
|
|
Red |
|
|
|
|
|
|
|
Risks |
|
|
Risks |
|
|
Risks |
|
|
|
Probability Impact Graphs
|
|
|
probability-Impact Scoring- Graph 2 |
|
|
|
|||
|
|
|
|
|
|
|
|||
|
|
|
|
|
|
|
|
|
|
|
|
Rank |
Probability |
Impact |
|
||||
|
|
VHI |
0.9 |
0.8 |
|
||||
|
|
HI |
0.7 |
0.4 |
|
||||
|
|
MED |
0.5 |
0.2 |
|
||||
|
|
LO |
0.3 |
0.1 |
|
||||
|
|
VLO |
0.1 |
0.05 |
|
The risk
|
|
|
|
|
Graph 3 -RBS Categorization |
|||
|
|
|
|
|
|
|||
|
|
|
|
|
|
|
|
|
|
Level 0 |
Level 1 |
Level 2 |
# Risk |
|
|
|
|
|
Project Risk 3.02 |
Technical Risk 2.00 |
1.1 Scope Definition |
0.55 |
|
|
|
|
|
|
|
1.2 Technical interface |
0.48 |
|
|
|
|
|
|
|
1.3 Design |
0.15 |
|
|
|
|
|
|
|
1.4Performance |
0.2 |
|
|
|
|
|
|
|
1.5 Test and Acceptance |
0.62 |
|
|
|
|
|
|
Management Risk 0.56 |
2.1 Project Management |
0.46 |
|
|
|
|
|
|
|
2.2 communication |
0.08 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Commercial Risk 0.46 |
3.1 Contractural terms |
0.2 |
|
|
|
|
|
|
|
3.2 Supplers and Vendors |
0.2 |
|
|
|
|
|
|
|
3.3subcontractors |
0.06 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Risk Activity |
Responsibility |
|
Risk registry |
Project manager |
|
Risk Assessment |
All the stakeholders of the project |
|
Risk response options identification |
All the stakeholders of the project |
|
Risk Response Approval |
Project manager with consultation with project coordinator |
|
Risk contingency Planning |
Project manager |
|
Risk response management |
Project manager |
|
Risk reporting |
Project manager |
|
|
|
Responsibility ensures that each risk is assigned to an individual. The move ensures identification of the risks hence applicable mechanism to counter its effect is instituted.
|
What |
Owner |
Time estimate |
|
Monitoring: the risk owners (supppliers, vendors) are supposed to monitor the risks in their sectors and relay the information to the project manager through email when a risk trigger occurs and the response plan is instituted |
Risk oners |
3 hours |
|
New risk Identification: stakeholders can detect the presence of additional risks. In such a case, the manager should be notified through email about the probable risk |
Stakeholders |
1.5 hours |
|
Audit processes: The project manager will oversee the risk activities and ensure an update is done on the risk register |
Project manager |
3hours per month |
|
Review: The project manager with availability of expatriate advice will review the risks every week |
Project manager with expatriate advice |
2 hours per month |
|
Reporting: Two methods will be applied: first, the project manager keeps the risk log in the depository. It will have contents of active risks, priority ones, current status and assignment Secondly, quarterly reports will encompass a risk log summary and any new risks. |
Project manager |
2 hours per month |
Risk monitoring and control is relevant as it assists in identifying the possible risks. It further ensures that effective mechanisms are developed that will ensure that the project risks are mitigated. As a result, the business/project will not be sank by the presence of the risks in its daily operations.
Section 3
TBD-PHASE3 Project Risks Responses Strategy
a. Create a table similar to the sample above, or use another method to list the risk, the likelihood of occurrence, and the overall severity of impact if it occurs.
b. Fill in the table with the information from the project identification utilizing the 2 scales that you determined as a part of your Discussion Board assignment. Be sure to consider both the cost and schedule impact as you determine the overall impact.
c. Rank your risks based on both the likelihood and impact using a technique, such as 2x2 matrix as shown in the assignment description section.
Section 4
TBD-Phase4 Project Risks Responsibility Plan
d. Include a responsibility matrix listing the stakeholders and project team members, with risk actions (or category of actions) along the top.
e. Next, fill in the table using the following letters, and refer to the examples in the Assignments section as "R" if they are responsible for monitoring and controlling the risk, "A" if they are the approver for taking action to respond to the risk, "S" if they have a support role in responding to the risk, and "I" if they only need to be informed. This is also known as a RASI chart.
Project Risks Monitoring & Control Plan
f. Include a detailed description of the overall monitoring process, including the techniques that will be used to monitor the existence and impact of individual risks.
g. Include a detailed description of the control process when a risk occurs.
h. Include a diagram flowchart to depict the steps in the control process from risk discovery through risk response.
Section 5
TBD-Phase5 Project Risks WBS & Budget Updates
Project Risks Communications Plan
|
Type of information |
participants |
Purpose of communication |
frequency |
Transmittal period |
|
Project plan |
Project team |
To define the background, responsibilities , risks, schedule, staffing and communication |
At the start- up of the project |
|
|
Project schedule |
Sponsor, project manager, customers |
To document as well as monitor the key tasks in the project and the present resources |
As neede |
|
|
Kick off meeting |
Project team |
To clarify the goals and objectives of the coffee shop, the roles by the staff and the interdependences within the operations |
Only once at the project start up |
meeting |
|
Weekly status meeting |
Project manager and staff |
Discuss status of the project, the issues that may have arose concerning the project |
Once in a week |
Oral discussions among the present |
|
Project sponsor |
Project sponsor and manager |
Communicate issues, resource concerns, milestones among other things |
monthly |
meeting |
The project communication will assist in the coordination within the project. Relaying of information among the different participants involved will assist in exchange of ideas that will assist in the moving forward of the project.
Final Audit
The final audit will be conducted by the review committee, along with an outside project consultant. Once the audit is complete, the audit team will take its findings and recommendations to the Client for project success evaluation. The audit will look at all areas of qualitative and quantitative performance measures, as well as analyzing team interaction and motivation levels. The audit team will also provide a lessons learned report in the final audit packet. The auditors will review the project manager in all areas of cost and schedule performances, and the level of cohesiveness maintained by the project team. The communication plan will also be reviewed to determine if the content was practical, informational, and/or significant to its target audience.
Post Project Review- Customer Review
After all audits have been finalized the conclusions presented, a review will be conducted by Executive committee that will determine if the project has been successfully completed. Along with the findings presented by the team leaders, the client will measure the quality of the delivered product by conducting visitor surveys during the two weeks of soft opening. They will look at reaction to the design of the building, the interior design, and exhibit content. This Executive Committee will also make a judgment on the quality of the management of this project by comparing the project specifications outlined in the scope statement to the end product to determine if it meets customer project expectations.
References Editorial Board. (2012). Introduction to Project Management . Words Of Wisdon LLC. PMI. (2004). Practice Standard for Project Risk Management. Newton Square,PA: PMI. PMI. (2013). A Guide to the Project Management Body of Knowledge . Newton Square,PA: PMI.
Risk Identification & Risk Register
Risk Method Analyst
Identify Risk Triggers
Risk Resolution Idea
Risk Resolution Action Plan
Responsibility & Accountibility