Milestones and deadlines

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

Milestones and deadlines

Name:
Date:
Class:

Quick Questions

Shade in the A or B circle for each question.

1. Which best describes a milestone in a project plan?
A A checkpoint showing a major piece of work is complete
B A single small task that takes a few minutes
2. Which is the best example of a milestone for a school app project?
A Work on the app when you feel like it
B Prototype finished and ready for testing by 14 June
3. How is a milestone usually shown on a Gantt chart?
A As a long bar that stretches across many weeks
B As a marker, such as a diamond, on a single date
4. When setting milestone dates, what should you do?
A Work out how long the tasks before it will take, then set a realistic date
B Pick the final due date for every milestone
5. Your team's 'Design complete' milestone is due Friday, but the designs are only half done on Thursday. What does this tell you?
A The project may be behind schedule and the plan needs checking
B The project is on track, so nothing needs to change

Match the Pairs

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

Left columnRight column
1Milestone: Prototype finished - 14 Aug AA milestone is a checkpoint showing finished work, not a task with a duration. It should say what is complete, for example 'Logo approved - 12 Aug'.
2Milestone ◆ on Gantt chart BA diamond marker placed on the timeline where a major piece of work should be finished
3Setting a milestone date: work backwards from the final deadline so each checkpoint is realistic CA checkpoint with a set date showing a major piece of work is complete
4Checking progress against milestones: compare today's status with the planned milestone date DThe milestone has no deadline, so the team cannot check whether they are on track. Add a date, such as 'Prototype finished - 14 Aug'.
5Milestone: Design the logo (3 days) EMilestone: Prototype - due 2 Oct Today: 5 Oct Status: Behind by 3 days
6Milestone: Prototype finished - (no date) FFinal deadline: 30 Oct Testing done: 16 Oct Prototype done: 2 Oct

Definitions

milestone

Fill in the Blanks

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

1.
_________ "Prototype finished" DUE 14/06
2.
MILESTONE "Prototype finished" ___ 14/06
3.
MILESTONE "Prototype done" DURATION _
4.
IF done = FALSE AND today _ dueDate THEN
5.
IF prototypeDone = ____ THEN

Spot the Error

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

Question 1
A milestone = "Prototype done"
B deadline = 12
C today = 15
D IF today < deadline THEN
E PRINT "Milestone late"
F ENDIF
Question 2
A task "Build" start=1 end=10
B milestone "Prototype" day=5
C task "Test" start=11 end=15
Question 3
A deadline = 30
B test_done = deadline + 5
C build_done = test_done - 10
D PRINT build_done
Question 4
A milestone "Design done" due 40
B milestone "Build done" due 20
C milestone "Launch" due 30
Question 5
A due = 12
B today = 10
C proto_done = TRUE
D IF proto_done = FALSE THEN
E PRINT "Milestone met"
F ENDIF

Answer Key

Milestones and deadlines
Section A: Quick Questions
Q1
A — A checkpoint showing a major piece of work is complete
Q2
B — Prototype finished and ready for testing by 14 June
Q3
B — As a marker, such as a diamond, on a single date
Q4
A — Work out how long the tasks before it will take, then set a realistic date
Q5
A — The project may be behind schedule and the plan needs checking
Section B: Match the Pairs
Q1
Milestone: Prototype finished - 14 Aug → A checkpoint with a set date showing a major piece of work is complete
Q2
Milestone ◆ on Gantt chart → A diamond marker placed on the timeline where a major piece of work should be finished
Q3
Setting a milestone date: work backwards from the final deadline so each checkpoint is realistic → Final deadline: 30 Oct Testing done: 16 Oct Prototype done: 2 Oct
Q4
Checking progress against milestones: compare today's status with the planned milestone date → Milestone: Prototype - due 2 Oct Today: 5 Oct Status: Behind by 3 days
Q5
Milestone: Design the logo (3 days) → A milestone is a checkpoint showing finished work, not a task with a duration. It should say what is complete, for example 'Logo approved - 12 Aug'.
Q6
Milestone: Prototype finished - (no date) → The milestone has no deadline, so the team cannot check whether they are on track. Add a date, such as 'Prototype finished - 14 Aug'.
Section C: Definitions
Q1
milestone — A marked checkpoint in a project plan, such as a finished prototype, showing a major piece of work is complete by its deadline. Used to check progress.
Section D: Fill in the Blanks
Q1
MILESTONE "Prototype finished" DUE 14/06
Q2
MILESTONE "Prototype finished" DUE 14/06
Q3
MILESTONE "Prototype done" DURATION 0
Q4
IF done = FALSE AND today > dueDate THEN
Q5
IF prototypeDone = TRUE THEN
Section E: Spot the Error
Q1
D — A milestone is late when today is after its deadline, so the check should be today > deadline. With < the program reports 'late' while there is still time left.
Q2
B — The prototype milestone marks the end of the Build task, so it should sit on day 10. Day 5 would show the prototype as finished halfway through building it.
Q3
B — When setting milestone dates, you work backwards from the final deadline. Testing must finish before it, so the line should be deadline - 5, not + 5.
Q4
A — Milestone dates should be in order. Design is finished before the build, so its due date must be earlier than day 20 (for example 8), not day 40.
Q5
D — The program should say the milestone is met only when the prototype is finished. The test must be proto_done = TRUE, not FALSE.