C01 · Topic 1.1 · 40 minutes · CRD-1.A, CRD-1.B, CRD-1.C
Working together on a problem
By the end you can:
- Explain a benefit of diverse perspectives.
- Coordinate responsibilities and shared review.
- Distinguish collaboration from isolated division of work.
Start here; no earlier topic is required.
- Collaboration
- People working together on a shared problem, with communication and coordinated responsibilities.
- Perspective
- A person’s experience or viewpoint that can reveal a different need or assumption.
Understand
A team can combine different skills and experiences to find problems one developer misses. Diversity does not automatically make every decision correct: members must listen, compare evidence and revise assumptions. A single representative is not a complete account of a group’s needs.
Dividing a project into parts helps only when the parts fit a shared specification. Agree on interfaces, responsibilities and how to share changes. Review one another’s work so a mistaken assumption does not survive merely because only one person owned that component.
Worked example
A booking team has three fictional testers who cannot find booking and one who cannot distinguish colour-only room status.
- A developer proposes changing the header colour, but that does not address either observed task barrier.
- A designer makes booking visible; an accessibility reviewer adds text/icon status.
- The team agrees what each change must do and asks peers to test the integrated version.
Explore each concept
Choose a concept, change its inputs and follow the explanation. Each example models the stated rule or scenario; completing it is practice rather than evidence of mastery.
- Diverse perspectives
- Driver and navigator
- Shared tools and conflict resolution
Change it · step through · explain
Change an input, predict what will happen, then advance one step. Read why the state changes, reset and experiment. This fixed teaching model does not save progress or award XP.
Ready · Make a prediction
- Team approachpaired-reviewWaiting
- User evidencecolour-vision-barrierWaiting
Ready to explore: Pair programming and shared review
Why: Change an input, predict the first effect, then advance one step.
Try this: Change one input or choose another listed case. Predict the effect, reset and compare the states and governing rule.
Step through and experiment
Change it · step through · explain
Change an input, predict what will happen, then advance one step. Read why the state changes, reset and experiment. This fixed teaching model does not save progress or award XP.
Ready · Make a prediction
- Input 1visible-and-labelledWaiting
Ready to experiment
Why: Predict the first change, then advance one step.
Try this: Compare text-only with visible-and-labelled. Which barrier remains?
Check a misconception
Claim: Splitting the work means nobody needs to review another person’s part.
Shared review catches interface and assumption problems that separate work can miss.
Guided practice
Assign responsibilities for the two revisions and name one integration check.
Work with a partner. Make a prediction, compare your reasoning, then identify the rule that supports your answer.
Independent transfer
A team member disagrees with the icon choice. Propose an evidence-based way to resolve it.
Exit check
Name a benefit and a limit of inviting different user perspectives.
Write your reasoning before comparing with a classmate. If your teacher assigned this task, submit it through My classes to save your work and receive feedback.
Check yourself
Your practice so far
Check an answer to see its rationale.