Switch course ▾
Session 4. Milestones, Check-ins and the Timetable
Objective. Build a calendar for a two-to-four-week project from the lessons you really have, set milestones that show finished work, and run short check-ins.
Most projects that run late did not fail in the last week; they slipped in the second. The calendar looked fine on paper, then a holiday, an inspection and a sick team member took three lessons. This session shows how to count lessons honestly, set milestones that make delay visible early, and run check-ins that take two minutes, not twenty. The aim is a project that finishes on a day pupils and visitors can rely on.
Key ideas
Count the lessons you really have
- Open the timetable and the school calendar. Cross out holidays, inspections, concerts, exams and trips. Two lessons a week for four weeks is 8 on paper and often 6 or 7 in practice.
- Choose a length that fits: two weeks for a first project, three or four for a deeper one. Longer projects lose pupils' energy.
- Keep one lesson as buffer. Use homework for reading, interviews and drafts; use lessons for what needs you and the team together.
Milestones that show finished work
- A milestone is a dated point where a team can show something done: a signed plan, a first draft, a prototype, a rehearsal.
- A good 3-week rhythm: Launch, Learn and plan, Build, Draft check, Feedback and revise, Showcase.
- Put the milestone dates on the wall where every team sees them. Late milestones are the earliest warning that a team is in trouble.
Short check-ins
- Spend about two minutes per team at the start of a work lesson: What did you finish? What is next? What is in your way? What does each person do today?
- With seven teams that is 14 minutes, too long. Check three teams at the start and the rest during work, a different three each lesson.
- Write one line per team in a notebook. After two weeks the notes show who needs help before problems grow.
Feedback, revision and falling behind
- Plan one round of feedback before the showcase: a team shows its draft, another team says one thing that is clear and one that is not.
- Use the rule: kind, specific, useful. 'The map is nice' is kind but not useful; 'the key does not say what red means' is all three.
- If a team is behind, cut scope, not quality: a smaller product that meets the outcome beats a large unfinished one.
A three-week project rhythm
Planning backward from the showcase date
Fix the showcase date first, then count back. Give the last two lessons to revision and rehearsal, one lesson to peer feedback, and keep a buffer. What remains is your build time, often only three or four lessons. Seeing that number early stops you from planning a product that needs eight.
Choose milestones that produce something you can see in under a minute: a signed plan, a first draft page, a labelled sketch, a table with data. 'We have started' is not a milestone. Write each on the wall with its date. If a team misses one, you have the early warning you need while there is still time to cut scope.
Check-ins in a class of 28
Seven teams at two minutes each cost 14 minutes, so split them. At the start of the lesson, ask three teams the four check-in questions standing by their desk. Walk past the others during work. Next lesson, take a different three. Use a one-line note: date, team, what is next, what is in the way. Over two weeks you have a record of every team.
Teach teams to run their own mini check-in too: the coordinator reads the milestone list aloud at the start and the recorder writes the day's goal in the log. A middle-school teacher in an Edutopia article uses a task board and regular reflection sessions in the same spirit. When teams manage themselves for the first five minutes, your time is free for the team that is stuck.
Examples from the classroom
Eight lessons that became five
Scene. Jasur teaches Grade 8 Uzbek literature in Tashkent, two lessons a week for four weeks. He crosses out an inspection, Navruz and a class trip, leaving five lessons. He moves reading and first drafts to homework, keeps one lesson for feedback, and shrinks the product from a four-page newspaper to two pages. The showcase happens on the planned day.
Insight. Counting real lessons before launch let him cut scope calmly instead of in a panic.
Week two warning
Scene. Dilnoza's Grade 5 teams in Samarkand are due to show a plan at the end of week one. At the Thursday check-in two of seven teams show nothing. She sits with each for five minutes, helps them split the plan into three tasks and moves their next date by one lesson. Both teams finish on time.
Insight. A dated milestone exposed trouble early enough for a small fix.
Smaller but finished
Scene. Aziz's Grade 6 team in Bukhara wants a map of 12 historic buildings but has time for 6. At the check-in he asks, 'What is the smallest map that still shows the outcome?' They choose six buildings, each with a one-line fact and a distance in steps. The final map is simple and correct, and it is finished the day before the showcase.
Insight. Cutting scope kept the quality of the learning; cutting quality would have lost it.
Common pitfalls
- Planning every lesson as a work lesson, with no buffer for holidays, inspections or illness.
- Setting milestones such as 'work on the poster' that show nothing and cannot be checked.
- Holding long check-ins with every team every lesson, so the lesson is used up by talking.
- Rescuing a late team by doing the work for them, so the pupils learn nothing from the delay.
Build the Calendar
- Read the timetable sheet in the Activity Kit: Grade 6 natural science, two lessons a week for four weeks, with three lost lessons.
- In pairs (20 min): mark the lost lessons, then decide what happens in each remaining lesson and which homework carries reading and drafts.
- Mark three milestones with what the team shows, and one buffer.
- (15 min) Swap with another pair. The reader plays a team that is one lesson behind: what do you cut from the product, and what stays?
Your facilitator will guide you through this activity in the session.
Questions to discuss
- Where was the calendar most fragile, and what protected it?
- What did you cut when the pair was one lesson behind?
- Which check-in question would have shown a problem earliest?
Reflect
- How many lessons does your next unit really have?
- What could your pupils do at home for 20 minutes without parents' help?
- Which milestone would you set first, and what would a team show?
Try it tomorrow
- Count the lessons you really have for your next unit and write the number at the top of the calendar.
- Set three dated milestones and write on each what the team will show.
- Run a two-minute check-in with three teams and keep a one-line note for each.
Further reading and links
Plan from the lessons you really have, set dated milestones, check in for two minutes, and cut scope, not quality.