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 | |
|---|---|---|
| 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 |
Complete each line of code by filling in the missing parts.
Shade in the letter of the line that contains an error.
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.Task: Test formulas against hand calcs
Responsibility: DeveloperTask: Say if the dashboard meets needs
Responsibility: ClientTask: Give an unbiased check of the solution
Responsibility: Independent reviewerTask: Fix errors found in testing
Responsibility: DeveloperTask: Complete the user feedback survey
Responsibility: User