How to Plan a Six Week Coding Club Project Beginners Finish

The first long coding club project I ran had eleven students on day one and four on demo day. The idea was great: a text adventure in Python with branching stories. The plan was not. By week three, half the group was stuck on a bug nobody understood and the other half had quietly started building something else. A coding club project that lasts more than a couple of sessions needs a shape, and I had given it none.

Since then I have run nine six-week projects with mixed groups of beginners, and the finish rate has climbed to roughly four out of five students. Nothing about the code got cleverer. What changed was how I planned the weeks, sized the tasks and handled the moment every project hits where motivation dips.

Why Six Weeks Is the Right Length for a Coding Club Project

Shorter projects are easier, and we run plenty of them, but they rarely give students the experience of building something bigger than one sitting. Longer projects lose people to exams, holidays and boredom. Six weekly sessions of about 90 minutes gives you around nine hours of building time, which is enough for a beginner to make something they are proud of and short enough that the finish line stays visible from the start.

If your club meets twice a week, compress it to three weeks. The structure below still works; what matters is the number of sessions, not the calendar.

Pick a Project With a Working Version on Day One

The single most useful rule I follow: by the end of the first session, every student must have something that runs. Not finished, just running. A text adventure with one room. A quiz with one question. A drawing program that draws one square.

Projects that fit this rule well:

A quiz game that grows from one question to a scored round with a high-score file.
A text adventure that grows from one room to a small map with items.
A turtle art generator that grows from one shape to patterns driven by user input.
A club helper bot for the terminal that answers questions like "when is the next meeting."

Avoid anything that needs setup before it shows a result, such as a web app with a database. Students who see nothing for two weeks stop coming. If you want options that suit different levels in one room, our list of coding club projects that work with mixed skill levels is a good place to choose from.

A Week by Week Plan

Here is the outline I hand out on day one, using the quiz game as the example. Printing it matters. Students like being able to tick off weeks.

Week	Goal	New idea introduced
1	One question that says right or wrong	input, print, if
2	Five questions and a score	lists and loops
3	Questions loaded from a file	reading files
4	Catch-up and one personal feature	none, on purpose
5	High scores saved between runs	writing files
6	Polish, test with a partner, demo	none

Week four is the important one. It looks wasteful on paper, but it is where students who fell behind recover and where fast students add a timer or a category menu. Without it, the gap between the quickest and slowest grows every week until the slow group gives up.

Break Every Week Into Three Small Tasks

A goal like "add a score" is too big for a beginner to start on. I split each week's goal into three tasks, each something a student can finish in about 20 minutes:

Make a variable called score that starts at zero.
Add one to it when an answer is right.
Print the score at the end.

Each task is written on a card. Students flip the card over when it works. It sounds childish, and teenagers love it anyway. The skill underneath is the same one we teach in how to break a coding problem into small steps, just done for them at first and by them later.

The Advice I Stopped Following

A lot of guides on club projects say to let students choose their own project from the start, because ownership drives motivation. I tried it twice. Both times, roughly a third of the group spent the first two sessions choosing, and several picked ideas far beyond a beginner's reach, like an online multiplayer shooter.

Ownership does matter, but it works better later. Everyone builds the same base project for three weeks, then week four is where they make it theirs. By then they know enough to judge what is realistic. One student turned the quiz into a football trivia game with team badges drawn in text characters. She would never have got there if she had started from a blank file.

Handling the Week Three Slump

Nearly every long project loses energy around week three. The novelty is gone and the end is not close yet. A few things help:

Show progress. Run a few students' week one programs next to their current ones on the projector.
Pair the stuck with the steady. Not the fastest student, who will just take the keyboard, but someone one step ahead.
Cut scope openly. Tell the group that if file loading is a struggle, hard-coded questions are fine for the demo. Finishing beats perfect.
Message absent students. A short "we missed you, here is the task card" brings back about half of them.

Make Demo Day Low Pressure

A full-room presentation scares off the quieter students, and some will skip the last session to avoid it. Instead, run a gallery: laptops open around the room, half the group walks around trying projects while the other half explains theirs, then swap after 15 minutes. Invite a parent or another club if you can. Everyone gets an audience, and nobody stands alone at the front.

Keep one rule for the demo: every project must run without the mentor touching it. That small standard gives students a clear and achievable definition of done.

Frequently Asked Questions

What if a student joins halfway through?

Give them the week one and two task cards and a partner for the first half of the session. Most beginners can catch up two weeks of cards in one sitting, because the early tasks are small.

Should students work alone or in teams?

Alone, with a seat partner to ask first. Teams of beginners usually end up with one person coding and others watching. Shared projects work better once everyone can write a loop without help.

How do I handle a student who finishes in week two?

Give them a stretch card, such as adding a timer or random question order, and ask them to help test a neighbour's code. Testing other people's work teaches them more than racing ahead alone.

Your First Step for Next Term

Pick one project that runs on day one, write the six-week table, and split week one into three task cards. That is an evening's work, and it is most of the difference between four finishers and nine. You can find more project ideas and formats in our club projects section.