| Course | PM FPX 4060 Risk Management in Project Management |
|---|---|
| Assessment | Assessment 1 |
| Paper type | Risk identification memo |
| Length | About 1,110 words, 5 pages |
| Format | APA 7 student paper |
| School | Capella University |
| Program | BS in Business, Project Management |
| Updated | September 2026 |
Free sample paper for PM FPX 4060 Assessment 1
Identifying Risks on a Veterinary Hospital Relocation: A Named Method, Cause, Event and Effect Kept Separate, Things That Already Happened Removed, Categories Used to Expose Gaps, and Opportunities Logged Alongside Threats
Student Name
Capella University
PM FPX 4060: Risk Management in Project Management
Instructor Name
Month Day, Year
A Named Method, Not a Brainstorm
Three named methods were used, each with its own inputs. Assumptions analysis: each assumption in the charter and scope statement was examined to ask what would happen if it were false. Checklist analysis: the architect's list of common risks on commercial interior renovations was reviewed item by item. Premortem: in a one-hour session, the project manager, owner, lead technician, architect, and contractor's superintendent imagined that the project had opened three months late and 200,000 dollars over budget, and each wrote down reasons why. The Project Management Institute (2017) lists assumption and constraint analysis, checklists, and facilitated sessions among tools for identifying risks. Using three methods reduces the chance that the register reflects only what one person worried about.
Cause, Event, and Effect Kept Separate
Each risk is written in three parts: because of a cause, an event may occur, leading to an effect on objectives. R1: Because the building was built in 1978 and the rear area has not been opened, hidden conditions such as damaged framing or outdated plumbing may be found during demolition, adding cost and delaying construction. R2: Because the city's permit office is short-staffed this year, the final inspection may be scheduled later than requested, delaying the certificate of occupancy and opening. R3: Because the digital X-ray vendor sources detectors from overseas, delivery may be delayed, reducing training time before opening or delaying opening if very late. R4: Because the Elm Street lease extension is verbal only, the landlord may decline to extend, leaving the practice without a location if the move is late. R5: Because one associate veterinarian opposes the move, she may resign before opening, reducing capacity and appointment availability. R6: Because the project manager is the only person with full knowledge of the plan, her absence through illness would stall decisions and coordination. R7: Because the neighboring business owner objected to noise and parking, she may file a complaint during permit review, delaying the permit. R8: Because the move weekend involves moving controlled substances, a count discrepancy may occur, triggering a regulatory report and investigation. R9: Because client communication depends on accurate contact data, some clients may not learn of the move and go to the old address, causing missed appointments and complaints. R10: Because equipment quotes are valid for 60 days, prices may rise if orders are delayed, increasing cost. A risk written as "permits" names a topic. A risk written with cause, event, and effect names something that can be managed.
Things That Already Happened Are Removed
The premortem produced several items that are not risks because they have already happened or are certain. The electrical service upgrade was found during demolition and approved as a change order; it is now an issue being managed, not a risk. The permit being three days late has happened. Higher permit fees than estimated have happened. These were moved to the issue log. Keeping them in the risk register would mix uncertain events with known ones and distort the ranking.
Categories Used to Expose Gaps
Risks were sorted into a risk breakdown structure with four categories to see where identification was thin. Technical: R1, R3. External: R2, R7, R10. Organizational: R4, R5, R6. Project management: R9. Sorting showed that the first draft had no organizational risks at all; the assumptions analysis and premortem had focused on the building and permits. Asking directly about the organization added R5 and R6. The project management category remains thin, so two questions were added: whether estimates were checked by anyone other than the estimator, and whether the schedule has enough float for inspections. These produced R11: because the physicist's shielding survey sits on a near-critical path with one week of float, a scheduling conflict for the physicist could delay the radiology room's certification.
Opportunities Logged Alongside Threats
Opportunities, uncertain events with a positive effect, are logged too. O1: Because the IT vendor has offered to begin cabling in finished rooms during the last weeks of construction, the IT installation could overlap construction, shortening the critical path by up to two weeks. O2: Because the equipment purchases qualify for accelerated tax depreciation, the practice's accountant may be able to reduce the owner's tax this year, lowering the project's effective cost. O3: Because the Elm Street landlord has another tenant interested, he may pay the practice to leave early if the new building is ready, offsetting move costs.
Who Took Part and Why
The premortem included the contractor's superintendent and the architect, not only practice staff, because they see construction risks the practice cannot. It also included the lead technician, who raised the controlled substance risk that no one else had considered. Mixing perspectives produced risks from all four categories once the organizational gap was addressed.
Quality of the Statements
Each statement was checked against three tests: the cause is a fact or condition that exists now; the event is uncertain; and the effect names an objective, such as cost, schedule, or patient care. Two draft statements failed. "Budget overruns" was a possible effect, not a risk, and was replaced by the specific events that could cause overruns. "Staff stress" was a condition, not an event, and was rewritten as R6, the project manager's absence, which is the specific event that stress could produce.
Risks Considered and Not Logged
Some suggestions were considered and not logged because they are too remote to manage, such as a natural disaster damaging the building before opening, which the practice's property insurance already covers. Others were outside the project's scope, such as the second location's financing. Recording that they were considered shows the register's limits are deliberate.
Using the Register
The register lives in the shared project folder and is opened at the start of every site meeting, before schedule review, so that new information from the site is checked against it while people are in the room.
Next Steps
The register will be assessed for probability and impact, owners will be assigned, and responses will be planned. The register will be reviewed at each site meeting.
Conclusion
Assumptions analysis, a renovation checklist, and a premortem identified eleven threats and three opportunities, each written with cause, event, and effect. Items that had already happened were moved to the issue log. Sorting by category exposed missing organizational and project management risks, which were added.
References
Project Management Institute. (2017). A guide to the project management body of knowledge (PMBOK guide) (6th ed.). Project Management Institute.
PM FPX 4060 Assessment 1 instructions, in plain terms
The first assessment in PM FPX 4060 asks you to identify the risks to a project and present them in a memo. You state the project and its objectives, describe the identification method, such as structured interviews, a checklist or a risk breakdown structure, explain who took part, write each risk in a cause, event and effect format, sort the risks by category to reveal gaps, include opportunities as well as threats and explain what will happen next with the list. Anything that has already occurred belongs in the issue log, not the risk list. The PMBOK Guide's section on identifying risks is the main reference.
Inside the PM FPX 4060 Assessment 1 example
The memo is built method first, output second, judgment third. It opens with a compact statement of the project and its objective, because a risk only exists relative to something the project is trying to achieve. The next block describes the identification approach and who was involved, which is what allows a reader to judge whether the coverage is plausible. The output block follows, arranged by category rather than by the order items were thought of, so gaps become visible. Each entry uses the same three-part sentence, and the memo says so once instead of repeating the formula. A short screening block explains what was rejected and why, which is where issues, constraints and effects that arrived disguised as risks get removed in view of the reader. The closing block states which categories carry the heaviest exposure and hands the list forward for scoring.
Reading the PM FPX 4060 Assessment 1 scoring guide
Capella's scoring guide rates the method, the participation, the risk statements, the separation of risks from issues, the use of categories and the inclusion of opportunities. The method reaches Distinguished when named and explained, so a reader can judge how complete the list is likely to be. Participation scores higher when the people involved bring different views, such as the vendor and the clinic's head nurse. Risk statements earn credit when written as cause, event and effect, like "Because the new building's power upgrade is pending, the inspection may fail, delaying the move by two weeks." Issues are judged on whether they are removed. Categories should be used to find missing risks. Opportunities should be logged. Proficient memos list risks; Distinguished ones show how the list was produced and where it might still be thin.
PM FPX 4060 Assessment 1 help: mistakes that cost marks
Risk memos often list vague worries, like "delays" or "budget problems," with no cause or effect, which gives the later assessment nothing to score. Another weakness is including things that have already happened, which are issues needing action, not risks. The method is not explained, so the reader cannot tell whether the list is complete. Only the project manager's view is represented. Categories are listed but not used to find gaps. Opportunities are left out entirely. Writing each risk in the same three-part sentence, then sorting the list by category and asking which categories are empty, produces a stronger register and prepares the ground for scoring in Assessment 2.
Get a PM FPX 4060 Assessment 1 example written to your instructions
Send the Assessment 1 instructions and the scoring guide from your PM FPX 4060 courseroom, along with the project or case scenario your section uses. We write a custom example to those criteria, with a stated method and entries that separate cause from effect, and return it in 24 to 48 hours. The first one costs nothing. The paper above is an original model document written by our desk, not a submitted student paper and not an official Capella University document.
More PM FPX 4060 papers and BS in Business, Project Management samples
- PM FPX 4060 Assessment 2: Risk Register
- PM FPX 4060 Assessment 3: Risk Response Plan
- PM FPX 4070 Assessment 1: Make-or-buy Analysis
- PM FPX 4050 Assessment 1: Stakeholder Analysis
- PM FPX 4080 Assessment 1: Product Backlog
- PM FPX 4040 Assessment 1: Responsibility Assignment Matrix
PM FPX 4060 Assessment 1 questions, answered
What is the difference between a risk and an issue here?
Timing. A risk has not happened and carries a probability; an issue is happening now and carries an owner and a resolution date. The distinction decides where an entry belongs, and mixing the two is the fastest way to lose the identification criterion. If you can put a past tense verb on it, log it as an issue and keep it out of the risk list.
How many risks should the memo identify?
Check your instructions, since some sections set a count. Where the number is open, coverage matters more than volume: entries spread across technical, external, organizational and delivery sources beat twenty variations on staffing. A memo with fifteen well written uncertainties across every category reads stronger than forty that cluster in one place and repeat each other.
Do positive risks belong in a risk memo?
In many sections yes, because current practice treats opportunity as uncertainty with an upside, and the scoring guide often names it. An early vendor delivery or a favorable exchange movement can change the plan as much as a threat. Confirm it in your own instructions, then write opportunities in the same three-part form so they can be scored beside the threats.
Where can I find a free PM FPX 4060 Assessment 1 sample paper?
The whole risk identification memo for the hospital move can be read here, with a named method, cause, event and effect kept separate, past events removed, categories used to find gaps and opportunities logged.
How should a risk statement be written in PM FPX 4060 Assessment 1?
As cause, event and effect: because of a condition, an uncertain event may happen, leading to an effect on an objective. This format makes the risk specific enough to score and respond to.