AP CSP 1.1 Exercise 1: Collaboration Post-Mortem

Big Idea 1 · Topic 1.1 · Exercise 1

Collaboration Post-Mortem

25 minutes

Back to the Topic 1.1 lessonAll CSP topics

How this page works

The writing boxes below are yours. What you type stays in this browser, is saved here as you go, and is never sent to us or to your teacher. Hand the written work in the way your teacher asked for it.

The graded check at the bottom is the part that records to your teacher's gradebook.

Part B, from your handoutNot recorded

Your handout says these are the same items available here. Part A stays on paper.

Q1 · 3 points on the handout

A classmate reviews the same log and concludes: 'The real problem was talent - four stronger programmers would have shipped a great app.' Argue the CED's counterpoint: what do four even-stronger copies of the SAME perspective still fail to produce?

Q2 · 3 points on the handout

The team gets one semester to build CampusNight 2.0. Design their user-consultation plan: whom should they gather information from, when, and what does the CED say that information is actually used for?

Q3 · 2 points on the handout

ENRICHMENT: Open-source projects like the Python language are built by thousands of contributors who never meet. Explain how a pull request satisfies EK CRD-1.B.1's description of what online tools do - and name two EK CRD-1.C.1 interpersonal skills that appear, in written form, in a typical code-review thread.

Graded checkRecorded

5 questions on the same ideas, drawn from this exercise's answer key. These are auto-graded and reported.

Question 1 of 5EK CRD-1.A.3 / CRD-1.A.4
A classmate says CampusNight would have succeeded with four stronger programmers from the same coding club. What does the CED say four stronger copies of the same perspective still fail to produce?
Incorrect. Schedule is not what the CED ties to collaboration quality here.
Incorrect. Feature count does not address who the product excluded.
Incorrect. Code quality was never the failure. The app worked; it excluded people.
Correct. Effective collaboration produces an innovation reflecting the diversity of talents and perspectives of its designers. More skill in one perspective leaves the blind spot, and the bias, exactly where it was.
Question 2 of 5EK CRD-1.A.6
For CampusNight 2.0, whom does the CED say the team should gather information from?
Incorrect. Staff are one useful group, but limiting it to them repeats the mistake of consulting a narrow slice.
Incorrect. Surveying the people the app already served reproduces the original blind spot.
Correct. The CED asks for information from potential users, which is precisely the group version 1 designed around and excluded.
Incorrect. The team asking itself again is what caused the failure.
Question 3 of 5EK CRD-1.A.5
When should that user consultation happen?
Incorrect. Consulting after shipping is how version 1 found out, at the users' expense.
Correct. The CED treats consultation and communication as aspects of development itself, which means recurring check-ins rather than one event.
Incorrect. Waiting for a complaint makes the excluded user the bug report.
Incorrect. A single survey at the start is better than none, and it still misses everything learned once a prototype exists.
Question 4 of 5EK CRD-1.A.6
What does the CED say the information gathered from users is actually used FOR?
Correct. The information shapes what gets built: it reveals the purpose from perspectives the team does not hold, and the program is meant to incorporate them.
Incorrect. Language choice is an implementation decision, unrelated to user consultation.
Incorrect. Scheduling is not what the CED ties this information to.
Incorrect. Marketing uses audience research too, but that is not the development purpose the CED names.
Question 5 of 5EK CRD-1.B.1
A pull request satisfies the CED's description of what online collaboration tools do because it supports which two things?
Incorrect. Release bookkeeping is not collaboration in the sense the CED describes.
Incorrect. Documentation matters and is a separate idea from the share-and-feedback pairing.
Incorrect. Continuous integration may run alongside a pull request, but that is not the pairing the CED names.
Correct. The CED describes online tools as supporting collaboration by letting programmers share AND provide feedback on ideas and documents. A pull request is both: the change is posted, and reviewers comment on it before anything merges.

Get in Touch

Whether you're a student, parent, or teacher — I'd love to hear from you.

Just want free AP CS resources?

Enter your email below and check the subscribe box — no message needed. Students get daily practice questions and study tips. Teachers get curriculum resources and teaching strategies.

Typically responds within 24 hours

Message Sent!

Thanks for reaching out. I'll get back to you within 24 hours.

🏫 Welcome, fellow educator!

I offer curriculum resources, practice materials, and study guides designed for AP CS teachers. Let me know what you're looking for — whether it's classroom materials, a guest speaker, or Teachers Pay Teachers resources.

Email

[email protected]

📚

Courses

AP CSA, CSP, & Cybersecurity

Response Time

Within 24 hours

Prefer email? Reach me directly at [email protected]