Roles and responsibilities in a team project

Tip: Choose Save as PDF in the print dialog to download. Use A4 paper size.

Roles and responsibilities in a team project

Name:
Date:
Class:

Quick Questions

Shade in the A or B circle for each question.

1. Your team is building a school app. Which is the best way to hand out the work?
A Tell everyone to just work on whatever they feel like
B Give each person a role with specific tasks they are responsible for
2. What does 'double handling' mean in a team project?
A Two people unknowingly doing the same task
B One person doing two different jobs well
3. Mia loves drawing and design, and Jay is great at writing code. Who should be given the interface artwork task?
A Jay, because he is the best at everything
B Mia, because her strengths suit the task
4. The task list says 'Write the test plan' but has no name beside it. What is the likely problem?
A No one is responsible, so it might never get done
B Everyone will do it, so it will be done perfectly
5. Which statement about a team check-in meeting is true?
A It lets members report progress and spot problems early
B It is only for giving the team leader's tasks to everyone again

Match the Pairs

Draw a line connecting each item on the left to its match on the right.

Left columnRight 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.

Definitions

role

Fill in the Blanks

Complete each line of code by filling in the missing parts.

1.
Task: Write the test cases _____: Sam
2.
Strength: Drawing Role: ________ Task: Design the logo
3.
Meeting: Weekly check-in Each member reports on their _____
4.
Task: Build the menu page Owners per task: _
5.
Tasks: 6 Assigned: 6 Unassigned: _

Spot the Error

Shade in the letter of the line that contains an error.

Question 1
A Mia: strong at drawing
B Leo: strong at coding
C Task: Mia codes the menu
D Task: Mia draws the logo
Question 2
A Test login - Owner: Sam, Mia
B Write help - Owner: Mia
C Build menu - Owner: Leo
Question 3
A Mia: design the logo
B Leo: code the menu
C Sam: code the menu
Question 4
A Check-in: Friday, 10 minutes
B Only the leader gives updates
C Each says what is stuck
Question 5
A Task: draw the logo
B Owner: Leo (weak at art)
C Task: code the menu
D Owner: Leo (strong at coding)

Answer Key

Roles and responsibilities in a team project
Section A: Quick Questions
Q1
B — Give each person a role with specific tasks they are responsible for
Q2
A — Two people unknowingly doing the same task
Q3
B — Mia, because her strengths suit the task
Q4
A — No one is responsible, so it might never get done
Q5
A — It lets members report progress and spot problems early
Section B: Match the Pairs
Q1
Role: Designer → The team member responsible for the look and layout of the project, such as the screen designs
Q2
Owner: Mia → Shows that Mia is the one person responsible for finishing this task
Q3
Assigning tasks by strength: Sam is great at testing, so Sam gets the testing job → Task: Test the app | Assigned to: Sam
Q4
A regular check-in where each member reports progress and raises problems → Meeting: Mon 9:00 - What did you finish? Any blockers?
Q5
Task: Write the user guide | Assigned to: Everyone → Giving a task to everyone means no one is clearly responsible, so it may be missed or done twice. Assign one named person.
Q6
Task: Build the menu | Assigned to: Ali, Zoe (no roles set) → Two 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.
Section C: Definitions
Q1
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.
Section D: Fill in the Blanks
Q1
Task: Write the test cases Owner: Sam
Q2
Strength: Drawing Role: Designer Task: Design the logo
Q3
Meeting: Weekly check-in Each member reports on their tasks
Q4
Task: Build the menu page Owners per task: 1
Q5
Tasks: 6 Assigned: 6 Unassigned: 0
Section E: Spot the Error
Q1
C — Tasks should be assigned by strength. Leo is strong at coding, so the line should be 'Task: Leo codes the menu'.
Q2
A — Each task needs one clear owner. Two owners means double handling and nobody is sure who is responsible. It should be 'Owner: Sam'.
Q3
C — Leo already codes the menu, so giving Sam the same task is double handling. Sam's role is testing, so it should be 'Sam: test the menu'.
Q4
B — At a check-in every member reports on their own tasks. If only the leader speaks, gaps and problems stay hidden. It should be 'Each says what is done'.
Q5
B — The logo task should go to someone whose strength fits it. Leo is weak at art, so the owner should be Mia (strong at art).