| Course | PM FPX 4020 Integration and Scope Management |
|---|---|
| Assessment | Assessment 2 |
| Paper type | Scope statement |
| Length | About 1,140 words, 5 pages |
| Format | APA 7 student paper |
| School | Capella University |
| Program | BS in Business, Project Management |
| Updated | September 2026 |
Free sample paper for PM FPX 4020 Assessment 2
A Scope Statement for a Veterinary Hospital Relocation: Exclusions Written as Full Statements, Acceptance Criteria Beside Each Deliverable, Assumptions and Constraints Kept Apart, a Change Process at the Boundary, and Language Flat Enough to Enforce
Student Name
Capella University
PM FPX 4020: Integration and Scope Management
Instructor Name
Month Day, Year
Project Description
Maple Ridge Animal Hospital is leaving its rented Elm Street space for the Prairie Road building the owner bought last summer. The project renovates the building for veterinary use, installs new equipment and IT, moves the practice, and opens for patients by June 1. The Project Management Institute (2017) describes the scope statement as the detailed description of the project's deliverables and the work required to create them, used as the basis for later decisions about whether a piece of work belongs to the project.
Deliverables With Acceptance Criteria Beside Each
D1, construction drawings and specifications. Acceptance: drawings stamped by a licensed architect; approved in writing by the sponsor; showing the room counts in the charter, a radiology room, a treatment area, and kennels for 30 animals. D2, building permit and premises permit. Acceptance: city building permit issued; state veterinary premises permit issued before any patient is seen. D3, renovated building. Acceptance: all work in the construction drawings complete; city certificate of occupancy issued; punch list items from the staff walkthrough closed or scheduled with sponsor approval; surgical lighting measured at the illumination level stated in the specifications. D4, radiology room. Acceptance: shielding certified by a qualified physicist; X-ray unit registered with the state radiation control program. D5, installed equipment. Acceptance: each item delivered, installed, and tested by the vendor with a signed installation report; staff trained, with attendance recorded. D6, IT and phones. Acceptance: every workstation connects to the practice software; phone system routes calls to all extensions; wireless coverage confirmed in every room. D7, completed move. Acceptance: all items on the move inventory present at the new building; patient records accessible; controlled substances transferred and logged as required. D8, opening. Acceptance: first patient appointment at the new building on or before June 1. An acceptance criterion is the test the sponsor will run before signing off. If it cannot be run, it is not a criterion.
An Exclusions List That Does Work
Exclusions are written as full statements so they can settle disputes. The project does not include work on a second practice location. The project does not include selling or disposing of equipment that will not be moved; that is handled by the practice outside the project. The project does not include landscaping, parking lot resurfacing, or exterior signage beyond what the city requires for the certificate of occupancy. The project does not include replacing the practice management software; the current system moves unchanged. The project does not include adding services such as boarding, grooming, or rehabilitation. The project does not include furniture for the staff break room beyond moving the existing furniture.
Assumptions and Constraints Kept Apart
Assumptions are things believed true that may turn out not to be. The city will review the permit within six weeks. The pre-purchase inspection found no roof, wiring, or pipe problems that would need repair. Equipment lead times will be about 12 weeks. The Elm Street landlord will allow monthly extension if needed. Constraints are fixed limits the project must work within. The opening must be on or before June 1. The total budget is 1,435,000 dollars. Under the loan terms, construction has to start no later than 90 days after the purchase closed. Animals may not be housed overnight before the certificate of occupancy is issued. The move may close the practice for no more than two business days.
A Change Process Attached to the Boundary
Any request that adds, removes, or changes a deliverable or acceptance criterion goes through the change process. The requester completes a change request form describing the change and its reason. The project manager, with the architect or contractor as needed, estimates the effect on cost, schedule, and quality within five business days. Changes costing up to 5,000 dollars with no schedule effect may be approved by the project manager, up to 20,000 dollars in total. All others go to the sponsor, who decides within five business days. Approved changes update this scope statement, the schedule, and the budget, and are recorded in the change log.
Relationship to Other Documents
The scope statement sits between the charter and the detailed plans. It expands the charter's high-level scope into deliverables and acceptance tests, and it is expanded in turn by the work breakdown structure and the construction drawings. If the scope statement and the drawings disagree, the drawings govern construction details and the scope statement governs what is included in the project.
Language Flat Enough to Enforce
The statement avoids words that cannot be enforced. It does not say "state-of-the-art equipment," "adequate lighting," or "a modern, welcoming space." Instead it names equipment by model in the equipment list, states lighting as a measured level in the specifications, and describes spaces by count and function. Flat language protects both sides: the contractor knows what is required, and the practice can hold the contractor to it. Adjectives are where scope disputes start.
Who Accepts Each Deliverable
Acceptance authority is named for each deliverable so that sign-off does not stall. The sponsor accepts the drawings, the renovated building, and the opening. The project manager accepts the IT installation and the move inventory, after checking against the acceptance criteria. The lead technician accepts installed equipment on the practice's behalf after training. The architect advises the sponsor on whether the building meets the drawings but does not accept it. Knowing who signs prevents the common problem of a contractor asking three people for sign-off and receiving three different answers.
Scope Risks at the Boundary
The most likely scope disputes are already visible. The veterinarians have asked about a second dental station, which is not in the drawings. The contractor has asked whether the parking lot restriping is included, which it is not unless the city requires it. The client service team has asked for a new phone menu, which is part of the phone system deliverable only if it uses the existing call flow. Each of these would go through the change process.
How the Statement Will Be Used
The scope statement is the basis for the construction contract's scope, the equipment purchase orders, and the work breakdown structure. It will be reviewed at each weekly site meeting when change requests are considered.
Conclusion
The scope statement lists eight deliverables, each with an acceptance test, six exclusions written as full statements, assumptions and constraints kept separate, a change process tied to the project manager's and sponsor's authority, and language plain enough that the contractor and practice can both enforce it.
References
Project Management Institute. (2017). A guide to the project management body of knowledge (PMBOK guide) (6th ed.). Project Management Institute.
PM FPX 4020 Assessment 2 instructions, in plain terms
Assessment 2 in PM FPX 4020 has you write a detailed scope statement for the project chartered in Assessment 1. You describe the product of the project, list each deliverable with its acceptance criteria, state what is excluded, separate assumptions from constraints, explain how changes to scope will be requested and approved, and name who accepts each deliverable. The statement should be precise enough that a dispute about whether something is in scope can be settled by reading it. Scope management texts and the PMBOK Guide's guidance on the project scope statement support the work.
How the PM-FPX4020 Assessment 2 example is put together
The example builds the boundary outward from the deliverables. It opens with the product description in a paragraph, so a reader knows what is being produced before reading a list. The deliverable section then names each item, and each item gets acceptance criteria immediately underneath rather than in a separate table, which keeps the pair together where a reviewer needs it. The exclusions section follows and is written as full statements rather than as a bulleted afterthought, each naming the thing excluded and, where useful, the reason. Assumptions and constraints occupy two separate sections, since collapsing them hides which items the project controls. A change process section closes the document by naming who can move the boundary, on what evidence, and what happens to the schedule and budget when they do.
PM FPX 4020 Assessment 2 scoring guide: what Distinguished looks like
The scoring guide weighs the deliverables, the acceptance criteria, the exclusions, the assumptions and constraints, the change process and the language. Deliverables reach Distinguished when each is a tangible result. Acceptance criteria score higher when placed beside each deliverable and written so they can be tested, such as all exam rooms passing inspection. Exclusions earn credit when written as full statements, like "The project will not replace existing X-ray equipment." Assumptions and constraints are judged on whether they are kept apart. The change process should be attached to the boundary. Language should be plain and enforceable, avoiding words like "appropriate." Distinguished statements settle arguments before they start.
PM FPX 4020 Assessment 2 help from the desk
Scope statements frequently list deliverables with no acceptance criteria, which leaves room to argue about whether each one is finished. Another weakness is a short exclusions list of single words, like "furniture," that do not say what exactly is excluded. Assumptions and constraints are mixed, so the reader cannot tell which are facts to work within and which are beliefs to test. The change process is missing. Language is vague, with terms like "as needed." Acceptance is not assigned. Writing each deliverable in a table with its acceptance criteria and the person who accepts it, followed by exclusions written as sentences, makes the boundary clear and supports the work breakdown structure in Assessment 3.
Get a PM FPX 4020 Assessment 2 example written to your instructions
Send the Assessment 2 instructions and the scoring guide from your PM FPX 4020 courseroom, along with the charter or case scenario the scope has to come from. We write a custom example to those criteria, with acceptance criteria and exclusions written out properly, and return it in 24 to 48 hours. The first custom sample is free. The paper above is an original model document written by our desk, not a submitted student paper and not an official Capella University document.
More PM FPX 4020 papers and BS in Business, Project Management samples
- PM FPX 4020 Assessment 1: Project Charter
- PM FPX 4020 Assessment 3: Work Breakdown Structure
- PM FPX 4030 Assessment 2: Cost Baseline
- PM FPX 4000 Assessment 2: Domain Analysis
- PM FPX 4040 Assessment 2: Staffing Management Plan
- PM FPX 1000 Assessment 2: Life Cycle Overview
PM FPX 4020 Assessment 2 questions, answered
How many exclusions is enough?
Enough to close the gaps a reasonable stakeholder would walk through. Work outward from each deliverable and ask what sits next to it: adjacent systems, later phases, training for other departments, historical data, ongoing support, hardware, licensing. Six to ten specific exclusions is common on a course-sized project, and each one should be something somebody might genuinely have expected.
What is the difference between an assumption and a constraint?
An assumption is something you have accepted as true without proof, such as a vendor delivering in a stated window or a department releasing staff. A constraint is a limit imposed on the project from outside, such as a fixed regulatory date, a capped budget or a technology the organization mandates. Assumptions can fail; constraints simply apply.
Should acceptance criteria be measurable?
Yes, and that is where most versions fall short. A criterion reading that the system performs well gives a reviewer nothing to check, while one naming a response time, a defect threshold, a document approved by a named role or a test suite passing does. Write each criterion as something that can be observed and recorded on a specific date.
Where can I find a free PM FPX 4020 Assessment 2 sample paper?
This page contains the complete scope statement for the veterinary hospital relocation, with acceptance criteria beside each deliverable, exclusions written as full statements and a change process at the boundary.
Why write exclusions as full statements in PM FPX 4020 Assessment 2?
A single word like "furniture" leaves room to argue about which furniture. A full sentence states exactly what the project will not do, which prevents scope creep later.