| Course | PJM-5100 Project Management |
|---|---|
| Module | Module 3 |
| Paper type | Written assignment 3: project structure |
| Length | About 822 words, 5 pages |
| Format | APA 7 student paper |
| School | Thomas Edison State University |
| Program | Master of Science in Management |
| Updated | October 2026 |
Free sample paper for PJM 5100 Module 3
Twenty-Nine Weeks to Opening Day: Structuring and Scheduling the Branch Project
Student Name
Master of Science in Management, Thomas Edison State University
PJM-5100: Project Management
Mentor Name
Month Day, Year
Twenty-Nine Weeks to Opening Day: Structuring and Scheduling the Branch Project
Introduction
With a contractor selected, the branch project moves into detailed planning. Gido et al. (2018) describe the structure of a project plan as a sequence: define the scope, break it into a work breakdown structure, assign responsibility for each work item, define activities and their dependencies in a network, estimate durations and calculate the schedule. This assignment applies that sequence to Prairie Hills Credit Union's ninth branch, with week 0 set at March 2 and opening required by September 30, about 30 weeks later.
Work Breakdown Structure
A work breakdown structure splits the project level by level until each element can be estimated and given to one owner. Globerson (1994) showed that the way a structure is organized, by deliverable, by function or by phase, shapes how managers think about the project, and recommended choosing the form that matches how the project will be controlled. Because the credit union will manage the contractor and its own teams by deliverable, the structure is organized that way.
| Level 1 | Level 2 work packages |
|---|---|
| 1. Project management | Plan, status reports, budget control, closeout |
| 2. Site and building | Permits and mobilization; construction to substantial completion |
| 3. Technology and equipment | Teller, vault and ATM equipment order; network and core system setup; installation |
| 4. Staffing | Branch manager recruitment; teller and member service hiring; training |
| 5. Marketing and members | Pre-opening campaign; member notices |
| 6. Opening | System test and mock day; grand opening |
Responsibility Assignment
A responsibility matrix shows who does each work package. The facilities manager is responsible for site and building and coordinates Cedar Ridge Builders; the information technology manager for technology and equipment; the human resources manager for staffing; the marketing manager for marketing; and the project manager, who reports to the chief operating officer as sponsor, for project management, opening and overall integration. Each work package has one responsible person, with others marked as supporting or approving, so no deliverable falls between departments.
Activity Network and Durations
Eleven activities, with durations in weeks from experienced estimates and the contractor's proposal, form the network.
| Activity | Predecessors | Weeks | Earliest start | Earliest finish | Latest start | Total slack |
|---|---|---|---|---|---|---|
| A. Permits and mobilization | None | 2 | 0 | 2 | 0 | 0 |
| B. Construction to substantial completion | A | 22 | 2 | 24 | 2 | 0 |
| C. Order teller, vault and ATM equipment | None | 10 | 0 | 10 | 14 | 14 |
| D. Network and core system design | None | 4 | 0 | 4 | 20 | 20 |
| E. Install equipment and network | B, C, D | 3 | 24 | 27 | 24 | 0 |
| F. Recruit branch manager | None | 6 | 0 | 6 | 9 | 9 |
| G. Hire tellers and member service staff | F | 8 | 6 | 14 | 15 | 9 |
| H. Train staff | G | 4 | 14 | 18 | 23 | 9 |
| I. System test and mock day | E, H | 1 | 27 | 28 | 27 | 0 |
| J. Pre-opening marketing | None | 6 | 0 | 6 | 22 | 22 |
| K. Grand opening | I, J | 1 | 28 | 29 | 28 | 0 |
Schedule Calculations
A forward pass sets each activity's earliest start at the latest earliest finish of its predecessors; the project's earliest finish is week 29. A backward pass from week 29 sets each activity's latest finish at the earliest latest start of its successors, and total slack is the difference between latest and earliest start. The critical path, the longest path with zero slack, runs A, B, E, I, K: permits, construction, installation, testing and opening, 29 weeks in total. Opening at week 29, about September 21, leaves roughly one week of buffer before the September 30 deadline.
Interpreting Slack
Slack shows where the plan can absorb delay. Staffing has nine weeks of slack along the path F, G, H, so recruitment can start later, which would reduce the cost of paying new staff before opening; but the slack is shared along the path, so a late manager hire also delays the tellers. Equipment ordering has 14 weeks of slack, though its long lead time makes an early order prudent. Marketing, with 22 weeks of slack, should be scheduled late on purpose, ending just before opening. Herroelen and Leus (2005), surveying scheduling under uncertainty, note that deterministic schedules like this one assume known durations; building protection into the most uncertain activities, here construction, is wiser than spreading buffers evenly.
Assumptions Behind the Schedule
The schedule rests on stated assumptions: city permits within two weeks, no more than five weather days during construction, equipment lead times as quoted by vendors and the availability of the network engineer, whose other commitments the next assignment examines. If any assumption fails, the project manager will recalculate the network and report the effect on the opening date at the next status meeting.
Conclusion
The work breakdown structure, responsibility matrix and network schedule turn the branch objective into a plan with clear owners and dates. The contractor's construction drives the 29-week critical path, so the project manager's attention belongs there, while staffing and marketing have room to be timed for cost and impact.
References
Gido, J., Clements, J. P., & Baker, R. (2018). Successful project management (7th ed.). Cengage Learning.
Globerson, S. (1994). Impact of various work-breakdown structures on project conceptualization. International Journal of Project Management, 12(3), 165-171. https://doi.org/10.1016/0263-7863(94)90032-9
Herroelen, W., & Leus, R. (2005). Project scheduling under uncertainty: Survey and research potentials. European Journal of Operational Research, 165(2), 289-306. https://doi.org/10.1016/j.ejor.2004.04.002
What the PJM 5100 Module 3 instructions ask for
Module 3's PJM-5100 written assignment covers project structure: scope, work breakdown structure, responsibilities and the network schedule. Build a work breakdown structure for your project and explain how it is organized, assign each work package to one responsible person, then list activities with predecessors and durations. Calculate earliest and latest start and finish times with forward and backward passes, identify total slack and the critical path, and interpret what they mean for managing the project. Present the network data in a table, such as one exported from scheduling software, and support planning choices with the textbook and research. Keep activity names and numbers consistent with your work breakdown structure. Show your passes.
How this PJM 5100 Module 3 example is built
The paper follows the textbook's planning sequence, so each element builds on the one before. The work breakdown structure is justified with research on how structure affects management, and the responsibility section assigns one owner per package. The network table contains everything needed to check the calculations, and a short section explains the forward and backward passes. The interpretation of slack is the most useful part for a manager: it shows where delay is safe, where it is shared along a path and where to place protection. The conclusion directs attention to the critical path, which later assignments will manage. Read it alongside the earlier assignments to see the project develop.
Where the marks sit in the PJM 5100 Module 3 rubric
Mentors grade the third assignment out of 100. They check the work breakdown structure for completeness and logic, the responsibility matrix for single ownership, and the network schedule for correct predecessors, forward and backward passes, slack and critical path. Interpretation of the schedule earns credit beyond the calculations, especially explanations of shared slack and buffers. Tables should be clear and consistent with earlier assignments. Research and APA citations support planning choices. Errors in the critical path calculation, or a work breakdown structure that mixes deliverables and activities without logic, cost the most points. Explaining what the schedule means for decisions, not only computing it, earns the most credit. Clarity helps.
PJM 5100 Module 3 help: mistakes that cost marks
Students often list activities without real dependencies, which makes every path look critical or none. Another frequent error is calculating slack correctly but treating it as free time for each activity on a path, when it is shared. Our writers can prepare PJM 5100 structure and scheduling assignments for your project. Draft the work breakdown structure by deliverable first, then list activities under each with predecessors and durations. Run the forward pass, then the backward pass, and compute slack in a table. Check the critical path by adding its durations, and explain what the slack means for timing decisions. Then confirm that the critical path matches the project finish date exactly.
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 Thomas Edison State University 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.
More PJM 5100 and Master of Science in Management sample papers
- PJM 5100 Module 1: Defining a Branch Opening as a Project
- PJM 5100 Module 2: An RFP and Bid Choice for a Branch
- PJM 5100 Module 4: Leveling, Budgets and a Status Report
- PJM 5100 Module 5: Leading the Branch Project Team
- PJM 5100 Module 6: Communication Plan and Matrix Structure
- MSM 6200 Module 6: Final Project: A Change the Warehouse Should Make, and How to Make It Stick
- MAN 6300 Module 2: Annotated Bibliography Written Assignment
- ORG 5020 Module 3: Five Lenses on Leading an Automation Change
- LCO 6100 Module 4: Final Paper: A Full Change Plan for a Contemporary Insurer
PJM 5100 Module 3 questions, answered
Where can I find a free PJM 5100 Module 3 sample paper?
The third Project Management written assignment is shown above, with a work breakdown structure, responsibility matrix and 11-activity network schedule for a composite credit union branch.
What is a responsibility assignment matrix?
A table showing which person is responsible for, supports or approves each work package, so every deliverable has one owner.
How is total slack calculated?
Latest start minus earliest start for each activity; activities with zero slack form the critical path.
Can every activity on a path use its slack?
No; slack is shared along a path, so using it on one activity reduces it for the activities that follow.
How should a work breakdown structure be organized?
In the way the project will be controlled, often by deliverable, because the structure shapes how managers think about and track the work.