Task 12: Define Team Ground Rules

Every high-performing team operates within a shared behavioral framework — an explicit or implicit set of expectations about how members treat each other, make decisions, communicate, and hold themselves accountable. Task 12 of the ECO People domain formalizes this as a core project management responsibility: define team ground rules. The project manager must communicate organizational principles to the team and stakeholders, establish an environment that encourages adherence, and manage and rectify violations when they occur. Ground rules are not bureaucratic overhead. They are the foundation of psychological safety, predictable collaboration, and team accountability.

This study guide covers all three ECO enablers for Task 12, the relationship between ground rules and team charters, the distinction between organizational principles and team-specific norms, how to handle violations constructively, and the connection to PMBOK 7's principles and performance domains.

ECO Enablers for Task 12

The Exam Content Outline identifies three enablers that describe the project manager's responsibilities for team ground rules:

Communicate organizational principles with the team and external stakeholders. Ground rules don't exist in a vacuum. They must align with the organization's values, code of conduct, ethics policies, and cultural norms. The project manager's first job is to ensure the team understands these organizational principles and how they apply to the project context.
Establish an environment that fosters adherence to the ground rules. Rules without a supportive environment are just words. The project manager must model the behaviors they expect, create psychological safety so team members feel comfortable calling out violations, and integrate ground rules into the team's daily rhythm so they become habits rather than mandates.
Manage and rectify ground rule violations. Violations will happen — ground rules are tested under pressure, during conflict, and when deadlines loom. The project manager must address violations promptly, fairly, and constructively, treating them as opportunities to reinforce the standard rather than occasions for punishment.

These enablers are deeply connected to PMBOK 7's Stewardship principle. Stewardship requires project managers to act with integrity, care, and trustworthiness — the same qualities that ground rules are designed to embed in team behavior. They also connect to the Team performance domain, which emphasizes shared ownership and a safe, respectful working environment. The Agile Practice Guide reinforces this through the concept of team working agreements in agile contexts, which serve the same function as ground rules but are typically created collaboratively by the team rather than handed down by management.

📝 PMP Exam Tip: Ground Rules Are Co-Created, Not Imposed

The PMP exam consistently rewards answer choices where the project manager facilitates the team in creating their own ground rules and penalizes choices where the project manager dictates rules unilaterally. PMI's philosophy — grounded in servant leadership, Theory Y, and agile values — holds that teams who co-create their behavioral standards are far more likely to adhere to them. When you see answer choices involving "the project manager publishes a list of rules" or "the project manager tells the team what is expected," eliminate them. The correct answer almost always involves facilitated discussion, collaborative agreement, or team charter development.

Communicating Organizational Principles

The first enabler requires the project manager to bridge the gap between organizational-level principles and project-level ground rules. Organizational principles include the company's code of conduct, ethics policies, diversity and inclusion commitments, communication standards, and any regulatory or compliance requirements that govern behavior. The project manager must ensure the team understands these principles not as abstract corporate statements but as concrete expectations for how the project operates.

Effective communication of organizational principles involves:

Translation, not repetition. Don't just forward the corporate code of conduct PDF. Translate organizational principles into project-specific examples: "Our organization's commitment to respectful communication means that in our daily standups, we listen without interrupting and assume good intent when someone challenges our ideas."
Contextualization for external stakeholders. Vendors, contractors, and client representatives may not share your organization's principles. The project manager must explicitly communicate which organizational standards apply to external parties and how they will be upheld in cross-organizational interactions.
Integration with the team charter. The team charter — a document that establishes team values, agreements, and operating guidelines — is the natural home for ground rules. Organizational principles provide the floor (minimum standards), while the team's own agreements provide additional specificity and commitment.
Reinforcement through onboarding. New team members who join mid-project must receive the same grounding in organizational principles and team ground rules as the original team. A common exam scenario involves a new team member violating an unwritten norm — the correct answer is to ensure proper onboarding, not to discipline.

Establishing an Environment of Adherence

The second enabler shifts from communication to culture. Communicating ground rules is necessary but insufficient; the environment must actively support adherence. This is where the project manager's leadership, facilitation, and emotional intelligence skills are most critical.

Environmental Factor	What It Looks Like in Practice	PM Behaviors That Foster It	Exam Scenario Cues
Modeling	The project manager consistently demonstrates the ground rules in their own behavior. If the rule is "no interruptions during standups," the PM never interrupts. If the rule is "decisions are made transparently," the PM never makes back-channel decisions.	Self-awareness about own behavior; publicly acknowledging and correcting own mistakes; never asking the team to follow rules the PM doesn't follow	"The project manager realized they had violated the team's communication agreement and apologized during the next retrospective"
Psychological Safety	Team members feel safe raising concerns about ground rule violations without fear of retaliation. Junior members can challenge senior members on behavioral standards. Silence is not mistaken for agreement.	Thanking team members who raise concerns; never punishing or marginalizing those who speak up; addressing violations consistently regardless of the violator's seniority	"A junior developer pointed out that a senior architect had interrupted during a review — the project manager acknowledged and addressed it"
Routine Integration	Ground rules are referenced in meetings, retrospectives, and decision-making processes. They are not a document that gets created and forgotten. The team revisits them periodically to confirm they're still relevant.	Opening kickoff meetings with ground rule review; including "how well did we follow our ground rules?" as a retrospective question; posting ground rules visibly (physical or digital team space)	"During sprint planning, the Scrum Master reminded the team of their working agreement about decision-making thresholds"
Accountability Without Punishment	When violations occur, the response is corrective and educational, not punitive. The goal is to restore the standard and strengthen the team's commitment, not to assign blame or impose consequences.	Addressing violations privately first (unless public acknowledgment is appropriate); focusing on the behavior, not the person; asking "what made it hard to follow the ground rule in that situation?" before prescribing a fix	"Rather than reprimanding the team member, the project manager asked what circumstances had made it difficult to meet the response-time expectation"

A critical insight for the exam: the environment of adherence is built primarily through consistency. When the project manager enforces ground rules selectively — cracking down on a junior team member's violation while overlooking a senior stakeholder's — the environment collapses. The PMP exam will test whether you recognize the importance of equitable enforcement and whether you choose answers that treat all team members and stakeholders consistently.

Managing and Rectifying Ground Rule Violations

The third enabler addresses what happens when ground rules break down. PMI's framework treats violations not as moral failures to be punished but as gaps to be understood and closed. The project manager's response should follow a deliberate sequence that prioritizes understanding and restoration over discipline.

⚠️ Exam Trap: Escalation Is a Last Resort, Not a First Response

The PMP exam will occasionally offer "escalate to the functional manager" or "report the violation to HR" as answer choices for ground rule violation scenarios. These are almost always wrong as a first response. PMI expects the project manager to address violations directly within the team first — through private conversation, facilitated discussion, or team retrospective — before involving external authority. Escalation may become appropriate for serious ethical violations, harassment, or repeated patterns that resist direct intervention, but the exam will make those scenarios unmistakably severe. For typical ground rule violations (missed meetings, interrupting, dismissive communication), the correct answer involves direct, constructive engagement by the project manager.

The recommended sequence for managing ground rule violations:

Observe and confirm. Is this actually a violation, or a misunderstanding? Gather facts before acting. Ask clarifying questions. What appears to be a missed deadline may actually be a communication breakdown about the deadline itself.
Address privately and constructively. For first-time or minor violations, a private conversation is almost always the correct first step. Use "I noticed" language rather than accusatory language. Focus on the impact, not the intent: "I noticed the meeting started 15 minutes late on Tuesday — this affected the team's ability to cover the full agenda. Can we talk about what happened?"
Explore root causes. Violations often signal deeper issues. A team member who consistently misses deadlines may be overloaded. A stakeholder who bypasses the change control process may not understand why it exists. Address the cause, not just the symptom.
Reaffirm the ground rule and the rationale. Remind the team member why the ground rule exists — not "because I said so" but because it serves the team's effectiveness. People adhere to rules they understand and believe in.
Agree on a path forward. What will the team member do differently? What support do they need? Document the agreement informally — not as a punitive record, but as a shared understanding of the expectation going forward.
Escalate if necessary. If the behavior persists despite direct engagement, if it involves ethical violations or harassment, or if it significantly damages team morale and productivity, escalation to the appropriate authority (functional manager, sponsor, HR) becomes appropriate. But this is the exception, not the rule.

Ground Rules Across Project Environments

Ground rules are not one-size-fits-all. The content and enforcement approach must be tailored to the project's methodology, team composition, and organizational context:

Predictive (Waterfall) projects: Ground rules tend to be more formal and documented, often part of the project management plan or team charter. They may address meeting protocols, decision authority, escalation paths, and deliverable acceptance criteria. Enforcement is typically through the project manager's formal authority within the governance structure.
Agile projects: Ground rules take the form of team working agreements, created collaboratively by the team during sprint zero or the project kickoff. They often cover standup protocols (timebox, who speaks), definition of done, how the team handles interruptions during a sprint, and retrospective norms (Vegas rule, no blame). The Scrum Master or agile project manager facilitates adherence but the team owns enforcement.
Hybrid projects: May have different ground rules for different workstreams or team segments. The project manager must ensure that rules are coherent across the project — a predictive governance team and an agile development team need compatible, not contradictory, behavioral standards.
Virtual and distributed teams: Ground rules for virtual teams must explicitly address digital communication norms: response time expectations, camera policies during video calls, use of chat during meetings, respect for time zone boundaries, and expectations for asynchronous vs. synchronous availability. These connect directly to Task 11: Support Virtual Teams.

Key Terms and Concepts for the Exam

Team Charter: A document that establishes the team's values, agreements, and operating guidelines. It is collaboratively developed by the team and the project manager, not imposed by management. Includes ground rules, communication protocols, decision-making processes, and conflict resolution approaches. The PMP exam will test whether you know the team charter is created at or near project initiation.
Working Agreement: The agile equivalent of ground rules. A set of behavioral expectations created and maintained by the team. Often posted visibly in the team's physical or digital workspace. Agile teams revisit working agreements during retrospectives.
Code of Conduct: Organizational-level standards of behavior, typically more formal and broadly applicable than project-level ground rules. The project manager must ensure the team's ground rules are consistent with the organizational code of conduct.
Constructive Feedback: Feedback focused on behavior and impact, not personality or intent. Describes what was observed, explains the effect, and invites collaboration on a solution. The preferred tool for addressing ground rule violations.
Norms: Informal, often unspoken behavioral expectations that emerge naturally in teams. Ground rules make norms explicit and agreed-upon, reducing the risk that team members operate under conflicting assumptions about what's acceptable.

Study Checklist for Task 12

✅ Can you distinguish between organizational principles (the floor) and team-specific ground rules (additional agreements the team makes)?
✅ Do you understand that ground rules should be co-created with the team, not imposed unilaterally by the project manager?
✅ Can you identify the four environmental factors that foster adherence — modeling, psychological safety, routine integration, and accountability without punishment?
✅ Do you know the correct sequence for addressing ground rule violations: observe → private conversation → explore root cause → reaffirm → agree on path forward → escalate only if necessary?
✅ Can you recognize exam traps that suggest escalation, punishment, or unilateral rule-making as first responses to ground rule scenarios?
✅ Do you understand how ground rules adapt across predictive (team charter), agile (working agreement), hybrid, and virtual environments?

Ground rules are the invisible scaffolding that holds team culture together. They connect directly to conflict management (Task 1) — because well-established ground rules prevent many conflicts from arising — and to building shared understanding (Task 10) — because ground rules create the safe container within which honest alignment can occur. Continue to Task 13: Mentor Stakeholders to learn how the project manager develops others beyond the immediate team, or review Task 11: Support Virtual Teams to explore how ground rules must adapt for distributed environments.

← Back to ECO Study Guide Index | Practice People Domain Questions →