What it means
Project team ground rules are explicit agreements about behavior, communication, decision-making, conflict, accountability, focus, and respectful collaboration.
Why it matters
Shared rules reduce ambiguity and give the team a neutral reference when pressure or disagreement makes informal expectations unreliable.
Practical focus
- Create the rules collaboratively and make them observable rather than aspirational.
- Cover decision methods, meeting behavior, response expectations, disagreement, confidentiality, and accountability.
- Review the agreement after team changes, recurring friction, or major delivery shifts.
- Retain the approved definitions, assumptions, decisions, ownership, exceptions, measures, and change history that demonstrate how Project Team Ground Rules operates in real project work.
- Exercise this failure scenario: The team claims to value collaboration but has no agreement for handling disagreement, so difficult decisions are delayed or settled by authority alone.
Common mistakes
- Using Project Team Ground Rules as a label without defining its scope, owner, decision criteria, and expected evidence.
- Treating a template, meeting, tool screen, or status report as proof that Project Team Ground Rules works consistently in normal delivery.
- Optimizing a single activity while ignoring dependencies, incentives, risk transfer, and the end-to-end outcome.
- Testing only the expected path and never rehearsing this failure condition: The team claims to value collaboration but has no agreement for handling disagreement, so difficult decisions are delayed or settled by authority alone.
Certification relevance
This subject appears in or supports the following certification bodies of knowledge: