Project Teams Understand Agreed-Upon Governance and Team Agreements
PMBOK v8 Definition
Project teams understand there are agreed-upon processes, protocols, team agreements, or other forms of project governance in tasks in which they are involved. Team agreements represent a set of behavioral parameters and working norms that are established by the project team and upheld through individual and team commitments. These agreements should be created at the beginning of a project to determine the essential norms and practices that facilitate ongoing collaborative success.
Why It Matters for the Exam
This concept appears frequently in PMI exam questions about team dynamics, governance compliance, and project startup activities. Questions test whether you understand that governance is not just organizational policy—it includes team-created agreements that empower collaboration. Expect scenario-based questions where a team is unclear about expectations, and you must identify the missing governance element (team agreements, protocols, or governance integration).
Key Points to Remember (for the exam)
- Governance Awareness: Project teams have awareness of—and act appropriately on—governance structure including policies, standards, procedures, guidelines, internal/external auditing/compliance, and customer governance requirements.
- Governance Integration: Project teams ensure that governance of interactions comes from both organizational and third-party governance and is integrated within project governance.
- Team Agreements Creation: Team agreements are created at the beginning of a project to determine essential norms and practices that facilitate ongoing collaborative success.
- Empowered Culture Foundation: Understanding relationships among components of project tasks and organizational procedures is important for teams to consider when building an empowered culture.
- Governance Instruments: Project teams may check governance using instruments such as compliance audits or checklists against internal or external standards/benchmarks for predictive approaches.
- Signaling Mechanisms: Project teams select and use one or more signaling mechanisms that align most closely to how the project can maximize its value proposition.
- Continuous Improvement: Project governance processes are in place, effective, and continuously improved throughout the project.
Typical PMI Exam Example
A project team is struggling with unclear expectations about meeting behavior and decision-making protocols. The project manager notices team members are unsure who can approve changes and how conflicts should be resolved. What is the MOST LIKELY missing element?
Answer: Team agreements—a set of behavioral parameters and working norms established by the project team and upheld through individual and team commitments, created at the beginning of the project.
PMI Exam Traps
-
Trap: Confusing team agreements with organizational policies
-
Reality: Team agreements are created BY the team for working norms; organizational policies are imposed by the organization for governance
-
Trap: Thinking governance only comes from the organization
-
Reality: Governance of interactions comes from BOTH organizational and third-party governance, integrated within project governance
-
Trap: Assuming governance instruments are only for predictive approaches
-
Reality: Compliance audits and checklists are specifically mentioned for predictive approaches, but governance awareness applies to all approaches
-
Trap: Believing team agreements are optional or can be created later
-
Reality: These agreements should be created at the beginning of a project to determine essential norms and practices
Important PMI Connections
| Related Concept | Relationship Type | Exam Attention Point |
|---|---|---|
| Project Governance Plan | Output of governance process | Documents the framework within which decisions will be made |
| Empowered Culture | Outcome of governance awareness | Understanding relationships among project tasks and procedures builds empowered culture |
| Lessons Learned/Retrospectives | Continuous governance improvement | Lessons learned/retrospectives are managed throughout the project |
| Organizational Process Assets | Input to governance | Governance artifacts include policies, standards, procedures aligned with organizational assets |
| Team Charter | Similar to team agreements | Both establish norms; team agreements focus on behavioral parameters and working norms |
Quick Review Questions
-
When should team agreements be created in a project?
-
What are the three sources of governance that project teams must integrate?
-
What instruments can project teams use to check governance in predictive approaches?
-
What is the relationship between team agreements and empowered culture?
-
How does the project team ensure governance of interactions is properly sourced?
PMBOK v8 Reference
Section 3.8 - Team Agreements and Governance Integration (Referenced passages: Governance structure awareness, team agreements definition, governance instruments, signaling mechanisms, and lessons learned management)