Collaboration

Effective collaboration is the foundation of high-performing teams. This section covers practices for working together effectively, whether co-located or distributed.

Pair Programming

What is Pair Programming?

Two developers working together at one workstation:

• Driver: Types the code
• Navigator: Reviews, thinks ahead, catches errors

Roles switch frequently (every 15-30 minutes).

Benefits

When to Pair

Good for:

• Complex or high-risk code
• Onboarding new team members
• Learning new technologies
• Debugging difficult issues
• Knowledge transfer

Less suitable for:

• Simple, routine tasks
• Individual research/exploration
• When both developers are unfamiliar with the domain

Pairing Styles

Driver-Navigator

• Driver writes code
• Navigator reviews and guides
• Switch every 15-30 minutes

Ping-Pong (with TDD)

• Developer A writes a failing test
• Developer B makes it pass
• Developer B writes next failing test
• Developer A makes it pass

Strong-Style

• Navigator has the idea
• Driver only types what navigator says
• Forces clear communication

Remote Pairing Tools

• VS Code Live Share
• JetBrains Code With Me
• Tuple
• Screen sharing + voice

Pairing Tips

• Take breaks (pairing is intense)
• Communicate constantly
• Be patient and kind
• Switch roles regularly
• Both should be engaged

Mob Programming

What is Mob Programming?

The whole team works on the same thing, at the same time, at the same computer.

• One driver at the keyboard
• Multiple navigators guiding
• Rotate driver every 10-15 minutes

When to Use

• Complex problems needing diverse expertise
• Team learning sessions
• Critical code requiring whole-team ownership
• Breaking down silos

Virtual Collaboration

Challenges of Remote Work

• Reduced spontaneous communication
• Time zone differences
• Isolation and disconnection
• Harder to read body language
• Meeting fatigue

Best Practices

Communication

• Over-communicate (err on the side of more)
• Default to async when possible
• Use video for important discussions
• Document decisions in writing

Meetings

• Cameras on when feasible
• Use collaborative tools (Miro, Mural)
• Record for absent team members
• Respect time zones

Connection

• Schedule informal time (virtual coffee)
• Celebrate wins publicly
• Check in on well-being
• Meet in person when possible

Async Communication

When to Use Async

• Status updates
• Non-urgent questions
• FYI information
• Documentation

When to Use Sync

• Urgent issues
• Complex discussions
• Conflict resolution
• Brainstorming

Async Best Practices

• Write clearly and completely
• Provide context
• Specify response expectations
• Use threads to organize

Time Zone Management

Knowledge Sharing

Why It Matters

• Reduces bus factor
• Accelerates onboarding
• Improves code quality
• Builds team capability

Practices

Documentation

• Architecture Decision Records (ADRs)
• Runbooks and playbooks
• Code comments for "why"
• README files

Presentations

• Tech talks
• Show and tell
• Lunch and learns
• Conference debriefs

Code Practices

• Pair programming
• Code reviews with explanations
• Mob programming sessions
• Coding dojos

Mentoring

• Buddy system for new hires
• Office hours
• 1:1 coaching
• Shadowing

Documentation Standards

Every repo should have:

README.md           # Project overview, setup, usage
CONTRIBUTING.md     # How to contribute
docs/
  architecture.md   # System design
  decisions/        # ADRs
  runbooks/         # Operational guides

Tech Talks

Format

• 15-30 minutes presentation
• 10-15 minutes Q&A
• Record for future reference

Topics

• New technologies learned
• Project deep dives
• Industry trends
• Lessons from failures

Building Team Trust

Psychological Safety

Team members feel safe to:

• Ask questions
• Admit mistakes
• Propose ideas
• Challenge decisions

Building Safety

Trust Behaviors

• Follow through on commitments
• Communicate proactively
• Give credit generously
• Accept feedback gracefully

Conflict Resolution

Healthy Conflict

• Debate ideas, not people
• Focus on shared goals
• Listen to understand
• Disagree and commit

Resolution Process

1. Address early - Don't let issues fester
2. Listen first - Understand all perspectives
3. Find common ground - What do you agree on?
4. Brainstorm solutions - Generate options together
5. Decide and commit - Move forward as a team
6. Follow up - Check that resolution holds

When to Escalate

• Safety concerns
• Repeated conflicts
• Power imbalances
• Policy violations

Collaboration Tools

Communication

Collaboration

Project Management

Team Health Metrics

What to Measure

• Sprint velocity (stability over time)
• Cycle time (time to complete work)
• Team satisfaction (surveys)
• Collaboration frequency (pairing, reviews)

Team Health Check

Regular assessment of:

• Mission clarity
• Psychological safety
• Sustainable pace
• Learning culture
• Fun factor

Related Resources

• Team Agreements
• Code Reviews
• Microsoft Playbook: Collaboration

Compliance

This section fulfills ISO 13485 requirements for internal communication (5.5.3), competence and training (6.2), and infrastructure management (6.3), and ISO 27001 requirements for information transfer (A.5.14), remote working security (A.6.7), and information security awareness (A.6.3).

View full compliance matrix