Guidelines

These patterns and guidelines were created as part of a study undertaken by Dr Mark Zarb, by analysing hours of expert pair programming communication. The primary aim is to help novice pair programmers achieve better communication within their pair.

Each node in the diagrams below represents a different communication state that the pair can be in, with the arrows representing different transitions. Each pattern is made up of the most common transitions observed among expert pairs across certain states. By clicking each diagram, you will be provided with relevant guidelines: this is what we are teaching our novice pairs.

Your feedback is very important – feel free to circulate this website.

A quick ‘cheat-sheet’ that you can easily refer to can be downloaded here.


Planning

Planning

 

When to Use: “We need to review legacy code, or start to plot future steps.”

Restarting

Restarting

 

When to Use: “We’re stuck, and can’t seem to make any good progress.”

Action

Action

 

When to Use: “We need to discuss logistics of code/actually produce code.”