Most EdTech brands refuse to answer this question specifically.
They say “it depends on the child.” They say “every learner is different.” They hedge and qualify and never commit to a number. The effect is that a parent trying to evaluate whether a course is worth the time investment has no concrete information to work with.
This article does what most do not: it gives you a specific, honest timeline. Week by week. What your child can realistically do at each stage. What progress looks like at the thirty-day mark and the sixty-day mark and the completion of a full course.
This timeline is based on the typical experience of children aged 8 to 12 at Chitti Future School. Younger children move slightly more slowly. Older children move faster. But the sequence is consistent regardless of age. The what always happens in this order. The when varies by roughly thirty to forty percent.
Week 1: The Sprite Moves
By the end of Week 1, your child can make a character move on
screen in response to keyboard input. They can change the character’s costume. They can add a sound that plays when a key is pressed. They can make something happen on a computer screen because of something they built.
This sounds modest. It is the foundation of every interactive program ever made. Input, response, feedback. Your child now has all three.
The visible change in your child by Week 1: they will try to explain to you what a sprite is. They will use the word “program” to describe what they built. They have a new vocabulary for something they made. This is the beginning.
Week 2 to 3: The First Game
By the end of Week 3, your child has built a working maze game with collision detection and a win condition. This is, by the functional definition of the word, a game. A player (the character), a goal (reaching the end), rules (touching walls returns the character to start), and a win condition (reaching the exit produces a message).
The maze project is where most children first encounter the debugging experience: their program does something wrong, they figure out why, and they fix it. This process, which sounds like a problem, is the most valuable activity in the course.
The visible change by Week 3: your child will come home and describe a problem they solved rather than something they saw or were shown. The language shifts from passive to active. They stopped watching the course happen. They started driving it.
Week 4 to 6: Variables and the Race
By Week 6, your child has built a race with two programmable characters, a variable-based score or winner system, and timing-dependent logic. They understand what a variable is not because they read a definition but because they built one, named it, and watched it change while their program ran.
Variables are the conceptual leap that determines whether a child can build genuinely sophisticated programs or only simple ones. A child who understands variables can build almost anything. A child who does not is limited to pr
ograms where nothing needs to be remembered between moments.
The visible change by Week 6: your child asks different questions about programs they encounter. “How do they make the score count?” “What happens when you lose a life?” “How does the game know when you win?” They are thinking about the systems behind things, not just the things themselves.
Week 7 to 8: The Spooky Forest — Design Thinking Begins
By Week 8, your child has built a maze with moving obstacles and has revised it based on watching someone else play it. They have been a designer, a programmer, and a user-researcher in a single project.
This is the point in the course where children begin to think about the experience of the person using their program rather than only about the technical function of the program. It is the beginning of empathy-driven design. For an 8 or 9 year old, this is a significant cognitive development.
The visible change by Week 8: your child will describe their project in terms of how someone else will experience it. “I made this part harder.” “I added a sound so you know when you die.” “I tested it on Amma and she said this bit was confusing, so I changed it.” They are thinking like a designer.
Week 9 to 10: The Interactive Story — The Full Creative Arc
By the end of Week 10, your child has completed an interactive story with branching narrative paths, multiple scenes, and dialogue they wrote and programmed. They have driven a creative project from concept to completion, managing all of the technical and creative challenges that arose along the way.
This is the project that most clearly reveals what the course has built. The child who completes an interactive story has demonstrated sequential thinking, conditional logic, debugging, creative decision-making, follow-through, and the ability to translate their internal vision into a working program.
The visible change by Week 10: your child has a portfolio. Six working projects. A maze, a race, a spooky forest, an interactive story, and several others. All of them running. All of them theirs. And the specific confidence of someone who has made things that work.
The Honest “It Depends” Addendum
There are three variables that affect this timeline.
Age: A 13-year-old moves through the foundational concepts in roughly half the time of an 8-year-old. By Week 5, a 13-year-old may be at the complexity level a 9-year-old reaches by Week 8. Both are exactly where they should be. The timeline compresses, not the learning.
Prior experience: A child who has used coding apps before has familiarity with the interface but not necessarily with the thinking. They may move through the first project quickly and slow down when the thinking demands increase at Weeks 3 and 4. This is normal and productive.
Consistency of attendance: A child who misses two sessions in a ten-week course takes longer than a child who attends every session. The projects are continuous, and a missed session requires a brief catchup that slightly extends the timeline.
These variables exist. They do not change the sequence. Every child who goes through the course goes through the stages in the order described here. The timing varies. The journey is consistent.
Ajitesh V Kumar, a student at Chitti Future School, went
through this timeline. At Week 1 a sprite moved. At Week 3 a game worked. At Week 10 a complete interactive story ran. And then the thinking that the timeline had built showed up at the All India Maths Based Finance Olympiad, where he won, drawing on the systematic, patient, first-principles reasoning that ten weeks of Scratch had built in him.
His parents did not need to wait for the Olympiad to see the progress. The progress was visible every week. Exactly as described in this article.
The timeline is clear. The first step is a free demo at Chitti Future School. Take it today
