PM 300 Week 3 Governance and Project Environments Example

Who Decides, and What Decides for Them: Governance and the Project Environment for a Duluth Arena Refrigeration Project

[Student Name]

University of Phoenix

PM/300: Project Management Principles and Standards

Week 3 Assignment

[Instructor Name]

[Date]

Northshore Community Arena, its governance structure, thresholds and figures are composites written for a model paper.

The first two papers followed the Northshore Community Arena replacement, an imagined Duluth rink whose R-22 plant is giving way to a low-charge ammonia chiller during a five-month summer shutdown, at a budget of $4.6 million. This paper turns to the structure around the project. It designs a governance framework that fits a public project of this size and risk, analyzes the internal and external environments the project works within and explains how those environments shaped the governance choices.

What Project Governance Means

The current standard treats governance as the framework of roles, decision rights and oversight through which an organization directs and controls a project (Project Management Institute [PMI], 2021). Turner (2006) described governance as the structure through which a project's objectives are set and the means of reaching them and monitoring performance are decided. In practice, governance answers three questions: who may approve money, scope and schedule changes; who checks that the project is on course; and who is accountable to the public when it is not. Project management works inside those limits, directing the team's daily work.

Too and Weaver (2014) proposed that governance should connect the organization's executive layer, which sets strategy and accepts risk, with the management layer, which delivers projects. A city arena project is small compared with a highway program, but the same layers exist: the city council and parks board at the top, the parks director as sponsor and the project manager and team below.

Governance Structure for Northshore

The sponsor is the parks director, who owns the business case and the benefits described in Week 1. A steering group of four people meets every two weeks during construction: the sponsor, the city's facilities manager, a finance analyst and the arena manager. The project manager, Dana Kowalczyk, reports to the steering group and has day-to-day authority over the team.

Decision limits are written into the project charter. Kowalczyk signs off on her own any change costing $25,000 or less and any schedule shift that do not use more than three days of float. Between $25,000 and $100,000 the sponsor signs. Anything larger, any use of more than half the $460,000 contingency and any change that would delay ice making past August 25 goes to the steering group, which escalates to the parks board when a council vote would be needed under the city's purchasing rules.

Three stage gates structure the project. Gate 1, design approval, requires completed drawings, a fire department review and a cost estimate within 10 percent of budget. Gate 2, equipment release, authorizes the chiller order and the start of demolition. Gate 3, handover, requires passing pressure and performance tests, operator training records and a benefits handover note.

Governance that gives a steering group no real authority is decoration, not oversight.

Change Control Path

Every change request begins as a single sheet that states what would change, why, what it costs and how many days it adds or saves. Kowalczyk reviews every request within two working days and decides those within her limit. Larger requests go to the sponsor with a recommendation, and those above the sponsor's limit go to the next steering group meeting or, if urgent, to an emergency call. Every decision is logged with its date, approver and rationale so that the board and auditors can trace how the budget was spent.

Internal Environment

Several internal factors shape the project. The city's culture is cautious with capital spending after a recent cost overrun on a different building, so the steering group expects early warning of problems. Purchasing rules require competitive bids above a set amount and council approval for the largest contracts, which adds weeks to any procurement. The arena's six technicians belong to a union whose agreement sets training hours and overtime rules, which affects the training schedule before handover. City engineering staff are shared across about 30 capital projects, so the project receives fixed hours rather than a dedicated engineer. Finally, the arena has no ammonia experience, which raises both a skill gap and some anxiety among staff.

External Environment

External factors are just as important. Federal process safety rules apply to facilities holding 10,000 pounds or more of anhydrous ammonia; the low-charge design holds far less, but the fire department and neighbors still expect strong safeguards. Duluth's construction season is short, and concrete work over the slabs must be done in warm months. The hockey calendar sets a hard end date, since the youth association's tryouts begin in early September. Chillers of this type have lead times of about 20 weeks. A state energy grant covers part of the heat recovery cost but requires metered savings data for two years. Interest in the arena from local media means delays become public quickly.

Joslin and Müller (2016) studied projects across many countries and industries and reported that the governance context surrounding a project was related to its success, with governance shaping how methods are applied. Their finding supports designing governance in response to the project's own environment rather than copying a standard template.

How the Environment Shaped Governance

Four environmental factors produced specific governance features. The cautious culture led to biweekly steering meetings instead of monthly ones and to a rule that any forecast overrun above 5 percent is reported within two days. The hard season deadline produced the schedule limit in the charter: no one below the steering group can approve a change that pushes ice making past August 25. The ammonia safety expectations created Gate 1's fire department review and Gate 3's training requirement, so the project cannot hand over equipment that staff are not ready to run. The grant's reporting rule placed metering in the project's scope and assigned data collection to operations in the handover note.

Conclusion

Northshore's governance gives clear decision rights to a sponsor, a steering group and a project manager, with written limits, three stage gates and a traceable change path. That structure was not chosen from a template. It responds to a cautious city culture, purchasing rules, union agreements, safety expectations, a short building season, long equipment lead times and grant conditions. Designing governance from the environment outward gives the team room to act quickly within its limits and gives the public confidence that someone is watching the money.

References

Joslin, R., & Müller, R. (2016). The relationship between project governance and project success. International Journal of Project Management, 34(4), 613-626. https://doi.org/10.1016/j.ijproman.2016.01.008

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

Too, E. G., & Weaver, P. (2014). The management of project management: A conceptual framework for project governance. International Journal of Project Management, 32(8), 1382-1394. https://doi.org/10.1016/j.ijproman.2013.07.006

Turner, J. R. (2006). Towards a theory of project management: The nature of the project governance and project management. International Journal of Project Management, 24(2), 93-95. https://doi.org/10.1016/j.ijproman.2005.11.008