Team Working Agreements

R&D Operating Model — Created by the team, for the team. Revisit each quarter.




Agreements Confirmed: 0 / 0
0%

Communication

How the team communicates day-to-day.

Core Working Hours
to Timezone:
Primary Communication Channel
Response Time Expectations
Urgent Escalation Path
Camera On/Off Policy for Meetings
Meeting-Free Blocks

Sprint Ceremonies

When and how the team runs its Scrum ceremonies.

CeremonyDay / TimeDurationFacilitator
Sprint Planning
Daily Stand-Up
Backlog Grooming
Sprint Demo / Review
Sprint Retrospective

Code & Quality

Standards for code reviews, testing, and engineering practices.

Minimum PR Reviewers
All code changes require a PR with at least reviewer(s)
PR Review Turnaround Time
Branch Naming Convention
Commit Message Format
Unit Test Coverage Expectation
All Automated Tests Must Pass Before Merge
Code Style / Linting Enforcement

JIRA & Work Management

How the team manages work in JIRA.

Stories must be groomed and estimated before pulling into sprint
JIRA Status Update Frequency
Maximum Story Size
Stories should be no larger than story points
Log blockers in stand-up AND in JIRA
FixVersion is set during Sprint Planning for committed items

Collaboration

How the team works together, shares knowledge, and handles disruptions.

Pair Programming Expectations
Knowledge Sharing
On-Call / Support Rotation
Handling Interruptions & Unplanned Work
Spike Timebox

Conflict Resolution

How the team resolves disagreements and ensures accountability.

Disagreements are discussed openly and resolved within the team first
Escalation Path
Retrospective action items are tracked and reviewed each sprint

Team Signatures

By agreeing to these norms, we commit to holding each other accountable.

NameRoleDate