Tip: Choose Save as PDF in the print dialog to download. Use A4 paper size.
Shade in the A or B circle for each question.
Draw a line connecting each item on the left to its match on the right.
| Left column | Right column | |
|---|---|---|
| 1Role: Designer | AThe team member responsible for the look and layout of the project, such as the screen designs | |
| 2Owner: Mia | BShows that Mia is the one person responsible for finishing this task | |
| 3Assigning tasks by strength: Sam is great at testing, so Sam gets the testing job | CTwo people were given the same task with no roles, so they may both build the menu and repeat the same work. Give each person a separate role or task. | |
| 4A regular check-in where each member reports progress and raises problems | DMeeting: Mon 9:00 - What did you finish? Any blockers? | |
| 5Task: Write the user guide | Assigned to: Everyone | ETask: Test the app | Assigned to: Sam | |
| 6Task: Build the menu | Assigned to: Ali, Zoe (no roles set) | FGiving a task to everyone means no one is clearly responsible, so it may be missed or done twice. Assign one named person. |
Complete each line of code by filling in the missing parts.
Shade in the letter of the line that contains an error.
role — A job given to one team member with set tasks they are responsible for, so no task is missed and no two people do the same work twice.Task: Write the test cases
Owner: SamStrength: Drawing
Role: Designer
Task: Design the logoMeeting: Weekly check-in
Each member reports on their tasksTask: Build the menu page
Owners per task: 1Tasks: 6
Assigned: 6
Unassigned: 0