Project Governance and Compliance
PMP PMP · Business Environment
Why governance moved to the center of the exam
In the July 2026 ECO, Business Environment grew from 8% to 26% of the exam, and governance is one of the reasons. The domain now has eight tasks, and two of them open this guide: define and establish project governance, and plan and manage project compliance. Governance is the framework of rules, roles, and decision-making processes that controls how a project is run: who decides what, how decisions are made and recorded, how the project is overseen, and how it stays aligned with the organization's strategy. Compliance is the project's obligation to follow the laws, regulations, standards, and organizational policies that apply to it. Together, they are the project's license to operate — and the exam now tests them as a core competence, not a side topic.
Governance is often confused with management, and the exam tests the distinction. Management is about doing the work: planning, executing, and controlling the project. Governance is about deciding and overseeing: setting the direction, defining who has authority to make which decisions, and monitoring whether the project is delivering what the organization needs. The project manager manages the project; the governance body — typically a steering committee, a project board, or a sponsor — governs it. The project manager's job is to define and establish the governance framework (with the sponsor) and then to operate within it, escalating decisions that belong at the governance level rather than making them alone.
Defining the governance framework
A governance framework answers a set of practical questions. Who approves the project charter and the project management plan? Who approves changes above a certain size or cost? Who decides whether the project continues, changes, or stops at a phase gate? How are risks above a certain threshold escalated? How often does the governance body meet, and what information does it need? The answers are recorded in the governance plan (or in the project management plan's governance section) and agreed with the sponsor at the start of the project. The exam tests this through scenarios where a decision is needed and it is unclear who should make it — the correct response is to check the governance framework and route the decision to the right level, not to decide alone or to escalate everything.
Phase gates (also called stage gates, kill points, or decision gates) are a key governance mechanism. At the end of each phase, the governance body reviews the project's performance and the business case, and decides whether to continue to the next phase, to continue with changes, or to stop the project. The exam expects you to know that a phase gate is a governance decision point, not a project manager decision — and that stopping a project at a gate is a legitimate outcome, not a failure. A project whose business case no longer holds should be stopped at the gate, not pushed through because of sunk costs.
Governance in agile and hybrid projects
Governance looks different in agile projects, but it does not disappear. Instead of phase gates and heavy documentation, agile governance uses frequent reviews, transparent information radiators, and empowered teams operating within clear guardrails. The governance body still sets the direction and the constraints (budget, timeline, compliance requirements), but the team decides how to do the work within those constraints. The exam tests this balance: an option that imposes predictive-style gate reviews on an agile team is usually wrong, and an option that removes all governance from an agile project is also wrong. The right answer is governance that fits the approach — lightweight, frequent, and transparent for agile; structured and documented for predictive; a deliberate blend for hybrid.
The project management office (PMO) is part of the governance picture. A supportive PMO provides templates, best practices, and coaching. A controlling PMO requires compliance with specific methods and standards. A directive PMO directly manages projects. The exam tests these types by scenario: a question describing a PMO that requires all projects to use the same methodology is describing a controlling PMO; a question describing a PMO that runs projects itself is describing a directive PMO. The project manager needs to know which type they are working with, because it determines how much freedom they have and what they must comply with.
Compliance: following the rules that apply
Compliance means ensuring the project follows all applicable laws, regulations, standards, contracts, and organizational policies. This can include data protection laws (such as GDPR for projects handling personal data), health and safety regulations, financial reporting rules, environmental standards, industry-specific regulations (such as pharmaceutical or aviation rules), and the organization's own policies on procurement, security, and ethics. The project manager's job is to identify which rules apply, build compliance into the project plan, monitor compliance during execution, and take corrective action when gaps appear.
The exam tests compliance through scenarios where following the rules conflicts with schedule or cost pressure. The correct answer is always to comply: a project manager who skips a required safety check to save time, or who ignores a data protection requirement to meet a deadline, is failing at a core responsibility. Compliance is not optional, and it is not something the project manager can trade away for speed. A question might describe a team member who suggests skipping a regulatory approval step — the project manager must refuse, explain why, and find a legitimate way to meet the schedule. Another common scenario is a regulation that changes during the project: the project manager must assess the impact of the change, update the plan, and process any resulting changes through change control.
Ethics and professional responsibility
Compliance overlaps with ethics, and the exam tests PMI's Code of Ethics and Professional Conduct through situational questions. The code has four values: responsibility (owning your decisions and their consequences), respect (treating others with dignity), fairness (being impartial and transparent), and honesty (telling the truth and acting with integrity). Exam scenarios include conflicts of interest (a project manager whose family member owns a bidding company must disclose the conflict and remove themselves from the selection), gifts from sellers (which must be declined or disclosed according to policy), and pressure to falsify reports (which must be refused). The correct answer in every ethics scenario is the one that is transparent, honest, and in the best interest of the project and the organization — never the one that hides a problem or benefits the project manager personally.
Confidentiality is part of the same picture. Project information — especially commercially sensitive or personal data — must be protected and shared only with those who need it. A question describing a project manager who shares a colleague's salary information, or who discusses a confidential bid with a seller, is testing whether you recognize the breach and know the correct response: stop the disclosure, report it if required, and reinforce the rules.
Exam mindset for governance and compliance
For governance questions, the pattern is: define the framework early, route decisions to the right level, and respect the gates. The project manager does not make governance-level decisions alone, and does not skip governance to save time. For compliance questions, the pattern is simpler still: follow the rules, always. No schedule pressure, no cost pressure, and no stakeholder request justifies breaking a law, a regulation, or an organizational policy. And for ethics questions, the answer is transparency: disclose conflicts, refuse improper gifts, tell the truth, and protect confidential information.
Exam traps to watch for
- Making a governance-level decision alone. Decisions about continuing, stopping, or fundamentally changing a project belong to the governance body, not the project manager.
- Treating compliance as negotiable under schedule pressure. Laws, regulations, and safety requirements cannot be traded away for speed.
- Confusing PMO types: supportive (templates and coaching), controlling (required compliance with methods), directive (directly manages projects).
- Hiding a conflict of interest. The correct response is always to disclose it and remove yourself from the affected decision.
Practice questions
Test yourself on this guide. Answers are checked instantly, with a full explanation for each question.
Q1.A project is approaching a phase gate. The business case has weakened significantly since the project started, but the team has already spent 60% of the budget. What should happen at the gate?
Explanation: A phase gate is a governance decision point: the governance body reviews the project's performance and the current business case and decides whether to continue, continue with changes, or stop. Money already spent is a sunk cost — it should not drive the decision. What matters is whether the project will still deliver value from this point forward. Option C is wrong because it commits the sunk-cost fallacy: spending more on a project whose business case has failed wastes more money, not less. Option B is wrong because the continue/stop decision belongs to the governance body, not the project manager. Option A is wrong because skipping the gate removes the very oversight that exists to catch this situation.
Exam objective: PMP ECO Task: Define and establish project governance (Business Environment)
Q2.A team member suggests skipping a required safety inspection to recover two days on the schedule. The inspection is mandated by regulation. What should the project manager do?
Explanation: Compliance with a regulatory safety requirement is not negotiable and cannot be traded for schedule. The project manager must refuse, explain why — safety regulations exist to protect people, and breaching them exposes the organization to legal liability and people to harm — and then work on legitimate schedule recovery options such as fast tracking or crashing. Option B is wrong because it breaks the law and endangers people. Option C is wrong because documenting a bad decision does not make it acceptable. Option A is wrong because compliance is not a democratic decision — the team cannot vote to break a regulation.
Exam objective: PMP ECO Task: Plan and manage project compliance (Business Environment)
Q3.A project manager discovers that their brother-in-law's company is one of the bidders for a major project contract. What should the project manager do?
Explanation: PMI's Code of Ethics requires transparency about conflicts of interest. The project manager must disclose the relationship and remove themselves from the selection decision, so that the decision is made — and is seen to be made — impartially. Option D is wrong because an undisclosed conflict, even if the project manager believes they can be impartial, undermines trust and violates the code. Option B is wrong because recommending a family member's company is favoritism, not good judgment. Option C is wrong because the brother-in-law's company should be judged on its merits by people without a conflict — disqualifying it without cause is also unfair.
Exam objective: PMP ECO Task: Plan and manage project compliance (Business Environment)
Q4.An organization's PMO requires all projects to use the same project management methodology, templates, and reporting formats, and audits projects for compliance. What type of PMO is this?
Explanation: A controlling PMO requires compliance with specific methodologies, templates, and standards, and checks that projects follow them. Option C is wrong because a supportive PMO provides templates, best practices, and coaching but does not require compliance — it helps rather than enforces. Option B is wrong because a directive PMO directly manages projects itself, taking over the project management role. Option A is not one of PMI's three PMO types.
Exam objective: PMP ECO Task: Define and establish project governance (Business Environment)
Q5.A new data protection regulation takes effect during a project, requiring changes to how the project handles customer data. What should the project manager do FIRST?
Explanation: The PMI reasoning chain is: assess the impact, then act through the proper process. The project manager must understand what the new regulation requires, how it affects the project's scope, schedule, and cost, and then update the plan and process any changes through change control. Option A is wrong because ignoring a regulation in force is a compliance breach. Option C is wrong because a regulatory change is a problem to manage, not an automatic reason to stop the project — stopping is a governance decision, not a first response. Option D is wrong because compliance cannot be transferred to the customer by asking them to accept the risk; the organization remains responsible for following the law.
Exam objective: PMP ECO Task: Plan and manage project compliance (Business Environment)
Q6.A seller offers the project manager an expensive gift during the contract negotiation. What should the project manager do?
Explanation: Accepting an expensive gift from a seller during negotiations creates an appearance of improper influence and violates PMI's Code of Ethics (fairness and honesty). The project manager should decline the gift, or if organizational policy allows small gifts, disclose it according to policy. Option B is wrong because politeness does not justify accepting something that compromises impartiality. Option C is wrong because secrecy makes the problem worse — an undisclosed gift is exactly what the ethics rules exist to prevent. Option A is wrong because sharing the gift with the team does not remove the improper influence; it spreads it.
Exam objective: PMP ECO Task: Plan and manage project compliance (Business Environment)
Q7.An agile project is being governed with heavy phase-gate reviews, detailed monthly reports, and formal change boards. The team says the governance is slowing them down. What should the project manager recommend?
Explanation: Governance must fit the delivery approach. For an agile project, the right governance is lightweight, frequent, and transparent: the governance body sets direction and constraints (budget, timeline, compliance), and the team decides how to work within those guardrails, with progress visible through reviews and information radiators. Option A is wrong because removing all governance leaves the project without oversight or accountability. Option C is wrong because governance is not one-size-fits-all — imposing predictive governance on an agile team creates exactly the friction described. Option B is wrong because changing the delivery approach to fit the governance gets the relationship backwards; governance should serve the project, not the other way around.
Exam objective: PMP ECO Task: Define and establish project governance (Business Environment)
Q8.A project manager is setting up governance for a new project. Which element is MOST important to define at the start?
Explanation: Governance is fundamentally about decision rights and oversight: who decides what, how decisions are escalated when they exceed the project manager's authority, and how the governance body monitors the project. Defining this at the start prevents the confusion and conflict that arise when a major decision is needed and nobody knows who should make it. Option A is a communications detail, not governance. Option D is a tool choice, not governance. Option B is an administrative detail, not governance.
Exam objective: PMP ECO Task: Define and establish project governance (Business Environment)