Sprint Schedule
Sprint Overview
A high-level view of the Foundations workload for each student looks like this:
- Students need to have their sprint completed and ready for review by 10 pm on the Sunday at the end of sprint.
- Each sprint includes at least one homegroup check in with your facilitator. Your facilitator will journey with you through this content to support your growth and skill development.
📚 Full-time students
- You have one week to complete each sprint
- Around 40 hours of study per week are required
🕰️ Part-time students
- You have two weeks to complete each sprint
- Around 20 hours per week of study are required
Engaging with the material
Each sprint will have a list of activities to complete. Some of these will be 'primers' - introducing to the context to get you going. Others will be 'challenges' that require you to complete a set of tasks. And some activities will be a combination of both. Some sprints include additional stretch material for those with the time who want to dive deeper.
Activities are in sequential order.
Build good habits
One rule for coding applies, Code Every Day!
Research shows that learning is quicker if you engage every day and avoid periods of inactivity. For example, if you've taken two days out from coding, the time to reorient will be longer than if you had spent 15 minutes coding on each of those days. This maximises the neuroplasticity of the brain - each time you practice something, you are strengthening the related neural pathways, and in turn, improving your skills.
End of Sprint Feedback
After a sprint is complete, you will need to fill out a feedback form. Your feedback influences design and content improvements, as has that from hundreds of students gone before. In addition to feedback being part of our continual improvement framework, it helps us to support you and your development and may at times inform your homegroup sessions. Submit sprint feedback form by 10 pm Sunday at the end of each sprint to signal completion of work.