Project: Whats Cookin'

Group Member Names: Andrew and Taylor

Goals and Expectations for the Project (What does each group member hope to get out of this project? What do we want to achieve as a team? How will we know that we're successful?):

• Group goals
  • Taking the time to have solid plans before work sections
  • pseudocoding when necessary
  • reaching MVP way ahead of time
  • don't overextend
  • be ambitious only if we complete original requirements
  • git hub projects is thorough
• Andrew
  • successful collaboration and organization
• Taylor
  • Work to be focused and intentional

Team strengths & collaboration styles (consider discussing your Pairin qualities here):

• Strengths
  • learning things outside the scope of the project
  • figuring things out independently
• Collaboration styles
  • more time solo in general
  • meet up before doing any work alone
  • not getting ahead of others
  • check in first before any individual meetings
  • working silently in zoom room together

How we can use our strengths to overcome obstacles:

• figuring out when to divide and conquer. Approaching things in an organized way.
• checking in with outside resources when needed
• Taylor's organization
• Andrew's debugging skillz

Schedule Expectations (When are we available to work together and individually? What constraints do we have? Make sure to discuss the remote questions above in regards to this section):

• Friday night off
• Projects in the evenings
• 1 hour dinner break
• done by 9 PM MT

Communication Expectations (How and often will we communicate? How do we keep lines of communication open? How will we make decisions as a team? How will we communicate about our emotional and mental well-being with each other?):

• Slack and meeting before individual work

Abilities & Growth Expectations (Technical strengths and areas for desired improvement):

• Spending time on testing initially
• improved git workflow
• consider feedback from flashcards project

Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests/Debugging and Problem-solving Techniques):

• refactoring after each section rather than all at the end
• updating readme continuously
• pull requests together
• teach taylor vs code
• mentor code review

Pomodoro Break Schedule:

• 35 / 5

Expectations for giving and receiving feedback:

• actually give feedback at end
• direct and respectful

Project management tools we will use (GitHub projects or Trello are popular tools):

• Git Hub Projects

Day 1 Agenda

• meet at 10 mt
• breaking everything apart in git hub projects
• class projects