# Pacing Calendar

The Pacing Calendar is an outline of how you may implement this course throughout a given school year. Please use this Pacing Calendar as a “suggested outline” and adapt it to fit your school’s calendar for any given school year and the needs of your students.  For ease, we pretend that there are 4 weeks in each month and acknowledge this is not always true. We also approximated the timing of longer holidays or breaks and know this too may shift from year to year.

We suggest that each project take approximately five weeks to complete - with one week for launch, three weeks for project mode, and a final week for presentations. We also suggest that the Final Project take about three months and can be broken up for students into three MVPs which will each last about a month. While we provide many protocols to help support students with the executive functioning skills necessary for working on a long term project, please feel free to add additional deadlines or expectations that may help support your students.

We also included an optional break for a Midterm Project for teachers that work in schools where midterm projects are an expectation for their classes. Feel free to skip this project if it does not make sense for your students or your school culture.

<figure><img src="/files/EKyX0hPp5B5929Ynm6D3" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://cs4all-icm.gitbook.io/high-school-capstone-computer-science/curriculum-map/pacing-calendar.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.