PM 360 Week 5 Selecting Tools Across Domains Example

A Smaller Toolkit for the Second Site: Selecting Models, Methods and Artifacts Across the Performance Domains

[Student Name]

University of Phoenix

PM/360: Models, Methods, and Artifacts

Week 5 Assignment

[Instructor Name]

[Date]

Valley Harvest Food Bank, its Visalia project and every figure are composites written for a model paper.

The imaginary Valley Harvest Food Bank finished moving into its new distribution center last spring. Its next project is a satellite site in Visalia, about 45 miles south, to serve 40 rural pantries that now wait for weekly truck deliveries. The satellite will occupy a 9,000-square-foot leased building with one walk-in cooler, a small dry storage area, two dock doors and a staff of six supported by about 150 volunteers a month. The project manager, Inés Carrillo, has five months and a budget of $640,000. This paper selects a toolkit of models, methods and artifacts across the eight performance domains and explains how it was tailored.

How the Satellite Differs

The current standard asks teams to tailor their approach to the project's context, considering factors such as size, criticality, complexity and the experience of the team (Project Management Institute [PMI], 2021). Compared with the first move, the satellite is smaller in scale and budget, uses the same warehouse system already configured, has fewer stakeholders and less schedule pressure but carries a new kind of risk: a leased building whose landlord controls some repairs. Shenhar (2001) studied more than a hundred projects and argued that project management should differ by project type, especially by technological uncertainty and system scope, and that one style does not fit all. The satellite is a lower-uncertainty, smaller-scope project than the first move, and its toolkit should be lighter.

Stakeholders

Tool: a stakeholder register using power, legitimacy and urgency, kept on one page. The main stakeholders are the 40 rural pantries, the landlord, the county health department, Visalia volunteers and the Fresno warehouse team, whose routes will change. The salience view worked well in the first move and costs little to repeat. Engagement is planned per group, with pantry visits as the main method.

Team

Tool: a short team charter and the situational leadership model. Four of the six satellite staff are new hires; two transfer from Fresno. The charter, written at the first meeting, sets working agreements across two sites. Situational leadership guides how Carrillo directs the new hires and delegates to the transfers, as it did with warehouse leads in the first move.

Development Approach and Life Cycle

Tool: a predictive life cycle with three gates: lease signed and permits issued, building ready and staff trained, first pantry deliveries. The work is well understood and there is no new software, so the iterative board used for system configuration in the first move is not needed.

Planning

Tools: a breakdown of the work, a milestone schedule with dependencies and three-point estimates for the two uncertain tasks, landlord repairs to the cooler and county permit approval. Bottom-up estimates cover the stock transfer, reusing the per-load figures from the first move. A full resource-leveled schedule is not needed for a team of six.

The first move needed a heavy toolkit because it was a big, unfamiliar project; the satellite is neither.

Project Work

Tools: a single combined log for issues and changes, kept by the site supervisor and reviewed at the weekly call, a weekly 30-minute coordination call with the landlord and contractor and the lessons register from the first move. Combining issue and change logs suits the smaller volume expected. The responsibility chart for cold-chain steps is reused without change.

Delivery

Tools: acceptance criteria for the building and cooler, including temperature mapping before any food is stored and a health department inspection, plus a readiness checklist before go-live. The checklist is new, drawn from the first move's lesson that operations were not fully ready for scanner problems. It covers staffing, cooler scanner tests, printed backup pick lists and pantry ordering instructions.

Measurement

Tools: five measures on a one-page dashboard: milestones met, budget against plan, readiness checklist completion and, after opening, order line accuracy and on-time deliveries to the 40 pantries. Wells (2012) studied practitioners' experiences of project management methodologies and found that their benefits were seen more clearly when the methodology supported the project's actual work, while heavy methodologies used for compliance were seen as burdensome. A short dashboard supports decisions without adding a reporting burden.

Uncertainty

Tools: a risk register limited to the top ten risks, reviewed every two weeks, and the five-belief readiness questions from the first move's change work for the Fresno staff whose routes change. The new risk category, landlord control of repairs, gets a specific response: a lease clause requiring the landlord to complete cooler repairs before occupancy, with a rent credit if delayed.

What Was Dropped and What Was Added

Compared with the first move, the satellite drops the iterative configuration board, separate issue and change logs, the full resource-leveled schedule and the eight-measure dashboard. It adds a readiness checklist and a cooler scanner test, both from lessons learned. Several tools serve more than one domain: the dashboard supports measurement and stakeholder updates; the risk register supports planning and uncertainty.

How the Tools Fit Together

The toolkit works as a chain rather than a pile. The stakeholder register tells Carrillo which pantries to visit first, and those visits feed the acceptance criteria for delivery days and ordering instructions. Three-point estimates for the cooler repairs set the buffer in the milestone schedule, and the same uncertainty appears as the top entry in the risk register, with the lease clause as its response. The readiness checklist pulls from both the risk register and the lessons register, and its completion rate is one of the five dashboard measures the executive director sees each week.

Revisiting the Toolkit

At each gate, Carrillo will ask one question of every tool: did anyone use it to make a decision in the last phase? Tools no one used will be dropped or simplified; problems that no tool caught will prompt a new one.

Conclusion

Tailoring the toolkit for the Visalia satellite meant starting from how the project differs from the first move and then choosing one or two tools per domain, keeping what worked, trimming what the smaller project does not need and adding what lessons learned recommended. The result is a lighter set of models, methods and artifacts, each with a reason, and a simple rule for keeping the toolkit honest as the project proceeds.

References

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

Shenhar, A. J. (2001). One size does not fit all projects: Exploring classical contingency domains. Management Science, 47(3), 394-414. https://doi.org/10.1287/mnsc.47.3.394.9772

Wells, H. (2012). How effective are project management methodologies? An explorative evaluation of their benefits in practice. Project Management Journal, 43(6), 43-58. https://doi.org/10.1002/pmj.21302