Pair Programming

Covering what pair programming is, its three advantages, egoless programming, pair programming vs formal code inspections, how pair programming supports refactoring, productivity findings from both student and experienced programmer studies, the critical value of knowledge sharing, and the dynamic nature of pair assignment

download Export

search_insights Statistics

stylus_note White Board

Quran

calculate Calculator

dictionary Dictionary

fullscreen Full Screen

more_vert More

QUESTION OF

volume_mute Read quiz aloud

Views #: 204

Questions #: 10

Pass Score: 80.0%

Style

Step

List

Mode

Exam

Practice

What Is Pair Programming?

1 pts

volume_mute

The diagram below summarises the key benefits of pair programming.

Which statement best describes pair programming as practised in XP?

A senior programmer reviews a junior programmer's code after it has been written

Two programmers work independently on the same feature and then merge their code

Programmers work in pairs, actually sitting together at the same workstation to develop software — pairs are created dynamically so all team members work with each other during the development process

One programmer writes code while the other writes the project documentation

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Three Advantages of Pair Programming

1 pts

volume_mute

Which of the following are the three stated advantages of pair programming in XP? Select all that apply.

It supports the idea of collective ownership and responsibility — reflecting the concept of egoless programming where the software is owned by the team as a whole

It helps support refactoring by ensuring others benefit immediately from the improvements, making them likely to support the process

It acts as an informal review process because each line of code is looked at by at least two people

It always produces twice as much code as individual programming in the same time

It eliminates all software defects before integration

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Egoless Programming

1 pts

volume_mute

Pair programming is said to reflect Weinberg's (1971) idea of egoless programming. What does this mean?

The software is owned by the team as a whole and individuals are not held responsible for problems with the code — the team has collective responsibility for resolving problems

Egoless programming means programmers must agree with all decisions made by the project manager

Programmers must work anonymously without their names attached to any code

Programmers are not allowed to take pride in their work

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Pair Programming as Informal Code Review

1 pts

volume_mute

How does pair programming compare to formal code inspections and reviews?

Formal code inspections have been replaced entirely by pair programming in all modern software development

Pair programming is a less formal process that probably doesn't find as many errors as formal code inspections, but it is a much cheaper inspection process that does not introduce delays into the development process

Pair programming and formal code inspections find exactly the same number of errors

Pair programming is more rigorous than formal code inspections and finds more errors

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Pair Programming and Refactoring

1 pts

volume_mute

Why does pair programming make refactoring easier to sustain compared to individual programming?

Because in individual programming, refactoring effort is expended for long-term benefit and an individual may be judged as less efficient — but where pair programming and collective ownership are used, others benefit immediately from the refactoring and are likely to support the process

Because pair programmers always have more time for refactoring than individual programmers

Because refactoring is automated when two programmers work together

Because pair programming eliminates code complexity and therefore removes the need for refactoring

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Pair Programming Productivity — Student Study

1 pts

volume_mute

What did Williams and collaborators find in their study of pair programming productivity using student volunteers?

Pair programming was significantly less productive than individual programming

Pair programming always produces exactly twice as much code as individual programming

Pair programming was found to have no effect on software quality

Pair programming productivity seems to be comparable with two people working independently — pairs discuss the software before development, probably have fewer false starts and less rework, and spend less time repairing bugs found during testing

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Pair Programming — Experienced Programmer Studies

1 pts

volume_mute

Studies with more experienced programmers produced different results. Complete the sentence.

Studies with more experienced programmers (Arisholm et al., 2007; Parrish et al., 2004) found a significant (1) in productivity compared to two programmers working alone, though there were some quality benefits. Nevertheless, the (2) of knowledge that happens during pair programming is very important as it reduces the overall risks when team members leave.

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Knowledge Sharing — Key Value of Pair Programming

1 pts

volume_mute

True or False: Even if pair programming has some productivity costs for experienced programmers, it may still be worthwhile solely because of the knowledge sharing it promotes.

False

True

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Classify Pair Programming Benefits

1 pts

volume_mute

Benefits

×Each line of code is looked at by at least two people reducing defect escape rate

×No islands of expertise develop — any team member can change any part of the code

×Refactoring is more likely to be supported because others immediately benefit from improvements

×The sharing of knowledge during pairing reduces project risk when team members leave

Code quality

Knowledge and ownership

Process sustainability

Classify each benefit of pair programming under the correct category.

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Pair Programming — Dynamic Pairing

1 pts

volume_mute

In XP, do the same two programmers always work together as a pair throughout the project?

Yes — fixed pairs are assigned at the start of the project and maintained throughout to build expertise

No — pairs are created dynamically so that all team members work with each other during the development process; the same pairs do not always program together

Yes — but pairs are reassigned once per sprint to allow some variation

No — pair programming is only used for the most complex features; simpler code is written individually

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Undergraduate Professional

What Is Pair Programming?

Correct Answer

Explanation

Three Advantages of Pair Programming

Correct Answer

Explanation

Egoless Programming

Correct Answer

Explanation

Pair Programming as Informal Code Review

Correct Answer

Explanation

Pair Programming and Refactoring

Correct Answer

Explanation

Pair Programming Productivity — Student Study

Correct Answer

Explanation

Pair Programming — Experienced Programmer Studies

Correct Answer

Explanation

Knowledge Sharing — Key Value of Pair Programming

Correct Answer

Explanation

Classify Pair Programming Benefits

Correct Answer

Explanation

Pair Programming — Dynamic Pairing

Correct Answer

Explanation

Quran Recitation

Query Dictionary

Select a result: