Did you know? A class can spend three afternoons working hard and still be unable to open its exhibition booth on time. Everyone may have completed a task, yet nobody prepared the one file the printer needed. The missed step is not necessarily laziness. Sometimes the team has never given the different parts of the work their proper names.
The useful answer is four words: a task is an action somebody does; a deliverable is a verifiable thing or result the project must produce; a milestone marks a significant point of progress; and a dependency is a relationship in which one piece of work needs something from another. Learning these words helps students decide what to do, what must exist at the end, which checkpoint matters and what cannot yet proceed.
A group project is a small model of adult work
Imagine a Secondary 2 team preparing a school science exhibition about safe water use. One student draws diagrams, another checks numerical examples, a third writes explanations and a fourth coordinates the display. At first they say, ‘We have to finish the poster.’ That sounds like a plan, but it hides four questions: What actions remain? What exactly must be handed in? When will a reviewer approve it? And which action has to happen first?
School projects provide a friendly practice ground for language used later in polytechnic assignments, university research, community events, engineering, design, healthcare administration and office work. The same reasoning matters even when the software changes from a paper checklist to a project-management app.
Task: the work somebody actually does
A task should be an action that can be assigned and checked. ‘Research’ is too vague to guide a group for long. ‘Find two authoritative sources about water conservation, record the URLs and extract one checkable claim from each’ is more useful. The wording names an action, its scope and the evidence that it happened.
In grammar terms, useful tasks begin with precise verbs: calculate, interview, sketch, measure, draft, verify, revise, print. The verbs are not interchangeable. To verify a fact means checking it against evidence; to draft a paragraph creates a first version, not proof of factual accuracy. If the team writes ‘done’ beside a draft, someone must still know whether revision and approval remain.
Deliverable: the thing somebody can inspect
A deliverable is the output the group is committed to produce. For this class it might be a printable A3 poster, a short oral script, a data table with labelled units and a bibliography. A deliverable may be digital, physical or a documented service result. What matters is that another person can tell whether it meets the stated conditions.
Consider the sentence ‘Aisha has completed two hours of research.’ That describes effort, not necessarily a deliverable. ‘Aisha submitted a source table with author, date, URL and the exact claim each source supports’ gives the team something to use. The work may have taken less time or more time; quality cannot be inferred from hours alone.
The pairing acceptance criteria is important. A poster can exist without being acceptable. Example criteria might be: all measurements have units; images are licensed for the intended use; the claim about water is supported by a named source; and text remains readable from the intended viewing distance. Criteria should be settled before ‘finished’ becomes an argument.
Milestone: a meaningful checkpoint
A milestone is not merely another item on a to-do list. It marks significant progress, such as ‘research plan approved’, ‘first complete poster reviewed’ or ‘exhibition materials accepted by the supervising teacher’. A team may mark a milestone on the day it is achieved, even though the tasks leading to it took several days.
A common mistake is treating every tiny action as a milestone. If ‘open the document’, ‘change the font’ and ‘save the file’ are all called milestones, the word loses its ability to show what stage the project has genuinely reached. Ask what important new state became true after this event. If there is no meaningful change, it may simply be a task.
Dependency: the invisible connection that causes delays
A dependency explains a sequence. The printing task may depend on receiving an approved final PDF. The final PDF may depend on a complete chart. The chart may depend on verified measurements. When one predecessor is late, several later tasks can become blocked. Students need not master specialised scheduling software to understand the logic.
Notice that a dependency is not the same as a due date. A due date says when something should be completed. A dependency explains what must happen first or together. Some work can proceed in parallel: one pupil may draft a presentation while another checks calculations. Other work, such as printing the final poster, must usually wait for the agreed file to be approved.
Worked example: why the poster cannot be printed on Thursday
This is a hypothetical classroom schedule, not a record of an actual eduKate student or school event. The teacher wants the science display ready for Friday. On Monday the team plans to finish research by Tuesday. Data checking is estimated to take one day after the research table is ready. Layout needs the checked figures. Printing needs the final approved PDF.
- Monday — tasks: identify two reliable sources, outline the experiment and decide who verifies measurements.
- Tuesday — deliverable: source table and labelled observations submitted for checking.
- Wednesday — milestone: verified evidence and layout approved for final production.
- Thursday — dependency: printing can begin only after the approved PDF exists and the printer’s specifications are confirmed.
- Friday — outcome: the display is available for the audience; this outcome is not identical to the printer receiving a file.
Now imagine the source table arrives late on Wednesday. Students may say ‘Printing is still scheduled for Thursday,’ but the date alone does not make the predecessor complete. A truthful project message is: ‘Poster printing is blocked by the unchecked data table. We can finish the title and layout while the figures are verified, but we cannot approve the numerical claim yet.’ This is the practical power of the preposition by in blocked by: it identifies the condition without blaming a person.
Word relationships that improve project communication
Build a small vocabulary network. Deliver is the verb, delivery the event, and deliverable the output. Depend leads to dependency, dependent on and independent of. Complete can be contrasted with submitted, reviewed and approved. In a professional register, ‘pending approval’ is not a polite way of saying ‘approved’. The difference affects real decisions.
A useful sentence frame is: ‘The [deliverable] is [status] because [dependency]; [owner] will [next action] by [date].’ For example: ‘The poster is under review because the chart units have not been verified; the data reviewer will check them by Wednesday afternoon.’ The language is precise without sounding cold or accusatory.
Try a three-question diagnosis
When students say ‘our group project is almost done’, ask: What can I inspect? (deliverable); What significant stage has been passed? (milestone); What is the next task waiting for? (dependency). A team that can answer those questions has a clearer picture of the work than one that merely reports a percentage complete. Percentages are especially misleading when the remaining item is essential.
Here is a short retrieval exercise. Hide the headings, then decide whether each sentence describes a task, deliverable, milestone or dependency. ‘Export the bibliography as a PDF’ is a task. ‘A checked bibliography PDF’ is a deliverable. ‘Research sources approved’ is a milestone. ‘The final script cannot be rehearsed accurately until the data labels are settled’ describes a dependency. More than one idea can appear in a real sentence; explain which aspect you are naming.
How a parent or teacher can help without taking over
- For Primary 5 and 6: start with three columns—‘do’, ‘show’ and ‘wait for’. The formal words can come after the child understands the actions.
- For Secondary G1/G2/G3 learners: ask students to explain a dependency in one plain sentence, then compare what can run in parallel. Choose complexity appropriate to the class.
- For teachers: show one example of ‘busy but not complete’ and one example of ‘approved deliverable’; avoid rewarding status language alone without checking the work.
- For parents: ask ‘What are you waiting for from the group?’ rather than immediately volunteering to finish the poster.
- For older students and interns: combine clear handoffs with a versioned checklist so the person responsible can see which source, file or decision is authoritative.
Common mistakes worth catching early
A milestone is not always a meeting. A deliverable is not necessarily a physical product. A dependency does not mean the next student must stop every other useful activity. An owner is not the same as the only person who may contribute. And an attractive coloured Gantt chart cannot rescue a plan that has no defined output or acceptance conditions. The labels make coordination possible; they do not replace judgement.
Frequently asked questions
Can a deliverable also mark a milestone? Yes. Approval of a finished prototype may simultaneously provide an inspectable output and mark an important phase change. Is every deadline a milestone? Not automatically; a deadline is a time constraint, whereas a milestone signals significant achievement. Do dependencies mean one student caused a delay? No; they describe relationships among work items, not moral responsibility. Do younger pupils need project-management software? No. A paper checklist with arrows often teaches the mechanism more clearly.
Connect the learning, not the article count
The existing eduKateSG article on Responsible, Accountable, Consulted and Informed roles explains who does and approves the work; this page explains what must be produced and what depends on what. Explore the Vocabulary Learning Hub for the larger habit of connecting words to real thinking. For definitions and planning context see Atlassian’s guide to work breakdown structures and its guide to project dependencies. The goal is not to make children speak like office managers. It is to help them finish meaningful work together—and explain where the next step belongs.