In pair programming, one developer codes whilst the other observes and reviews the progress made. If done well, pair programming can speed up development time, improve code quality and avoid human error.
The developer-focused on coding is commonly referred to as the ‘driver’. Whereas the developer who is observing, reviewing and providing feedback is known as the ‘navigator’.
Learn how to prioritize by making it a simple process, to build products that stand out. Learn more about how to source insight, choose the right prioritization framework and much more.
During pair programming, the programmers are expected to swap roles on a regular basis — as rapidly as every couple of minutes! — to keep things fresh.