A finished BU 396 Unit 1 risk management planning document: bands, categories, roles and acceptance thresholds settled in advance, with no risk yet identified. Searches like "bu 396 unit 1 assignment example", "bu396 unit 1 sample" and "bu 396 unit 1 example" land here.
What a finished BU 396 Unit 1 risk management planning looks like
The document reads as an instruction manual for a process that has not started. An opening passage fixes what will count as a risk on this project and what will be handled as an issue instead, since the two get confused the moment work begins. Definition tables follow: probability bands with a stated range against each, and impact bands defined separately for cost, for the schedule and for the quality of what gets delivered, because a slipped date and an overrun are not the same size to every sponsor. A category breakdown lists the sources entries will be filed under. Role definitions say who identifies, who scores, who approves a response and who may accept exposure at each band. A short section fixes the register format and the meeting that carries its review.
How a BU 396 Unit 1 example is structured
Bands are defined before anything is scored because a rating produced against a private sense of high and low cannot be argued with, and this unit exists to remove that. Impact is split by objective rather than kept as one axis, since a project can absorb money it cannot absorb delay, and a single impact column hides which one the sponsor cares about. Categories precede identification so the later session has prompts to work through instead of relying on whatever the room remembers. Thresholds and the authority to accept sit with the roles rather than inside the register, which stops a scoring argument from becoming a decision nobody was entitled to make. The review cadence is fixed here and expanded later in the term, and naming it early keeps the plan from reading as a one-time exercise. A closing note marks the project as constructed for the assignment.
A document that names no risks
The plan settles how risk will be handled on this project and deliberately stops short of saying what those risks are.
Probability bands given numeric ranges
Each band carries a stated range rather than a word, so two people rating the same entry land in the same place.
Impact defined separately per objective
Cost, schedule and quality get their own definitions, because a sponsor who can fund an overrun may be unable to move a date.
Categories fixed before the search
A breakdown of sources is agreed in advance so identification works through prompts instead of depending on what the room happens to recall.
Authority to accept written down
The plan says which role may accept exposure at each band, which keeps a scoring argument from turning into an unauthorized decision.
Review cadence named at the start
When the register is revisited is fixed here, since a process defined once and never scheduled produces a document nobody reopens.
Where marks go in BU 396 Unit 1
This one loses points by describing risk in general. Three pages on why risk matters to projects, followed by a definition of probability copied from the reading, leave the plan itself unwritten. Bands given as high, medium and low with nothing behind the words put every later rating beyond challenge. Impact treated as one column means the plan cannot tell a schedule threat from a cost threat when both arrive together. Categories borrowed wholesale from a template, none of them touched to fit the project described, show the breakdown was pasted rather than reasoned. Plans assigning everything to the project manager have not distributed the work the process needs. Naming actual risks here is the commonest misread and it spends Unit 2 early. A risk framework lifted from an employer's own methodology belongs to that employer.
Get a BU 396 Unit 1 example written to your instructions
Send the Unit 1 instructions and the rubric posted in your BU 396 classroom, plus the project or case your section assigns. We write a custom example that defines the bands numerically, splits impact by objective, fixes categories and thresholds, and names who may accept what. First custom sample free, back in 24 to 48 hours.
BU 396 Unit 1 questions, answered
Can I set the bands however I like?
Within whatever the instructions fix, yes, and the reasoning behind your choice is the graded part. Bands have to suit the project in front of you, since a six month build and a three year program do not share a definition of a serious delay. State the range each band covers, say what the top one would mean for this sponsor, and use the same bands in every later unit.
Does this unit need a real project?
Follow the instructions, since many sections supply a case. Where the choice is open, a composite project you describe fully works better than a real one you only half know, because every band you define has to mean something measured against it. Say in the opening that the project is constructed, and treat its budget and its dates as case material rather than as facts about the world.
Is my company's risk methodology usable here?
No. A corporate risk framework, its rating matrix and the register templates built around it are internal property, and a graded submission is read by people outside that company. Build the bands from the course reading and the project described in the assignment. If the shape of what you handle at work informs your thinking, that is unavoidable and fine; reproducing the document itself is not.