AI-generated content. This lesson was generated by AI and is posted as generated. AI can make mistakes. Check your teacher’s instructions and official sources.
Grade 8 learning series · Lesson 3 of 4
Turn a group idea into a manageable plan, track what actually happens and verify the final submission.
Tutorial and Q&A · Practice exercises · Assessment · Project · Instructor notes
Tutorial
By the end, you should be able to:
- Distinguish a proposal, a milestone, a log plan and a log entry.
- Give every task an owner, a checkpoint and a way to tell when it is done.
- Revise a plan after a setback and record changes honestly.


Write a proposal someone could act on
A proposal says what you will make, why it matters, who it is for and how you will complete it. A deliverable is what you hand in or present. “We will teach people about flooding” is an idea. “We will make a one-page poster for Grade 8 students with a labelled map, three safety tips from a reliable source and a source credit” is a deliverable you can check.
For each major task, record an owner, a due time and a sign that it is ready. Everyone can help, but one person should make sure the task moves forward. The file owner or submitter is an administrative role, not proof that one person did all the work.
Work backward and name dependencies
A milestone is a checkpoint you can recognize. “Complete the map and verify its legend before drafting the caption” is better than “work on the map.” A dependency is a relationship between tasks. If your caption needs labels from the map, drafting the final caption depends on having a usable map.
Example: the poster is due on Day 5. Day 2 is for source selection. Day 3 is for a full draft. Day 4 is for a partner check, fixing the layout and testing access. Day 5 is for submission and verifying that it went through. A time buffer is useful because things like broken links can take longer than expected.
Plan the log, then record what happens
A log plan says when entries will be made, who records them, and what details to include. A log entry records what actually happened. A simple format is: date or session, contributor, work done, evidence or file location, obstacle, and next step with an owner.
Model log plan: “At the end of each session, each task owner adds one update to the shared log. The coordinator checks that every entry has a next action.” Model entry: “Day 3, map lead: placed the revised map on draft page 1. A teammate could not read two labels. Next step: map lead enlarges the labels before the Day 4 review.”
Before turning in, identify the authorized submitter and use the teacher’s templates and instructions. Check the correct files are attached, test access, confirm the submission, and follow any separate turn-in step for other members. Do not post private class files or make them public just to fix a sharing issue.
Video to watch
Michigan Learning Channel: How Teamwork Works. Watch for one example of how a team coordinates individual contributions. Turn that example into a rule for your group.
Tutorial Q&A
How is a proposal different from a log? The proposal says what you intend to do. The log records what you did and what changed.
Do all roles need the same amount of work? Not exactly, but the group should check whether the effort is fair and whether everyone can explain a contribution.
What if we discover a source is wrong? Record the issue, find a reliable replacement, tell the person whose work depends on it, and update the checkpoint.
Does uploading a file to Drive count as submission? Not necessarily. Check the assignment’s required submission steps and verify the final status.
Practice exercises
Try these first. You may look back at the tutorial while you practise.
- Rewrite “We will make a great poster” as a deliverable with an audience and three checkable features.
- Put these in a sensible order and name one dependency: present, verify sources, rehearse, finish slides.
- Turn “we worked on slides” into a log entry with a contributor, evidence, obstacle and next step.
- Create a Day 1–5 schedule that leaves a buffer before submission.
- Write a polite one-sentence update to your group explaining that a blocker will affect one task.
Show practice answers and examples
- Example: “A one-page classroom poster with a labelled diagram, two explanations and three source links.”
- One sensible order is verify sources, finish slides, rehearse, present. Rehearsing from the final slides depends on getting them ready.
- Example: “Day 3, slide editor: added the map to slide 2. The source link was broken. The researcher will replace it before rehearsal.”
- Check that the review is scheduled before the final due date, with time to fix something.
- Example: “The map link is unavailable, so I’ll use our backup and update slide 2 by tomorrow.”
Independent assessment — 15 marks
Suggested time: 20 minutes. Work independently without the tutorial or the practice answers. Keep the marking guide closed until you finish.
- A team proposes “a slideshow on the water cycle.” Write a more usable deliverable and include an audience and two checkable features. (4)
- Put four tasks in a sensible order, name two checkpoints, and explain one dependency for a three-day poster project. (4)
- A group member’s source image cannot be opened on Day 2. Write a log entry with the known event, evidence location, blocker, and next action with an owner. Do not pretend the problem was solved. (4)
- Name three checks a group should make before or immediately after turning in. (3)
Show assessment marking guide
- 1 for a specific product, 1 for audience, and 1 for each checkable feature.
- 1 for a usable order, 1 per checkpoint, and 1 for explaining a real dependency.
- 1 each for a factual event, location, blocker and actionable next step with an owner.
- 1 per distinct valid check, such as correct files, access permissions, authorized submitter, submission confirmation, or required individual action.
Project — 12 marks
Design and manage a team mini-project
In a team of two to four, create a one-page guide that teaches a school skill. Submit a one-page proposal with roles, three checkpoints and a contingency. Include a log plan, at least three dated entries, the final guide, and a short individual reflection. For a solo version, use roles such as researcher and reviewer and log when you switch roles.
Project scoring guide
- Clear deliverable, roles and feasible checkpoints (4)
- Honest log entries with evidence and next actions (4)
- Usable final guide plus a submission and reflection check (4)
Instructor notes
- Use the class templates where provided. The sample is about transferable planning skills and is not a copy of the class documents.
- Look at the individual reflection and log together. Early, honest identification of a blocker is good project management, not a reason by itself to penalize a team.
- For a quick formative check, give students three vague tasks and ask them to add an owner, deadline and definition of done.
