MGT 440 Topic 3 scope statement and change log example

Project Management Grand Canyon University Free custom sample in 24 to 48h

This MGT 440 Topic 3 sample paper sets out three linked documents for a credit union's contact center relocation: a scope statement, a work breakdown structure and a change log. It was prepared for GCU MGT 440, Project Management, catalog code MGT-440, in the Grand Canyon University BS in Business Management. Five deliverables carry acceptance criteria, and seven exclusions name what is not moving or changing. The work breakdown has five branches, each work package with an owner. The change log records three requests: adding the collections team at $24,000 and eight critical path days is rejected and deferred, a quiet room is approved and headsets are deferred.

CourseMGT 440 Project Management
TopicTopic 3
Paper typeScope statement and change log
LengthAbout 970 words, 3 pages
FormatAPA 7 student paper
SchoolGrand Canyon University (GCU)
ProgramBS in Business Management
UpdatedOctober 2026

Free sample paper for MGT 440 Topic 3

1

What Moves, What Stays and What Was Asked For Later: Scope Statement, Work Breakdown and Change Log for a Contact Center Relocation

[Author Name]

Colangelo College of Business, Grand Canyon University

MGT-440: Project Management

Topic 3 Assignment

[Instructor Name]

[Date]

The organization, setting and figures below are a composite written as a model document. No real employer, client, colleague or patient is described.

What this page is doingThe title names the three linked documents by what each answers, so a reader knows the exclusions and the change requests carry as much weight as the deliverables. The credit union and every figure are an illustrative composite; the sources are real.
2

What Moves, What Stays and What Was Asked For Later: Scope Statement, Work Breakdown and Change Log for a Contact Center Relocation

Scope Statement

The project moves the credit union's phone and chat team out of rented ground-floor offices and up to vacant owned space before the October 31 lease deadline. The scope statement lists what the project will deliver and the criteria each deliverable must meet to be accepted, and, just as importantly, what it will not do. A clear list of exclusions is the first defense against scope creep, because requests that were never authorized are easier to recognize when the boundary is written down (Project Management Institute, 2021).

Table 1

Deliverables and Acceptance Criteria

DeliverableAcceptance criteria
Third-floor workspace for the contact center40 agent workstations, 2 supervisor stations and a 10-person huddle room, built to the approved layout and passing building inspection
Network and telephonyAll 42 stations connected to the credit union network and phone platform, with call routing tested on every station
Furniture and equipmentErgonomic desks and chairs at all stations; headsets and dual monitors moved or replaced; damaged items replaced
CutoverAll agents taking calls from the third floor by October 24, with member service below standard for no more than one business day
Decommissioning of the old spaceOld space cleared, network equipment removed and keys returned by October 31

Each acceptance criterion is written so that the person accepting the deliverable can check it without asking the project team what it meant. The cutover criterion, for example, uses a service measure the contact center already reports daily.

Exclusions

The following are outside the project. Any request to add them goes through the change process below.

1. Moving the back-office teams on the first floor: the loan processing and card services teams stay where they are under a separate lease decision.

2. Replacing the phone platform: the existing platform is moved and reconnected, not upgraded.

3. Changing call routing rules or menu options: routing is tested for continuity only.

4. Moving the collections team, which shares the first floor with the contact center but reports to lending.

5. Redesigning contact center staffing, schedules or service standards.

6. Renovating third-floor areas outside the contact center footprint, such as the adjacent conference rooms.

7. Purchasing new computers: existing computers are moved; only failed units are replaced.

Several of these exclusions came from conversations during chartering, when stakeholders mentioned things they hoped the move would also fix. Writing them down now means each of those hopes is acknowledged and can be pursued separately, rather than quietly attached to this project.

What this page is doingThe exclusions list is longer than the deliverables list on purpose, because the requests most likely to arrive later are the ones a reader would otherwise assume were included.
3

Work Breakdown Structure

Table 2

Work Breakdown Structure

BranchWork packagesOwner
1. Workspace1.1 Layout design and approval; 1.2 Electrical upgrade; 1.3 Build-out and cabling; 1.4 Building inspectionFacilities coordinator
2. Network and telephony2.1 Network design; 2.2 Switch and cabling installation; 2.3 Phone platform reconnection; 2.4 Station testingNetwork engineer
3. Furniture and equipment3.1 Furniture ordering; 3.2 Furniture installation; 3.3 Equipment move and replacementFacilities coordinator
4. Cutover4.1 Cutover plan; 4.2 Agent communication and training; 4.3 Cutover weekend; 4.4 First-week supportProject manager
5. Decommissioning5.1 Equipment removal; 5.2 Space clearing; 5.3 Lease handbackFacilities coordinator

Below, the deliverables are broken down into five branches and their work packages. Each work package has an owner, and nothing appears that the scope statement does not authorize. The structure should hold every piece of authorized work and nothing beyond it, so its parts add up exactly to the project (Project Management Institute, 2019).

The breakdown follows the deliverables rather than the departments doing the work, which keeps each branch tied to something the sponsor will accept. Work packages are small enough to estimate and assign but not so small that the structure becomes a task list (Haugan, 2002). The cutover branch belongs to the project manager because it requires coordinating every other branch.

Ownership is assigned at the work package level, not the branch level, so that each package has a single person accountable for estimating it, doing it and reporting its progress.

Change Log

Table 3

Change Log, First Month

No.Request and sourceCost impactSchedule impactDecision
1Add the collections team, 12 agents, to the move (Head of Lending)+$24,000+8 days on the critical pathRejected for this project; deferred to a follow-on move in the first quarter
2Add a quiet room for agents handling difficult calls (Contact Center Manager)+$3,500None; built within existing footprintApproved; funded from contingency
3Upgrade all headsets to noise-canceling models (Contact Center Manager)+$9,600NoneDeferred; to be funded from the contact center's operating budget next year

Three change requests were received in the first month after the charter was signed. Each is recorded with its source, its estimated impact and the decision. Impacts are illustrative estimates.

Why Each Decision

The collections team request is the most significant. It would add twelve workstations, require a larger build-out and add eight days to the critical path, leaving only a few days between the planned completion and the lease end. It also appears on the exclusions list. The sponsor rejected it for this project because the end date is fixed, and deferred it to a separate move once the contact center is settled.

The quiet room was approved because it fits within the footprint, does not affect the schedule and costs little. The headset upgrade was deferred because it is an operating improvement rather than part of the move. Recording each decision, rather than handling requests in conversation, means the project can show later why its scope looks the way it does.

The change log will be kept until closure and reviewed at every status meeting. A request that is deferred is not lost; it is listed with an owner in the closure report so the organization can decide whether to pursue it later.

References

Haugan, G. T. (2002). Effective work breakdown structures. Management Concepts.

Project Management Institute. (2019). Practice standard for work breakdown structures (3rd ed.). Project Management Institute.

Project Management Institute. (2021). A guide to the project management body of knowledge (PMBOK guide) (7th ed.). Project Management Institute.

The MGT-440 Topic 3 assignment instructions

MGT-440 Topic 3 asks students to define a project's scope and control changes to it. A list of tasks presented as scope, or a scope statement with no exclusions, will not hold up once requests start arriving. The prompt rewards deliverables with acceptance criteria, a list of exclusions at least as long as the deliverables, a work breakdown structure that contains all the authorized work and nothing else, and a change log that records requests with their cost and schedule impacts and the decisions taken. Students should explain the reasoning behind each change decision, with attention to whether a request touches the critical path or the fixed constraint.

Inside the MGT 440 Topic 3 example

The paper opens with the scope statement and the role exclusions play in preventing scope creep. Table 1 lists five deliverables with acceptance criteria. Seven exclusions follow. Table 2 sets out the work breakdown structure in five branches with work packages and owners, followed by a note on why it follows deliverables rather than departments. Table 3 records three change requests with sources, cost and schedule impacts and decisions. A closing section explains each decision, especially why the collections team request was rejected for this project given the fixed lease date. Each table is short enough to read at a status meeting.

MGT 440 Topic 3 rubric: what Excellent looks like

Faculty grading the scope documents reward acceptance criteria that can be checked and exclusions that anticipate the requests most likely to come. Strong papers keep the work breakdown structure aligned with the scope statement, so nothing appears in one that the other does not authorize. Credit goes to a change log with estimated impacts and a recorded decision for each request. The rubric values explaining decisions in terms of the fixed constraint and the critical path. The highest band shows how the three documents depend on one another. Scope statements that list only deliverables, or change logs that record requests without decisions, tend to lose points.

MGT 440 Topic 3 help before you submit

The edges decide most of the scope marks. Scope statements that describe the project enthusiastically and never say what it excludes leave every neighboring department free to assume its needs are included. Deliverables with no acceptance criterion cannot be closed, because nobody agreed in advance what finished means. Work breakdown structures organized by department or by calendar phase, rather than by deliverable, lose the 100 percent check and usually omit project management work entirely. Change processes described in general terms, with no approval levels, route every request to whoever is most senior in the room. Logs that approve changes without recording cost, schedule impact and a re-baseline let the project grow through approvals nobody priced, which is how the original budget stops meaning anything.

Get an MGT-440 Topic 3 example written to your instructions

Send the MGT-440 Topic 3 instructions, the rubric in your classroom and the project the assignment is built around. We write a custom example to those criteria, with deliverables and acceptance criteria, exclusions stated, a work breakdown structure that passes the 100 percent rule and change requests logged with their impact, in 24 to 48 hours. The first one is free.

More MGT 440 papers and BS in Business Management samples

MGT 440 Topic 3 questions, answered

What is the 100 percent rule?

The principle that a work breakdown structure includes all of the work defined by the project scope and nothing outside it, with each level summing exactly to the level above. It turns the structure into a test: a task found later that fits nowhere in it is either unauthorized work or a gap in the original scope, and either way it needs a decision.

Should a WBS be organized by deliverable or by phase?

Most project management texts prefer deliverables, because they can be accepted and checked, while phases describe time rather than outputs. Some organizations use phases at the top level for reporting and deliverables beneath them. The example uses deliverables throughout and keeps project management as its own branch, since that work consumes hours and budget too.

Who should approve a change request?

It depends on the size of the change, and the change process should say so in advance. Small changes within reserve and with no schedule effect may sit with the project manager; anything affecting the fixed constraint or drawing heavily on reserve goes to the sponsor or a change board. Writing those thresholds down keeps every request from becoming a negotiation.

Where can I find a free MGT 440 Topic 3 sample paper?

All three documents for the contact center move appear above: the scope statement and exclusions, the work breakdown structure and the change log with reasons for each decision. Send your project's deliverables and a free version can be built for it.

Why was the collections team rejected in MGT 440 Topic 3?

Adding twelve workstations would cost $24,000 and add eight days to the critical path, leaving little margin before the fixed lease date. The team was on the exclusions list and its move was deferred to a later project.