How it works
Teams need communication, role clarity, shared files or version habits, and a way to compare ideas against evidence.
Resolve disagreements by testing prototypes against requirements instead of choosing by opinion.
Common error
Collaboration is not the same as one person doing all coding and others only watching.
Worked example
Two teammates propose different search interfaces. Resolve the disagreement with evidence.
Data / pseudocode
Requirement: locate a task by keyword
Option A: text search
Option B: category-only menu
Users: tasks may span categoriesBuild small prototypes and compare completion of the required keyword-search task. Divide implementation and testing responsibilities, review each other work, and track changes. Personal preference should not replace evidence about whether the requirement is met.
Exercises
1.3.1
Name two collaboration practices that reduce accidental loss of another teammate changes.
Show solution
Use a shared version history or controlled file workflow, and communicate which changes are being made. Review and reconcile edits before combining them.
1.3.2
Why is attribution important when a team uses external code or media?
Show solution
It identifies what was created by the team and what came from others, supports license compliance, and helps reviewers understand the contribution. Attribution alone does not grant permission to use material.