AP CSP - Sprint Reflection
Categories: PersonalPersonal Achievements in Sprint One and Goals for Sprint Two
๐ Sprint Reflection
This notebook documents my personal achievements from Sprint One and sets goals for Sprint Two. It serves as both a record of progress and a guide for my continued growth as a collaborator and developer.
๐ Sprint One Achievements
During Sprint One, I built a strong foundation in both technical and collaborative areas. Here are my accomplishments, in order:
- Getting past tools and make
- Learned how to use essential tools and commands in order to open VSCode properly and get started with my Sprint One journey
- Got past the struggle of learning how to run make while also changing the theme
- Creating a personal repository
- Built my own repository with interactive buttons and a personalized About section
- Changed the font and buttons of the main page so it looks more aesthetically pleasing to me
- Learning how to transfer files from one repository to another
- Practiced moving files across repositories, an important skill for version control and collaboration
- Learned how to open two repositories at the same time to easily move one file to another
- Also learned how to git pull when the
pagesrepository is updated.
- Getting into groups in order to work on projects
- Joined a group project and practiced collaboration with peers.
- Organized a board of ideas and things to do in groups
- Created issues to organize ideas and to also assign people to certain jobs
- Working on game hacks with a group and having them graded
- Contributed to game hack projects, reinforcing both coding and teamwork skills.
- Agreed with group on what games to do, making sure that we donโt do the same hacks
- Working on a โgamifiedโ lesson to teach others how to make with a theme
- Designed an engaging, theme-based lesson to introduce new learners to making concepts.
- Created steps to create the process of making this game
- Although the game was not officially โfinishedโ, that just means that we have more things to work on
- Game still worked pretty well, the visual of it was good
M&M Gamified Lesson
This was a big part of sprint one, since this was the project that we spent the most time on. We created a game that would make learning how to make while also changing theme understandable but not boring to learn. I created the steps and worked with team members to make the โplotโ for the game, what we wanted to happen and what we wanred to put into the game so that the player would learn.
๐ฏ Sprint Two Goals
For Sprint Two, I want to deepen my coding skills and strengthen my teamwork. My personal goals are:
- Continue to work on teamwork and communication
- Build stronger collaboration with peers by being more engaged and supportive.
- Continue to create issues and start assigning people to do certain things
- Communicate with others to make sure they are doing what they are supposed to do
- Encourage the team to create forks of their repository
- Guide teammates toward better version control practices (forks and pull requests instead of only using
git pull). - Mr. Mortensen mentioned that we should instead have each of the team members creating their own forked repo to the main repository so we donโt have to keep telling each other when we are changing things
- Guide teammates toward better version control practices (forks and pull requests instead of only using
- Stay connected with the team
- Avoid isolating myself and work more closely with the group.
- Help group members when they need help
- Make sure to keep an eye on the team, making sure they are keeping up and they understand what they are doing
- Learn essential coding concepts in JavaScript and Python
- Strengthen my foundation in both languages to prepare for more complex projects.
- Pay attention to all the lessons coming up in sprint two, do the hacks they might give in order to understand python and javascript more
- Create three lessons on coding concepts in JavaScript and Python
- Share my knowledge by designing clear, accessible lessons.
๐ Comparison: Sprint One vs. Sprint Two
| Sprint One Achievements | Sprint Two Goals |
|---|---|
| ๐ Mastered tools & make | ๐ค Improve teamwork & communication |
| ๐ Built personal repo | ๐ง Encourage forks & PR workflow |
| ๐ Transferred files between repos | ๐ฅ Stay engaged with team |
| ๐ค Joined project groups | ๐ป Learn coding concepts (JS & Python) |
| ๐ฎ Completed game hacks | ๐ Create three coding lessons |
| ๐ Designed a gamified lesson | โ |
โ Closing Thoughts
Sprint One allowed me to establish a foundation in tools, repositories, and group collaboration. For Sprint Two, I aim to evolve into a stronger collaborator, coder, and teacher. By staying connected with my team, learning new coding concepts, and creating educational lessons, Iโll continue to grow and prepare myself for future challenges.