The BU 345 Unit 2 charter and stakeholder register in full: authorization, business case and success measures, followed by every party the work touches. Searches like "bu 345 unit 2 assignment example", "bu345 unit 2 sample" and "bu 345 unit 2 example" land here.
What a finished BU 345 Unit 2 charter and stakeholder register looks like
The charter half occupies the first page and reads like an internal authorization rather than a proposal. It names the project, the sponsor, the manager and the authority that manager holds, which is the line most drafts leave vague. A business case paragraph follows in the sponsor's terms rather than the writer's: what problem the work removes and what the firm gets. Objectives appear next, each written so a reader could tell later whether it happened. High level scope, assumptions, constraints and a coarse milestone list finish the charter. The register is a table on the second page, one row a party, carrying interest, influence, what they need to hear and who carries it to them. Rows include the parties nobody wants there. A note at the foot places the whole document inside a constructed case.
How a BU 345 Unit 2 example is structured
Authorization sits at the top because everything after it depends on somebody having the standing to commit the money. The business case precedes objectives, since an objective with no problem above it is a preference, and objectives precede scope, because scope is the boundary drawn around them. Assumptions and constraints are separated rather than merged: an assumption can be tested and may prove false, while a constraint is fixed and shapes the plan whether the writer likes it or not. Milestones stay coarse here, since detailed dates belong to the schedule unit and a charter that estimates too early usually contradicts itself later. The register comes after the charter, because a party's influence can only be rated once a reader knows what the project will change. Difficult parties are entered in the table rather than mentioned in a note.
Authority stated rather than implied
The charter says what the manager may commit without returning to the sponsor, which is the line most drafts leave comfortably vague.
Business case written in sponsor language
The problem and the payoff appear as the person funding the work would state them, not in the vocabulary of project management.
Assumptions kept apart from constraints
One can be tested and may collapse, the other is fixed, and merging them hides which exposures the plan is quietly carrying.
Milestones left coarse at this stage
Dates stay rough in the charter, because detailed estimates made before the breakdown exists tend to contradict the schedule two units later.
Every party earns a row
The register runs one line per party, with interest, influence, what they need to hear and the name of whoever tells them.
Unwelcome parties entered too
The department losing headcount and the vendor being displaced appear in the table, since the parties who resist are the ones needing management.
Where marks go in BU 345 Unit 2
Charters lose marks by drifting into proposal writing. A page arguing why the project deserves funding, with no authorization, no named sponsor and no statement of what the manager may spend, has produced a pitch and skipped the document. Objectives phrased as improve efficiency or enhance communication cannot be checked at closeout, and the closeout unit will need them. Registers listing only friendly parties, with the displaced group and the resisting manager left out, describe a project nobody would need to manage. Influence and interest rated with no reason attached read as guesses. Scope written at the level of individual tasks belongs three units later. Real sponsors, live approval emails and an employer's actual spending authority carry material into a submission that no classroom assignment requires.
Get a BU 345 Unit 2 example written to your instructions
Send the Unit 2 instructions and the rubric from your BU 345 classroom, plus the project you carried forward from Unit 1. We write a custom example that states authority plainly, puts the case in sponsor language, keeps assumptions and constraints apart and registers the awkward parties. First custom sample free, returned in 24 to 48 hours.
BU 345 Unit 2 questions, answered
Who should the sponsor be if the project is invented?
Give the role rather than a person: the operations director who owns the budget line, the partner who signs off capital under a stated amount. A named individual adds nothing a marker can grade and creates a problem if the name belongs to somebody real. State the role, the authority it carries and the point where that authority stops.
How many stakeholders belong in the register?
Follow any count the instructions give, and otherwise let the project decide. A dozen rows on work four people deliver looks padded, while three rows on a project crossing two departments has missed most of it. The test is whether a party can affect the project, or be affected by it, in a way somebody would have to manage.
Does the charter need a budget number?
Most sections want an order of magnitude rather than an estimate, since the estimating work belongs to the cost unit. Give a range, say what it rests on, and mark it as preliminary. What matters here is that the sponsor's approval covers a figure, so the baseline built later has something to be measured against.