A finished BU 345 Unit 6 risk response table: threats and opportunities rated on a defined scale, each with a response, an owner and a residual rating. Searches like "bu 345 unit 6 assignment example", "bu345 unit 6 sample" and "bu 345 unit 6 example" land here.
What a finished BU 345 Unit 6 risk response table looks like
The table is wide and the prose around it is short. Each row opens with a risk written as a cause, an event and an effect, which is what stops entries reading as one word worries. Probability and impact follow, rated against a scale printed above the table so a reader knows what a rating of four means. A score column orders the register, and a response column names the strategy: avoid, transfer, mitigate or accept for threats, with the parallel set used for the opportunities. Actions sit beside the strategy, an owner beside the actions, and a residual rating at the end of the row. Trigger conditions appear for the entries worth watching. A footnote marks the register as belonging to an invented job.
How a BU 345 Unit 6 example is structured
The rating scale is printed before any risk is rated, because a register scored against an unstated scale cannot be read by anybody except its author. Risks are written in cause, event and effect form so the response has something to attack: a cause can be removed, an event can be planned for, an effect can be reduced, and a one word risk offers none of those. Scoring orders the table, but the order is not the analysis, so responses come next and each names the part of the risk it addresses. Owners are individuals by role rather than departments, since a threat owned by everybody is watched by nobody. Residual ratings close each row, which is where a reader learns whether the response was worth what it costs.
Scale printed above the table
What a probability of four or an impact of two means is set down first, or the ratings cannot be read.
Risks written as cause, event, effect
Each entry names what could happen, what would trigger it and what it would do, giving the response something specific to attack.
Strategy named before the actions
Every row says whether the risk is being avoided, transferred, reduced or accepted, since the actions only make sense underneath that choice.
One owner per risk, by role
Responsibility sits with a single role rather than a department, because a threat assigned to everyone is monitored by no one.
Residual rating closes each row
What remains after the response has worked is rated again, which is where a reader sees whether the effort bought anything.
Opportunities included, not only threats
A couple of rows cover upside events, since most sections read a register of pure threats as half the exercise.
Where marks go in BU 345 Unit 6
Registers lose marks by staying vague. Entries reading budget, weather or communication name a category rather than a risk, and no response can be written against them. Probability and impact scored with no scale above the table make the numbers private to the writer. Responses amounting to monitoring the situation are acceptance without the word, and a table where most rows do that has avoided the work of the unit. Risks with no owner, or owned by the project team collectively, will not be managed. Residual ratings identical to the original ones say the response does nothing. Registers ignoring opportunities cover half the ground in most sections. A real risk log from work, with a named supplier and a live commercial dispute in it, is not the writer's document to reproduce.
Get a BU 345 Unit 6 example written to your instructions
Send the Unit 6 instructions and the rubric from your BU 345 classroom, with the rating scale your section supplies if there is one. We write a custom example that prints the scale first, writes each risk as cause, event and effect, assigns a strategy and an owner, and rates what is left. First custom sample free, back in 24 to 48 hours.
BU 345 Unit 6 questions, answered
How many risks should the table hold?
Follow the count the instructions give. Where none is set, a register somewhere between eight and a dozen rows lets a writer show range without repeating one threat in different words. What matters more is spread: entries drawn from the schedule, the budget, the supply chain, the sponsor and the technical work, rather than five versions of running late.
Is accepting a risk a weak answer?
No, and a register with nothing accepted usually means the writer thought acceptance would look lazy. Small, cheap risks are accepted every day on real work, and saying so, with the trigger that would change the decision, reads as judgment. What loses marks is acceptance disguised as mitigation by promising to monitor something closely.
Do the opportunities have to be realistic?
They have to be arguable from the project you described. An early supplier delivery that lets a later package start sooner, or a package that could be shared with another team, are the kind of upside a marker recognizes. Vague optimism about efficiencies is the opportunity equivalent of a one word threat and earns about as much.