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 | |
|---|---|---|
| 1Time frame: Test formulas by 12 May | AThe activity date is before the milestone it is linked to, so it would be tested before the work is finished | |
| 2Time frame: During the project, after each milestone | BCheck chart accuracy | 3 days | 5 June to 7 June | |
| 3A time frame states when each evaluation activity will happen and how long it has | CCollect user feedback | After handover | 20 June | |
| 4Some evaluation happens after the project to judge how well the finished solution worked | DThe time frame has no date or length, so nobody knows when the activity must happen or how long it takes | |
| 5Evaluate the dashboard | Sometime later | ESays the evaluation happens while the project runs, and is linked to each milestone | |
| 6Test security controls | 30 April | Milestone: Data cleaned (due 10 May) | FSets a date for one evaluation activity, so the team knows when the check must be finished |
Complete each line of code by filling in the missing parts.
Shade in the letter of the line that contains an error.
time frame — States when each evaluation activity will happen and how long it has, such as during or after the project, with dates linked to milestones.activity: Test formulas
timeframe: during project
milestone: Prototype builtactivity: Survey users
timeframe: after project
milestone: Solution handed overstart: 3 Mar
end: 7 Mar
activity: Check chartsactivity: Review dashboard
linked to: milestone 3
date: 14 Apractivity: Survey users
timeframe: 20 Mar to 24 Mar