Ground Rules

Agreed standards that set how project team members are expected to act and interact with one another.

Key Points

  • Established collaboratively early in the project and endorsed by the whole team.
  • Cover meeting etiquette, communication norms, decision-making, conflict handling, and mutual respect.
  • Documented (often in the team charter) and applied consistently, with clear consequences for violations.
  • Reviewed and updated as the team evolves or new members join.

Example

At project kickoff, the team agrees to start meetings on time, keep laptops closed unless needed, let one person speak at a time, address issues not people, respond to messages within 24 hours, and escalate unresolved conflicts to the project manager. These agreements become the team's ground rules in the team charter.

PMP Example Question

During a startup workshop, the project manager facilitates a session to define how the team will communicate, behave in meetings, and resolve disagreements. What is the team creating?

  1. Resource management plan
  2. Ground rules
  3. Stakeholder engagement plan
  4. RACI matrix

Correct Answer: B — Ground rules

Explanation: Ground rules specify expected conduct within the project team. The other options focus on staffing and roles, external engagement, and responsibility assignments.

AI Systems with Claude, for Scrum Masters and Project Managers

Most AI pilots in project management do not fail on the model. They fail because somebody pointed the thing at a decision instead of at a task. This course is built around that distinction, and around the work that follows once you get it right.

Eight teaching sections, taught against one running project from the first lecture to the last. You watch a system get built, then you build the same one against your own sprint. Nothing here is a demo that works only on the example.

You finish with five working systems and you keep them. The sprint report machine turns your board export and standup notes into the report you currently write by hand. The retro intelligence system tells you what the team keeps saying, not just what it said this time. The stakeholder comms engine drafts the update in the register the audience expects. The backlog health monitor flags the quiet decay nobody has time to check for. The risk and dependency tracker follows the chains that actually bite.

Seventy-six working files ship with it, across four sections, so every system is built against real sprint data rather than material invented for a slide. Four sprints of retrospectives, board exports, standup notes, backlog and risk data.

Explore the Course


Launch your career!

HK School of Management offers training in project management, job-search strategies, and career growth. Practical skills, tools, and guidance you can apply right away. Covered by Udemy's 30-day refund policy.

Learn More