DoAssignment study guide

B1.6 · Compare planned and actual project progress

Learn to compare planned and actual project progress through clear examples and targeted practice.

Ontario Grade 12 Computer Science

Software Development

ICS4U B1.6 study lesson

A project plan describes intended progress: what work is expected and when. Actual progress describes what has happened, based on evidence gathered during the project. Comparing the two helps a team see whether work is proceeding as planned. The comparison is meaningful only when the planned and actual information refers to the same tasks, checkpoint, and units. In this lesson, a project may be a school software project, but the comparison method applies to project work generally. The focus is B1.6: comparing planned and actual project progress—not choosing a particular project-management method.

What you will learn

Explain why a project plan is a useful reference for checking progress.
Compare planned and actual progress at the same checkpoint using consistent evidence.
Describe a difference accurately without confusing completed work with elapsed time.
Recognize that a comparison informs a project discussion but does not, by itself, explain a delay.

1. Start with the plan and the evidence

ICS3U programming experience may include organizing work into tasks and keeping track of what has been completed. For this expectation, the key step is to compare the project’s intended progress with its observed progress. A plan is the reference point; it is not proof that work has happened. Actual progress should come from evidence, such as a task being completed or a recorded amount of work, rather than a guess.

Before comparing, identify the checkpoint: for example, the end of a particular school week. Then select the same tasks in both records. Use the same measure on each side. If the plan says that 6 of 10 tasks should be complete, compare it with the actual number of those same 10 tasks completed at that checkpoint. Do not compare planned task count with actual hours, or compare different task sets.

A simple comparison can state the planned amount, the actual amount, and the difference. For task counts, subtract planned completed tasks from actual completed tasks. A negative difference means fewer tasks are complete than planned; a positive difference means more are complete than planned. The result describes the comparison, not its cause.

\text{difference} = \text{actual} - \text{planned}

Choose one checkpoint and compare like with like.
Use recorded evidence for actual progress.
State the measure and units; a difference alone can be unclear.
A comparison shows a gap or match, not why it occurred.

2. Read progress carefully

A useful comparison names the date or checkpoint, the work being measured, and both values. For example: “At the Friday checkpoint, 4 of the 6 tasks planned for completion were complete.” This is clearer than saying only “we are behind.” It tells the reader what was expected and what the evidence shows.

Progress can be recorded in different ways, such as completed tasks or hours spent, but those measures answer different questions. A team might have spent the planned number of hours while completing fewer tasks than expected. Reporting hours alone would not establish that the planned work was completed. Keep the chosen measure consistent and avoid treating effort as the same thing as finished work.

A project timeline can make the comparison visible. Planned and actual entries should use the same checkpoint labels. If actual progress differs from the plan, record the difference honestly. A useful next discussion can check whether the records are current and what work remains. Do not assume that a schedule difference proves poor effort or that it identifies the reason for the difference.

Describe both the planned and observed values.
Task completion and time spent are not interchangeable measures.
Use the comparison to support an informed project discussion, not to assign blame.

3. Make a fair comparison

Use this repeatable process at a chosen checkpoint. First, read the plan to determine what work was expected by that point. Next, consult the project record to identify what work is actually complete. Confirm that the same tasks and checkpoint are being compared. Then state the two values, calculate the difference if the measure allows it, and explain what the sign means in ordinary language. Finally, note any limits in the evidence, such as an incomplete status record.

For instance, if the plan and actual record use different definitions of “complete,” the numerical comparison may be misleading. Agree on what counts as completion for the comparison and apply that meaning consistently. If a task is only partly finished, do not silently count it as complete; report it separately or explain how the team records partial work.

This is a descriptive comparison, not a promise that the remaining work will take a particular amount of time. It also does not require a special program. A clear written record, a small table, or a timeline can be enough to compare the planned and actual progress.

Check checkpoint, task scope, units, and completion meaning.
Show the evidence and interpretation, not just a conclusion.
Do not turn one checkpoint’s difference into an unsupported prediction.

4. Practice the comparison

The worked examples use small illustrative project records. Their values are supplied as part of each example; they are not benchmarks for how quickly a real project should proceed. Each timeline displays the plan and actual record at matching checkpoints. Read the labels before interpreting the gap.

A timeline is useful when checkpoint order matters.
A table or written sentence may be clearer when only one checkpoint is being compared.

Worked example

Fewer tasks complete than planned

At the end of Week 2, a team’s plan says 5 of its 8 listed tasks should be complete. Its current task record shows 3 of those same 8 tasks complete. Compare progress at this checkpoint.

Week 2 task comparison

Illustrative counts at the same checkpoint; both refer to the same eight tasks.

Match the comparison
Both records refer to Week 2, the same eight tasks, and the same unit: completed tasks. That makes the comparison like-for-like.
Calculate and interpret
Subtract the planned completed-task count from the actual count. The negative result means the record shows two fewer completed tasks than the plan called for at this checkpoint.
$3 - 5 = -2$
Report the evidence
A fair summary is: “At the end of Week 2, 3 of 8 tasks were complete, compared with 5 of 8 planned; actual progress was 2 tasks below the plan.” This does not establish why the difference occurred.

Answer: Actual progress was 2 completed tasks below the plan at the Week 2 checkpoint.

Check: The task set, checkpoint, and unit match in both records.

Worked example

Progress matches the plan

At a Friday checkpoint, the plan calls for 4 of 7 tasks to be complete. The project record confirms that 4 of those same tasks are complete. State the comparison and what it does—and does not—show.

Friday checkpoint

Planned and actual task counts are equal at the stated checkpoint.

Confirm matching records
The plan and the actual record describe the same seven tasks at the same Friday checkpoint. Both values count completed tasks.
Compare the values
Subtracting the planned count from the actual count gives zero. At this checkpoint, the observed task count matches the planned task count.
$4 - 4 = 0$
Avoid overclaiming
The record supports saying that the task count matches the plan at this checkpoint. It does not establish that every task is complete, that later checkpoints will match, or that time spent was exactly as planned.

Answer: At Friday’s checkpoint, actual progress matches planned progress: 4 of 7 tasks are complete.

Check: A zero difference describes this checkpoint only; it is not a guarantee about future progress.

Worked example

Do not confuse hours with completed tasks

At the Week 3 checkpoint, the plan lists 6 tasks expected complete and 9 planned work hours. The record shows 5 tasks complete and 9 hours spent. Compare what can be compared.

Week 3, two measures

Compare each actual measure only with the same planned measure.

Separate the measures
The plan and record each include task counts and hours. Compare task counts with task counts, and hours with hours; do not combine the two measures.
Compare task completion
The actual task count is one below the planned task count at Week 3. This describes completed work, not the reason for the difference.
$5 - 6 = -1$
Compare recorded hours
The recorded hours equal the planned hours. That does not erase the task-count difference: time spent and tasks completed provide different information.
$9 - 9 = 0$

Answer: At Week 3, task completion is 1 task below plan, while recorded hours match the planned hours.

Check: The comparison keeps tasks and hours in separate units and avoids claiming that matching hours means matching completed work.

Common mistakes and how to avoid them

Comparing actual progress at one checkpoint with planned progress at a different checkpoint.

Correction: Use the same checkpoint for both records, or clearly explain that the comparison is between different dates.

Saying that matching hours proves the planned tasks are complete.

Correction: Compare hours with hours and completed tasks with completed tasks. They are separate measures.

Treating a difference as proof of its cause.

Correction: Report what the records show. A difference alone does not explain why it occurred.

Calling progress “behind” without saying what was expected or observed.

Correction: Name the checkpoint, task measure, planned value, and actual value.

Lesson summary

Planned progress is the work expected by a checkpoint; actual progress is the work supported by the project record.
A fair comparison uses the same checkpoint, task scope, unit, and meaning of completion.
State planned and actual values, then interpret their difference clearly.
A comparison describes the records; it does not by itself explain a difference or predict future progress.

Check your understanding

Question 1

At the same checkpoint, a plan lists 7 tasks complete and the record shows 5 of those tasks complete. What is the actual-minus-planned difference?

2 tasks; actual is above plan
-2 tasks; actual is below plan
12 tasks; actual is above plan
The difference cannot be stated because both values count tasks

Show answer and explanation

-2 tasks; actual is below plan

Subtract the planned count from the actual count: 5 minus 7 is -2. Actual progress is two tasks below the plan at that checkpoint.

Question 2

The plan expects 3 tasks complete and 8 hours spent. The record shows 3 tasks complete and 10 hours spent. Which statement is supported?

Both task completion and hours match the plan.
Task completion matches the plan, while hours are 2 above plan.
Task completion is 2 tasks above plan.
The project must be ahead because more hours were spent.

Show answer and explanation

Task completion matches the plan, while hours are 2 above plan.

The task counts match. The hours difference is 10 minus 8, or 2 hours above the planned amount. More hours do not establish that more tasks were completed.

Question 3

Why should planned and actual progress refer to the same checkpoint?

So the comparison describes the same point in the project.
So any difference can be assumed to have one known cause.
So task counts can be compared with hours.
So a single comparison guarantees that later progress will match.

Show answer and explanation

So the comparison describes the same point in the project.

Matching checkpoints makes the comparison relevant to the same point in time. It does not identify a cause or guarantee future progress.

Key terms

Planned progress: The work that the project plan expects to be complete by a stated checkpoint.
Actual progress: The work recorded as complete, or the amount recorded as spent, by that checkpoint.
Checkpoint: A chosen date or project point at which planned and actual progress are compared.
Like-for-like comparison: A comparison using the same checkpoint, task scope, unit, and completion meaning on both sides.

Continue through ICS4U

View the complete ICS4U Ontario Grade 12 Computer Science curriculum and lessons

About this lesson and its review

Published by DoAssignment. This reviewed lesson follows Ontario Grade 12 Computer Science (ICS4U), expectation B1.6. It is a study resource, not an official curriculum publication.

Before publication, content is checked for structure, mathematical or chemical notation, calculations, course boundaries, and readability. Errors can still occur, so corrections are welcomed.

Official curriculum reference

Report a correction or ask a question