Pair Programming

Two developers working together on the same code.

Also Known As

• Buddy Programming
• Collaborative Coding
• Collective Code Ownership (in Extreme Programming)
• Cross-Functional Teams (in Lean Software Development)
• Joint Programming
• Mob Programming
• Pairing

Related

• Coding
• Review
• Stakeholder Management

Addresses / Mitigates

• Coordination Risk: Enhances collaboration and coordination between developers.
• Learning Curve Risk: Facilitates knowledge sharing and learning.
• Implementation Risk: More eyeballs means fewer bugs and a better implementation

Attendant Risks

• Coordination Risk: Requires effective coordination and can be challenging to implement.
• Schedule Risk: Can slow down individual productivity, impacting overall schedule.
• Agency Risk: Staff might not like working in this arrangement.

Used By

• Extreme Programming: XP encourages two developers working together at one workstation, which improves code quality and facilitates knowledge sharing.
• Lean Software Development: Lean encourages collaboration through cross-functional teams.

Description

"Pair programming is an agile software development technique in which two programmers work together at one workstation. One, the driver, writes code while the other, the observer or navigator, reviews each line of code as it is typed in. The two programmers switch roles frequently." - Pair programming, Wikipedia

Pair Programming involves two developers working together on the same code. One developer writes the code while the other reviews each line in real-time, providing instant feedback and suggestions. This practice not only improves code quality but also facilitates knowledge sharing and collaboration between team members.

See:

• Crisis Mode

See Also

No documents tagged