Team Teach Planning

[KinetekEnergy]

Details

Description:

This document will be for planning our group’s presentation on College Board’s AP CSA Unit 5. It will be done in markdown format on this google document first so that all group members can work at the same time without causing merge conflicts, and pasting it into a notebook will be easy.

Group members:

Aashray, Lilian, Matthew, Tara, and Trevor

Scrum master: Matthew

Template: Unit 5 Lesson Base

Version Control Practices

• Team Practices to Ensure Minimal Conflicts + Easy Debugging

  • Small incremental changes that can be easily and quickly tested to check the validity of the code. If something goes wrong, we can simply revert to a previous version utilizing GitLens. Also decreases the likelihood of integration conflicts because changes will be easier to track down and commits will be more specific.

  • Pull Requests: Once commits are made, pull requests will give a descriptive overview of what task was completed in the fork/branch. Each pull request should be reviewed by a peer.

    • To make a good pull request: Github Docs
    • Commit messages: Properly documented changes in the form of descriptive messages
      • Feat: new feature
      • Fix: bug fix
      • Test: testing
      • Format: <type>: <description>
        • EX: feat: added user authentication & each user can only react to a poll once
    • Make very small commits, only completing one task or one fix. Makes it easier to make code reviews and reverts easier
    • Make sure commits are grouped based on context. Make two separate commits if they are doing two separate things \

  • Code Reviews

    • Branching: Ask each teammate to cross-check whether a proposed piece of code solves the problem.
    • Pull requests: Matthew will ensure that all pull requests to the portfolio_2025 repository are of quality.
    • No garbage commits.

Member Roles:

Aashray:

• Anatomy of a Class
• Constructors
• Popcorn Hacks

Tara:

• Accessory methods
• Mutator Methods
• Popcorn Hacks

Trevor:

• Writing methods
• Static Variables and Methods
• Popcorn Hacks

Matthew:

• Scope and Access
• This Keyword
• Popcorn Hacks

Lilian:

• Homework
• Accessory methods
• Anatomy of Class

Plan

*Need submenus for each topic

Monday

• Continue making content (Reference Spring Portfolio 2025)
• Finish Watching all CB videos (4 each, 6 minutes → expect about 25 mins/person)
• Draft Popcorn Hacks
• Start Making HW

Tuesday

• Share ideas with the group/receive feedback
• Edit Popcorn Hacks if needed
• Draft Pull Request (Revise if Needed)

Wednesday

• Final Touches
• Polish HW
• Pull request

Thursday (If we do not go first)

• Take learnings from other groups we thought were impressive and edit our presentation if needed
  • New pull request if we do so

[LiliWuu]

What We Did

We all watched the College Board videos to understand our topics and we each completed our respective sections. Each person also did a popcorn hack and made forks to our repository. We then committed our changes and made a pull request to the main repository. To make our project more engaging and visually appealing, we made a Nearpod as the big popcorn hack and we also created a poster.

[TDWolff]

Grow: Maybe work harder for the homework/hack, it is not made yet or is very little done. Maybe include a sub-bar and nav-bar cause that's missing Glow: I like the extra work, and it's very organized, the speaking is pretty good, and the pictures allow for people to be more interested.

[Th35py27]

Glows:

Blog showed good information. I like the theme which feels more engaging

Grows:

Submenu Didn't have any homework on their teach.

[DavidL0914]

Glows:

• Well done with pull requests and having different files for your lesson. Your lesson seems very organized with everything in place.
• Good theme that can help capture student's attention and keep them engaged with lesson/

Grows:

• No submenu to navigate through your different files. Implementing this on your page would be beneficial.
• No homework created yet. Some of the content is a bit long and should be split up and have hacks in between.

[JoshThinh]

Glows

• Included a well-organized with cool pictures that make the team teach more interesting.
• I liked the joke at the beginning grabbing the listeners attention.

Grows

• Include your frq homework hack to help display what was learned during the presentation.
• Images are a bit too big, maybe make it smaller and centered.

[iKAN2025]

Good job with the cohesive theme. Maybe add the paper infographic Tara made to the blog

[SlothInTheHat]

I really liked how you had a minion theme which you kept consistent throughout the whole presentation. I thought it was a good idea to have external multiple choice questions and a poster.

One of the things you could work on is adding the nav bar, and maybe add a homework page where you can have your hacks.

[dylangarrettschool99]

I love the addition of the minions to help keep the audience engaged during the presentation. However, I wish there was a navbar as it makes it easier for people to navigate when they are doing the hacks.