Responsibility in an evaluation strategy

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

Responsibility in an evaluation strategy

Name:
Date:
Class:

Quick Questions

Shade in the A or B circle for each question.

1. In an evaluation strategy, what does the responsibility column tell you?
A Who will carry out and report on each evaluation task
B How much each evaluation task will cost
2. Which task is best given to the developer?
A Testing that each formula gives the expected result
B Deciding if the dashboard suits the client's daily needs
3. Who is best placed to judge whether a dashboard is easy to use and meets their needs?
A The developer alone
B The client or user
4. Why might an independent reviewer check the accuracy of a visualisation?
A They have no stake in the work, so their judgement is unbiased
B They know the solution better than the developer does
5. Which evaluation task entry names a responsibility clearly?
A Check chart against source data - someone - sometime
B Check chart against source data - Developer - 12 May

Match the Pairs

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

Left columnRight column
1Responsible: Developer ATask: Check dashboard meets needs | Responsible: Client
2Responsible: Independent reviewer BNo person or group is named, so nobody knows who will carry out or report on the task
3The client or user judges whether the solution meets their needs, so they are named as the person responsible for that task CSomeone outside the project team checks the solution and reports without bias
4Each evaluation task in the strategy is paired with a named person or group who carries it out and reports back DAn independent review cannot be done by the developer, who built the solution and is not independent
5Task: Review accuracy | Responsible: (blank) EThe person who built the solution runs the task, such as testing formulas, and reports the results
6Task: Independent review | Responsible: Developer FTask: Test formulas | Responsible: Developer | Report to: Client

Definitions

Responsibility

Fill in the Blanks

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

1.
Task: Test formulas against hand calcs Responsibility: _________
2.
Task: Say if the dashboard meets needs Responsibility: ______
3.
Task: Give an unbiased check of the solution Responsibility: ____________________
4.
Task: Fix errors found in testing ______________: Developer
5.
Task: Complete the user feedback survey Responsibility: ____

Spot the Error

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

Question 1
A Task: Check formulas by hand
B Responsibility: Everyone
C Time frame: Week 2
Question 2
A Task: Test dashboard filters
B Time frame: Week 4
C Responsibility: Friday
Question 3
A Task: Independent code review
B Time frame: Week 6
C Who: Developer who wrote it
Question 4
A Task: Client signs off solution
B Responsibility: Developer
C Time frame: Final week
Question 5
A Task: Fix errors from testing
B Responsibility: Client
C Time frame: 2 days

Answer Key

Responsibility in an evaluation strategy
Section A: Quick Questions
Q1
A — Who will carry out and report on each evaluation task
Q2
A — Testing that each formula gives the expected result
Q3
B — The client or user
Q4
A — They have no stake in the work, so their judgement is unbiased
Q5
B — Check chart against source data - Developer - 12 May
Section B: Match the Pairs
Q1
Responsible: Developer → The person who built the solution runs the task, such as testing formulas, and reports the results
Q2
Responsible: Independent reviewer → Someone outside the project team checks the solution and reports without bias
Q3
The client or user judges whether the solution meets their needs, so they are named as the person responsible for that task → Task: Check dashboard meets needs | Responsible: Client
Q4
Each evaluation task in the strategy is paired with a named person or group who carries it out and reports back → Task: Test formulas | Responsible: Developer | Report to: Client
Q5
Task: Review accuracy | Responsible: (blank) → No person or group is named, so nobody knows who will carry out or report on the task
Q6
Task: Independent review | Responsible: Developer → An independent review cannot be done by the developer, who built the solution and is not independent
Section C: Definitions
Q1
Responsibility — In an evaluation strategy, it names who carries out and reports on each evaluation task, such as the developer, the client or user, or an independent reviewer.
Section D: Fill in the Blanks
Q1
Task: Test formulas against hand calcs Responsibility: Developer
Q2
Task: Say if the dashboard meets needs Responsibility: Client
Q3
Task: Give an unbiased check of the solution Responsibility: Independent reviewer
Q4
Task: Fix errors found in testing Responsibility: Developer
Q5
Task: Complete the user feedback survey Responsibility: User
Section E: Spot the Error
Q1
B — A responsibility must name a specific person or group. 'Everyone' means nobody is accountable. It should name one role, such as 'Responsibility: Developer'.
Q2
C — A responsibility names who does the task, not when. 'Friday' is a date. The line should name a person or group, such as 'Responsibility: Client'.
Q3
C — An independent review must be done by someone who was not involved in building the solution. The developer who wrote the code cannot review it independently. It should be 'Who: Independent reviewer'.
Q4
B — Signing off the solution is the client's decision, because the client judges whether their needs are met. The developer cannot approve their own work. It should be 'Responsibility: Client'.
Q5
B — The developer built the solution, so the developer fixes the errors found in testing. The client reviews and approves but does not fix the errors. It should be 'Responsibility: Developer'.