AP Computer Science Principles · Unit 1 lecture · Part 2 of 11 · 6 min

1.1 Collaboration in practiceHow good teams actually work

Mr. Thompkins
Putting people in a room doesn't make them a team. Good collaboration is a set of skills, and the exam asks about them by name. Let's learn the names and what each one looks like when it's done well.

Effective teams practice four interpersonal skills. Communication: saying clearly what you're doing and why, and really listening. Consensus building: finding a plan that everyone can support, even if it wasn't anyone's first choice. Conflict resolution: settling disagreements fairly, ideally with evidence instead of volume. Negotiation: trading so that each person gets what matters most to them.

SkillWhat it looks likeExample
CommunicationSay what you are doing and listen"I am rewriting the login screen. Who uses it?"
Consensus buildingFind a plan everyone can supportThe team votes, then agrees to try the winner for a week
Conflict resolutionSettle a disagreement fairlyTwo designs? Test both with real users
NegotiationTrade so each side gets what matters most"You pick the colors, I pick the layout"
The four collaboration skills the course names, with what each looks like on a real team.
?Wait, what's consensus?
Consensus is general agreement: a decision the whole group can accept and support. It doesn't mean everyone thinks it's the best idea. It means nobody is left out, and the team commits to it together.

Pair programming

One famous model of collaboration is pair programming. Two programmers share one computer. The driver types the code. The navigator watches each line, catches mistakes as they happen, and thinks about where the program is going next. They swap roles often. It sounds slower than two people working separately, but pairs catch many errors the moment they are typed, and both people end up understanding all of the code.

One computerDriverNavigatortypes the codereads, checks, plansswap roles often
Pair programming: the driver types, the navigator reviews and plans, and they switch roles often.

Teams today rarely sit in one room, so they use online tools that let programmers share and give feedback on ideas and documents: shared documents and slides, comment threads on code, chat channels, shared task boards. These tools let a team in three time zones review the same code and see each other's comments. The course doesn't ask you to name specific products. It asks you to know what the tools are for: sharing work and giving feedback.

There is one more piece of good teamwork that matters a lot in this course: giving credit. When your program uses code that someone else wrote, whether a teammate, a classmate, a library, a website or an AI tool, you acknowledge it in the program's documentation, with where it came from or who wrote it. We'll come back to this in Topic 1.3.

?Wait, what's a code segment?
A code segment is a collection of program statements that is part of a larger program: a few lines, a loop, a procedure. When you credit someone else's work, you credit the specific code segment you used.
Pause and think
Two teammates disagree about whether their quiz app should show the correct answer right away or only at the end. Which collaboration skill fits best, and what would it look like?
I thought about it. Show me
Conflict resolution, and the fairest way is with evidence: build both versions as quick prototypes, let a few classmates try each, and go with what helps users more. That also builds consensus, because the decision comes from data instead of from whoever argues loudest.
Name the skill
Read each moment from a team project and name the collaboration skill or model it shows. (a) Mia types while Jon reads each line and points out a missing closing brace. (b) The team can't agree on a color scheme, so they agree to let the user pick a theme in settings. (c) Before the vote on which feature to cut, Ravi makes sure each teammate has explained their view and that the final plan is one everyone will support. (d) Leah posts a draft of the design in a shared document and teammates leave comments on it overnight.
  1. (a) Pair programming: Mia is the driver, Jon is the navigator, and the error is caught as it's typed.
  2. (b) Negotiation, or conflict resolution: instead of one side winning, they find an option that gives everyone what matters to them.
    Why?
    Either name is defensible here. On the exam, look for the choice that matches the action described: trading to a compromise is negotiation.
  3. (c) Consensus building: every view is heard, and the team commits to a plan everyone can accept.
  4. (d) Online collaboration tools: sharing a document and giving feedback on it, without meeting in person.

Answer: (a) Pair programming. (b) Negotiation (resolving a conflict). (c) Consensus building. (d) Using an online tool to share and give feedback.

Stuck? Get a hint
  1. For each moment, ask: is this about who types, about a disagreement, about agreeing as a group, or about sharing work?
  2. Two people at one keyboard with different jobs is a named model.
  3. A comment thread on a shared document is an online collaboration tool.
Check yourself
Which statement best describes the benefit of pair programming?
  1. AIt lets each programmer work on a different program at the same time.
  2. BIt guarantees the program will have no errors.
  3. COne programmer writes code while the other reviews it as it is written, so many errors are caught early and both understand the code.
  4. DIt removes the need to test the finished program.
Show the answer

C. Pair programming puts a second set of eyes on every line as it is written. That catches many errors early, but it guarantees nothing, which is the trap in the second choice. The program still needs testing.

  • Collaboration skills: communication, consensus building, conflict resolution, negotiation.
  • Pair programming: a driver types and a navigator reviews and plans, swapping roles often.
  • Online tools let programmers share work and give feedback from anywhere.
  • Credit any code segment written by someone else, including from libraries, websites and AI tools.