| Course | PM 340 Project Delivery and Measurement (PM/340) |
|---|---|
| Week | 1 |
| Paper type | Project work domain analysis |
| Length | about 1,060 words, 4 double-spaced pages plus title page and references |
| Format | APA 7 student paper |
| School | University of Phoenix |
| Program | BS in Business |
| Updated | October 2026 |
Free sample paper for PM 340 Week 1
Mammoth Bones and Purchase Orders: The Project Work Domain in a Museum Gallery Build
[Student Name]
University of Phoenix
PM/340: Project Delivery and Measurement
Week 1 Assignment
[Instructor Name]
[Date]
Prairie River Museum of Natural History, its gallery project, people and figures are composites written for a model paper.
The Prairie River Museum of Natural History, a composite museum in Omaha, Nebraska, is replacing a 1980s dinosaur hall with a 9,000-square-foot gallery on the Ice Age animals of the Great Plains: Columbian mammoths, giant ground sloths, short-faced bears and the ancient bison whose bones turn up in Nebraska river gravels. The project's budget is $3.8 million, raised mostly from donors, and its opening is fixed for the Saturday before spring break, when the museum's attendance peaks and the donors' preview has already been announced. Design is complete. This paper examines the project work domain as the team moves into fabrication and installation.
What the Project Work Domain Covers
The current standard describes the project work performance domain as the activities and functions of establishing project processes, managing physical resources and procurement, keeping the team engaged and communicating and fostering a learning environment (Project Management Institute [PMI], 2021). Other domains describe what should happen; this one is about making it happen each day. The museum's project manager, Teresa Whitfield, spends most of her week in this domain: approving shop drawings, answering fabricator questions, tracking crates of specimens and keeping a team of curators, designers, contractors and media producers working on the same version of the gallery.
Establishing and Improving Processes
The team's process for approving fabricator shop drawings was slow. Each drawing went to the designer, the lead curator and the facilities manager in sequence, and the average approval took nine working days against a target of five. At a process review in the first month, the team found that most delays happened while drawings waited for the curator, who reviewed them only for scientific accuracy of labels and models. The team split the review: the designer and facilities manager approve construction details, and the curator reviews only the elements carrying scientific content, in parallel. Average approval time fell to four days. The standard encourages exactly this kind of review of process efficiency during the work (PMI, 2021).
Managing Physical Resources
Physical resources include fabricated casework, lighting, a cast skeleton of a Columbian mammoth, 160 fossil specimens from the museum's own collection and 22 on loan from a state university. Loaned specimens carry conditions on temperature, humidity, light levels and handling. Whitfield set a protocol: every specimen move is logged by the registrar, handled only by trained staff, staged in a climate-controlled room until its case is certified ready and photographed before and after installation. Cases are delivered in the order they will be installed so the gallery floor never becomes a warehouse.
A fossil that waits in a hallway for a missing case is a schedule problem and a conservation problem at once.
Working With Suppliers
The museum has two main contracts: a fixed-price agreement with an exhibit fabricator in Minneapolis for casework, scenery and the mammoth mount, and a time-and-materials agreement with a media studio for three interactive stations and a short film. Turner and Simister (2001) argued that the choice of contract type should fit the uncertainty in the work: fixed prices suit well-defined scope, while cost-based terms suit work whose content will change. The museum's choices follow that logic, since the casework is drawn in detail but the interactives will evolve with visitor testing.
Managing these suppliers goes beyond the contracts. Whitfield visits the fabricator's shop every three weeks, reviews finished pieces before they ship and holds a weekly call with each supplier. Payments are released against inspected milestones, such as the mammoth mount passing a load test at the shop, so the museum pays for finished work it has seen rather than for percentages reported on an invoice. When the fabricator found that a curved case wall could not be made in tempered glass at the drawn radius, the weekly call settled on laminated glass in four days instead of a formal dispute.
Handling New Work
Donors sometimes ask for additions. One family asked for a donor wall in the gallery entrance; a board member asked for a children's dig pit. The team screens every new request with three questions: does it serve the gallery's purpose, can it fit within the budget and schedule and who approves it? The donor wall fit the purpose and could be built from the contingency; it went to the sponsor and was approved. The dig pit could not be built safely in the space before opening and was added to a list for a later phase.
Keeping the Team Focused
During installation, the team meets for 15 minutes every morning at the gallery entrance: what was installed yesterday, what goes in today and what is blocking anyone. A wall chart shows each case's status from shop drawing to finished. A weekly summary goes to the museum director and the development office, which keeps donors informed. Messages stay short and frequent because installation problems, such as a case that does not fit its floor anchors, must be solved within hours.
Learning During the Project
Williams (2008) surveyed project practitioners and found that while most organizations held lessons-learned reviews, the lessons were often not used in later projects, and that learning worked better when it was embedded in people and practices rather than stored only in reports. The museum will open two more renovated galleries within five years. Whitfield keeps a running lessons log, reviewed at each weekly meeting, and assigns each lesson to an owner who will carry it into the next project's procedures, such as the split drawing review and the specimen staging rule.
Connecting to Other Domains
Project work links directly to delivery and measurement, the subjects of later weeks. Efficient processes and well-managed suppliers make it possible to deliver the gallery's scope at the required quality. The status chart and daily stand-ups produce the data the team will use to measure progress. Learning captured now improves both domains on the next gallery.
Conclusion
The gallery's opening date depends on hundreds of small actions: approving a drawing, staging a fossil, settling a glass question with a supplier, screening a donor's request and solving a floor-anchor problem before lunch. The project work domain gathers those actions into a discipline: efficient processes, careful handling of physical resources, procurement managed as a relationship, controlled acceptance of new work, focused team communication and learning that outlasts the project.
References
Project Management Institute. (2021). A guide to the project management body of knowledge (PMBOK guide) (7th ed.). Project Management Institute.
Turner, J. R., & Simister, S. J. (2001). Project contract management and a theory of organization. International Journal of Project Management, 19(8), 457-464. https://doi.org/10.1016/S0263-7863(01)00051-5
Williams, T. (2008). How do organizations learn lessons from projects: And do they? IEEE Transactions on Engineering Management, 55(2), 248-266. https://doi.org/10.1109/TEM.2007.912920
What the PM 340 Week 1 instructions ask
In Week 1 of PM 340, students are commonly asked to explain the project work performance domain and how it supports delivery. Prompts often name the activities in the domain: establishing efficient processes, managing physical resources, working with procurements and contracts, monitoring new work and changes, keeping the team focused and communicating, and enabling learning through knowledge management. You may be asked to apply these to a project you know or one described in the classroom. Explain each activity with an example, note how the domain connects to others such as planning and delivery and use the standard plus scholarly sources in APA style. Keep the discussion operational, since this domain is about doing the work.
How this PM 340 Week 1 example is built
Our worked sample follows a museum gallery from fabrication through installation. It explains why project work is its own domain: plans do not move crates or answer a fabricator's question at 4 p.m. on a Friday. The paper then walks through six activities with museum examples: a weekly process review that cut drawing approval time, a specimen-handling protocol for fossils on loan, contracts with an exhibit fabricator and a media studio, a rule for new requests from donors, a short daily stand-up during installation and a lessons log tied to the museum's next gallery. Research on contracting relationships and on learning from projects supports two of those sections, and the conclusion links the domain to delivery and measurement in later weeks.
PM 340 Week 1 grading rubric: where the points go
Points on this paper follow operational detail. High marks go to papers that explain each activity in the domain accurately and show it in practice: a process that was examined and improved, physical resources handled with care, a procurement relationship managed beyond the contract signature, new work screened before it is accepted, communication that keeps the team focused and knowledge captured in a usable way. Graders also look for links between this domain and others, especially delivery and measurement. Scholarly sources on contracting, knowledge management or process improvement show research beyond the standard. Clear organization, consistent terms, specific examples and correct APA citations complete the strongest papers.
PM 340 Week 1 help: mistakes to avoid
Domain papers often turn into a list of definitions copied from the standard. Use one sentence to define each activity and the rest to show it on your project. Another frequent issue is treating procurement as a one-time purchase rather than a relationship that has to be managed through delivery. Describe how you work with suppliers after the contract is signed. Students also overlook knowledge management or reduce it to a lessons-learned meeting at the end. Show how learning is captured during the work and used afterward. Some papers ignore physical resources entirely; materials, equipment and their logistics often decide the schedule. Finally, connect the domain to delivery and measurement. A tutor can help you choose examples that show the domain clearly.
Related PM 340 sample papers
Other PM 340 week samples
- PM 340 Week 2: Delivering Scope and Quality
- PM 340 Week 3: Measures and Baselines
- PM 340 Week 4: Earned Value and Dashboards
- PM 340 Week 5: Managing Uncertainty
More BS in Business sample papers
- MKT 498 Week 1: IMC Basics and Situation Analysis
- PM 300 Week 1: Projects and Value Delivery
- PM 310 Week 1: Stakeholders and Engagement
- PM 350 Week 1: Organizational Project Management
PM 340 Week 1 questions, answered
What does PM 340 Week 1 usually cover?
It usually covers the project work performance domain: establishing processes, managing physical resources, working with suppliers and contracts, handling new work, keeping the team communicating and capturing knowledge as the project proceeds.
Where can I find a free PM 340 Week 1 sample paper?
The Week 1 paper above, which follows the project work domain through a museum gallery build in Omaha, can be read in full for free.
What is the project work performance domain?
It is the area of project management concerned with the processes and activities that carry out the work: establishing processes, managing resources and procurement, communicating with the team and learning as the project proceeds.
What is knowledge management in a project?
The practice of capturing and sharing what the team learns, both explicit information such as documents and tacit know-how held by people, so it can improve this project and future ones.
How does procurement fit into the project work domain?
Procurement covers selecting suppliers, forming contracts and then working with suppliers during delivery, including inspections, changes, payments and resolving issues.
Write yours, or have the desk draft it
This paper is an original model document written by our desk, not a submitted student paper and not an official University of Phoenix document. Read it for the moves, then write your own to the instructions in your classroom. If you want one built to your exact prompt and rubric, the first custom sample is free and arrives in 24 to 48 hours.
Request this one custom, free · All PM 340 week samples · All courses