A complete BU 396 Unit 2 risk identification workshop output: attendance, prompts, the raw capture, and surviving entries rewritten as condition, event and consequence. Searches like "bu 396 unit 2 assignment example", "bu396 unit 2 sample" and "bu 396 unit 2 example" land here.
What a finished BU 396 Unit 2 risk identification workshop output looks like
The output is a record with a working list inside it. It opens on the session: who was there, the role each brought, how long the session ran and which prompts were used, since a room of builders and a room including the sponsor produce different lists. The raw capture follows, printed as it was said, duplicates and vague entries still in place. A cleaning pass sits beside it, showing what was merged, what was dropped and on what grounds. Survivors then appear in a fixed form: the condition already true today, the event that might follow from it, and what that would do to a stated objective. An assumptions list closes the record, because most of what was found came out of questioning something the plan had quietly taken for granted.
How a BU 396 Unit 2 example is structured
The room is described before the list because who was present determines what could be found, and a session run by one person is not a workshop whatever the document is called. The raw capture is preserved rather than tidied away, since the cleaning pass can only be judged against what it started from. Merging and dropping carry reasons, which turns an editorial decision into something a reader is able to disagree with. The three part form arrives after cleaning rather than during capture, because insisting on it while people are still talking stops them talking. Assumptions are listed last but were used first, and saying so is honest about where identification actually comes from. Nothing here is scored, and the record says as much, since the moment a number appears the room begins arguing about ratings instead of finding entries it has not yet named.
Who was in the room, by role
The record names the roles present and the ones missing, because a list produced by a single writer has different coverage.
Prompts worked through in order
Category headings, the assumptions log and interview notes are each used as a separate pass rather than relying on open discussion.
Raw capture kept, not tidied
What was said appears before it was edited, so the cleaning decisions that follow can be judged against something visible.
Merges and deletions given reasons
Every entry removed carries a line saying why, which lets a reader argue with the editing rather than only with its result.
Survivors rewritten in a fixed form
Each one states a present condition, an uncertain event and the effect on a named objective, which is what a response can attack.
Nothing scored at this stage
Ratings are held back on purpose, since a room that starts arguing about numbers stops finding entries nobody has named yet.
Where marks go in BU 396 Unit 2
Identification loses credit by producing worries. Entries reading staff turnover, funding or scope creep name a heading, and a heading cannot be scored or owned. Lists that could describe any project at all, with nothing tied to the case described, show the prompts were never applied. Sessions reported without attendance, so that a workshop appears to have been held by one person, miss the part the unit is examining. Raw material thrown away before the cleaning pass leaves every merge unverifiable. Entries stated as certainties are issues rather than risks and belong in a different log, and mixing the two is the standing confusion here. Upside events left out narrow the record in many sections. Notes from a session actually run at work, with colleagues named and their concerns quoted, are not the writer's to publish.
Get a BU 396 Unit 2 example written to your instructions
Send the Unit 2 instructions and your BU 396 rubric, along with the project case and any category list your section supplies. We write a custom example that records the room, works the prompts as separate passes, keeps the raw capture beside the cleaned list and states every survivor as condition, event and consequence. First custom sample free, returned in 24 to 48 hours.
BU 396 Unit 2 questions, answered
How many risks should the session produce?
More than the register will keep. A first pass running to thirty or forty entries is normal and healthy, because the merging and dropping that follow are half the deliverable and need something to work on. Where the instructions set a final count, produce the long list first, then show the reduction down to that number with the reasoning attached rather than stopping early and pretending.
Do I have to hold an actual session?
Check what your instructions require, since some sections want a simulated session and others expect a real conversation with classmates. Where the session is constructed, say so plainly and write the roles as positions rather than as people. What fails is describing an event with attendees, timings and quoted contributions that never took place, then presenting it as something recorded.
What separates a risk from an issue?
Whether it has happened yet. A supplier that might miss a date is a risk carrying a probability; a supplier that has already missed one is an issue and gets managed differently. Entries written in the present tense are usually issues in disguise, and a register holding them will score responses against events that no longer need a probability at all.