Tracking progress with a project log
Name:
Date:
Class:
A
Quick Questions
Shade in the A or B circle for each question.
1. Which entry is the better project log entry for a work session?
2. What should every project log entry start with?
3. You hit a bug during a session. What should the log show?
4. Your Gantt chart said the database would be finished by 20 May, but your log shows it was finished on 27 May. What does the log show?
5. Your team changed the plan because the chosen app tool was too hard to use. Where is the best place to evidence why?
B
Match the Pairs
Draw a line connecting each item on the left to its match on the right.
| Left column | Right column | |
|---|---|---|
| 112 Aug: Built login page. Problem: button did not work. Fix: renamed the ID. Next: test with users. | AThe log ignores a problem. Actual progress is behind the plan but no problem or reason for the delay is recorded. | |
| 2Planned: 5 tasks done. Actual: 3 done. Reason: testing took longer. | BProblem: images loaded slowly. Fix: compressed the files. Plan: add 1 day for testing. | |
| 3Dated entries let you see when work happened and in what order | CA complete project log entry with the date, what was done, a problem and its fix, and the next step | |
| 4Recording a problem and its fix shows how you solved issues and why the plan changed | DLog entry - Tue 3 Sep: Wrote the survey questions. | |
| 5Log entry: Worked on the app. Next: keep going. | EComparing actual progress with the plan and recording why they differ | |
| 6Week 4: Everything went fine. (Actual progress: 2 of 6 tasks, planned: 6 of 6) | FThere is no date, no detail about what was done, and the next step is vague. |
C
Definitions
project log
D
Fill in the Blanks
Complete each line of code by filling in the missing parts.
1.
____: 12 March
Done: Drew the app wireframes
Next step: Build the login page
2.
Date: 14 March
_______: Login button did not work
Fix: Renamed the button ID
3.
Date: 19 March
Done: Tested the quiz screen
_________: Fix the scoring bug
4.
Planned: 5 tasks done by Friday
______: 3 tasks done
Change: Move testing to Week 4
5.
Planned: 5 tasks
Actual: 3 tasks
Tasks behind: _
E
Spot the Error
Shade in the letter of the line that contains an error.
Question 1
A
Date: 12 May
B
Done: Wrote survey questions
C
Problem: stuff went wrong
D
Next: Fix the submit button
Question 2
A
Date: 14 May
B
Planned: Finish menu page
C
Actual: Finished half of it
D
Next: Nothing, I am done
Question 3
A
Date: sometime this week
B
Done: Drew app wireframes
C
Problem: Colours hard to read
D
Next: Test new colour pairs
Question 4
A
Date: 21 May
B
Done: Coded the quiz scoring
C
Problem: Score showed NaN
D
Fix: Nothing, ignored it
Question 5
A
Date: 26 May
B
Done: Will test game levels
C
Problem: Level 3 too hard
D
Next: Lower enemy speed
Answer Key
Tracking progress with a project log
Section A: Quick Questions
Q1
A — 12 May: Built the login page. Problem: button did not submit. Next: fix the form code.
Q2
B — The date of the work session
Q3
A — The problem and how you fixed it (or what you will try next)
Q4
B — Actual progress was behind the planned progress
Q5
A — In a dated project log entry that explains the problem and the change
Section B: Match the Pairs
Q1
12 Aug: Built login page. Problem: button did not work. Fix: renamed the ID. Next: test with users. → A complete project log entry with the date, what was done, a problem and its fix, and the next step
Q2
Planned: 5 tasks done. Actual: 3 done. Reason: testing took longer. → Comparing actual progress with the plan and recording why they differ
Q3
Dated entries let you see when work happened and in what order → Log entry - Tue 3 Sep: Wrote the survey questions.
Q4
Recording a problem and its fix shows how you solved issues and why the plan changed → Problem: images loaded slowly. Fix: compressed the files. Plan: add 1 day for testing.
Q5
Log entry: Worked on the app. Next: keep going. → There is no date, no detail about what was done, and the next step is vague.
Q6
Week 4: Everything went fine. (Actual progress: 2 of 6 tasks, planned: 6 of 6) → The log ignores a problem. Actual progress is behind the plan but no problem or reason for the delay is recorded.
Section C: Definitions
Q1
project log — A record of each work session: the date, what was done, any problems and the next step. It shows actual progress against the plan and evidences why the plan changed.Section D: Fill in the Blanks
Q1
Date: 12 March
Done: Drew the app wireframes
Next step: Build the login pageQ2
Date: 14 March
Problem: Login button did not work
Fix: Renamed the button IDQ3
Date: 19 March
Done: Tested the quiz screen
Next step: Fix the scoring bugQ4
Planned: 5 tasks done by Friday
Actual: 3 tasks done
Change: Move testing to Week 4Q5
Planned: 5 tasks
Actual: 3 tasks
Tasks behind: 2Section E: Spot the Error
Q1
C — A log problem must say exactly what went wrong so it can be fixed and evidenced. It should be specific, like 'Problem: Form would not submit'.
Q2
D — The Actual line says only half the menu is finished, so the next step must be to finish the rest. It should be 'Next: Finish rest of menu'.
Q3
A — Each log entry needs an exact date so progress can be tracked and checked later. It should be a specific date like 'Date: 19 May 2025'.
Q4
D — A fix must record what was actually done to solve the problem. Ignoring it leaves no evidence of a solution. It should be something like 'Fix: Changed text to number'.
Q5
B — 'Done' records work already completed in the session, so it must be in the past tense. It should be 'Done: Tested the game levels'.