Sprint 2 Retrospective Review
Review of MCQ practice and the past 8 weeks
Past 8 Weeks
The past eight weeks have been very productive and fruitful as they were the first eight weeks of the year altogether. Here are the things we have done and finished throughout the past eight weeks!
Sprint 1: Setting Up Tools & Work Habits (Weeks 0–4)
During the first four weeks of school, we focused on getting initialized and setting up tools like VS Code and GitHub.
Initial Capstone Ideation
Our group decided to inherit the ACS capstone project.
Target Audience
Cancer patients in need of a safe space and those involved with cancer patients who would like to learn more (like mothers and fathers)
Objective
Users need a safe space where people understand what they are going through and can learn more about cancer because younger generations usually aren’t aware of how cancer works at a biological level, leading to a lack of understanding of what cancer patients go through.
Success Statement
We know this works when we have a website where people can not only learn about cancer but also connect and ask questions.
Scope
This project will not include excessive educational content.
Sprint 2: Full Stack Foundations (Weeks 5–8)
Sprint 2 had more of a workload, with more projects and more coding.
Toggles Lesson
I enjoyed the toggles lesson because it taught me more about Sass and how it works, while also introducing something fun and unique.
Lesson Plan
- Introduction: Explain what toggles are and where they are used, such as notifications, settings, and turning features on or off.
- OCS Sass Version: Introduce the OCS Sass system and explain why reusable classes are preferable to writing custom CSS every time.
- Creating a Toggle: Demonstrate the basic structure of a toggle before introducing labels and checked states.
- Code Runners: Allow students to edit examples and test their code using starter code.
- UI Runners: Let students see and interact with the toggles they create.
- Accessibility: Cover labels, keyboard usability, visible focus, and accessible names.
- Using OCS Sass: Explain preference variables such as
--pref-text-color,--pref-accent-color,--ui-bg, and--ui-border. - Practice: Have students create a small settings section with two or three toggles, labels, a default checked state, and an OCS card.
Keeping the Lesson Easy to Follow
We will introduce concepts gradually, keep examples short, explain new classes and Sass variables before using them, and use code and UI runners to help students understand how their changes affect the interface.
What Makes This Better
The original lesson mostly shows different toggle options. Our version explains the purpose of each part, uses the OCS Sass system, includes interactive code and UI runners, and gives students opportunities to practice.
Expected Result: Students should be able to create a simple, reusable toggle using OCS Sass, keep it accessible, test their code, and see how it works in the UI runner.
Frontend and Backend
We learned a little about managing the frontend and backend of our capstone projects. They are interesting because they rely on ports and can connect to one another without a manual trigger each time.
APIs
We briefly touched on APIs in class and how they work in the backend. My understanding of them is still developing because this is my first time hearing about and working with them.
What we plan to do with APIs:
- Store usernames and passwords.
- Develop a cancer risk assessment.
- Continue brainstorming additional uses.
Practice Multiple Choice Quiz
Overall, I received 54/66.
Topics to Work On
These are the AP CSP topics where my performance was below 75% in the results report:
- 2.4 — Using Programs with Data (50%): Review this topic more.
- 3.6 — Conditionals (50%): Get more practice with this topic.
- 3.9 — Developing Algorithms (50%): Work on understanding this topic better.
- 3.15 — Random Values (50%): Spend some more time reviewing this.
- 4.1 — The Internet (67%): Review the main ideas.
- 4.2 — Fault Tolerance (0%): Practice this topic more.
- 5.1 — Beneficial and Harmful Effects (67%): Keep working on this area.
- 5.6 — Safe Computing (67%): Review this topic some more.
Goal: Focus my studying on these topics and practice applying each skill to new problems. I can review the questions I missed, revisit class notes, and do a few extra practice problems to see which areas still need work.
Main Areas for Improvement
| Focus Area | How I Can Improve |
|---|---|
| Time Management | Plan ahead and avoid rushing assignments. |
| Problem Solving | Work through difficult problems more independently. |
| Coding Skills | Practice more advanced concepts and learn how code works. |
| Debugging | Find and fix errors more efficiently. |
| Communication | Share my ideas and ask questions more often. |
| Teamwork | Contribute ideas and communicate with my team. |
| Organization | Keep my files and work organized. |
| Learning from Mistakes | Use mistakes to understand what I can do better. |
The past eight weeks have been very productive and fruitful as they were the first eight weeks of the year altogether. Here are the things we have done and finished throughout the past eight weeks!