> For the complete documentation index, see [llms.txt](https://x.ancorasir.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://x.ancorasir.com/me303-311/2020-autumn/project-work/milestone-reflection-in-the-physical-notebook.md). # Milestone Reflection (in the physical notebook) Adapted from Source: ### **Background** Reflection is thinking about a recent experience and linking it to earlier ones. The thinking involves looking for commonalities, differences, and interrelations between the recent experience and prior experience. Critical reflection is an important part of consolidating a learning experience, and we would like to use the results of the project milestone review as an opportunity for such reflection. ![fig-reflections.jpg](https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fliz72SG2VHq4ab4qMVYb%2Fuploads%2FV5lySLFPA9N543Bh6Siz%2Ffig-reflections.jpg?alt=media\&token=96163c29-5703-4667-99ff-47cae09ebaa8) ### **Structure** After each course milestone, we would like you to think about how you and your team performed during the milestone phase. Think about assumptions/expectations that you and your team made going into the milestone phase as well as the actual preparation and review event. After completing the milestone and seeing the results: * what were a few key moments (e.g. challenges, high points) in the milestone phase? * were there assumptions/decisions that were important to your success? * were there assumptions/decisions that you would change if you were to do it again? * what did you learn from seeing the work/presentations of other teams? * what is your take-home message from the phase? ### **Submission** After each milestone review and results, write your reflective thinking in your design notebook. Your instructor will review it at the [next notebook submission.](https://x.ancorasir.com/me303-311/2020-autumn/project-work/deliverable) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://x.ancorasir.com/me303-311/2020-autumn/project-work/milestone-reflection-in-the-physical-notebook.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.