Aim for FiveComputer Science Principles

Unit 1 · Topic 1.1

1.1 Collaboration

A computing innovation is anything that has a program at its core, and almost all of them are built by teams. This topic is about why teams with different backgrounds build better, fairer products, how teams actually share the work, and why talking to users matters from the start.

Key terms

  • computing innovation
  • collaboration
  • diverse perspectives
  • pair programming
  • user feedback

What counts as a computing innovation

A computing innovation is any new product, tool or idea that depends on a program to work. Take away the code and it stops doing its job.

It doesn't have to be something you can hold. The exam groups innovations into three kinds:

  • Physical: a device you can touch, like a smart thermostat, a fitness tracker or a delivery drone.
  • Software: a program or app, like a photo filter app, a video game or a spreadsheet.
  • A computing concept: a new way of doing something that only exists because of computing, like online shopping, ride-sharing or video streaming.

Why diverse teams build better innovations

Every person brings their own experiences, skills and blind spots. A team whose members differ in age, culture, gender, language, ability and background will notice needs and problems that a team of similar people would walk right past.

For example, a team building a voice assistant that includes people with different accents is more likely to test whether it understands all of them. A team with a member who uses a screen reader will catch accessibility problems early.

This is also how teams avoid bias. Bias in a computing innovation often comes from the people who made it assuming everyone is like them. Including more perspectives during design is one of the best ways to catch those assumptions before the product ships.

How teams work together

Teams use online tools to share ideas, code and documents and to give each other feedback. Shared documents, comment threads, chat channels and code-sharing sites let people work on the same project from different places and see each other's changes.

Pair programming is a common model for working together. Two programmers share one computer: the driver types the code, and the navigator reviews each line, thinks ahead and spots mistakes. They swap roles often. It catches errors early and spreads knowledge across the team.

Good teams also rely on people skills, not just coding skills:

  • Communication: explaining your ideas clearly and listening to others.
  • Consensus building: working toward a decision the whole team can support.
  • Conflict resolution: settling disagreements in a respectful way.
  • Negotiation: finding a compromise when people want different things.

Bringing users into the process

The people who will use a program are part of the collaboration too. Developers consult users through surveys, interviews, watching people use a prototype and asking for feedback. What users say helps developers understand what the program is really for and who it needs to work for.

Feedback works best when it comes from many kinds of users. A study app tested only by honors students might be confusing for students who are new to a subject.

Worked examples

Try each one yourself first, then open the solution.

  1. Example 1

    Explaining how collaboration helps

    A team of four students is building an app that helps people find wheelchair-accessible entrances to buildings on campus. Explain one way that including a wheelchair user on the team, or consulting wheelchair users, could improve the app.

    Show the solution
    1. Step 1: Name the specific perspective the person brings: they know from experience which details matter, like whether a ramp is too steep, whether a door opens automatically, or whether an elevator is often out of service.
    2. Step 2: Connect that perspective to a specific change in the app: the team might add a field for door type or a way to report a broken elevator, which the others might never have thought of.
    3. Step 3: Say why that makes the innovation better: the app now meets its real users' needs and avoids a bias toward what able-bodied designers assume is important.

    Answer: A wheelchair user knows which access details actually matter (ramp slope, automatic doors, working elevators), so the team adds features for them that it would otherwise have missed, making the app more useful and less biased.

Common mistakes

  • Saying collaboration helps only because the work gets done faster. The exam's main point is that different perspectives catch problems and reduce bias.
  • Thinking a computing innovation must be a physical device. Software and ideas like online banking count too, as long as a program is central to them.
  • Mixing up the pair programming roles. The driver types; the navigator reviews and plans.

On the exam

  • Expect scenario questions that describe a team or a product and ask which change would best reduce bias or improve the innovation. The answer usually adds a missing perspective or gathers feedback from more kinds of users.
  • On the written response, you may need to explain how your own program's design considered its users. Be specific about who the users are and what you changed because of them.

Connected topics

Videos

Check yourself

4 questions on 1.1 Collaboration. Pick an answer to see if you got it, and why.

Question 1 of 4

A company is building a voice assistant. The team first tests it only with its own engineers, who all grew up in the same region. After launch, users with other accents find that it often misunderstands them. Which change to the development process would most likely have prevented this problem?

Question 2 of 4

Two students are pair programming. Which of the following best describes how they should work?

Question 3 of 4

A team is designing an app that helps students in a school find a study partner. Which two of the following are ways the team could investigate what students need from the app? Select two answers.

Select two answers. 0 of 2 chosen

Question 4 of 4

A programming team has members in three different cities. Which of the following best explains how an online code-sharing tool supports their collaboration?

0 of 4 answered