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?):
- Get to iteration 5, hopefully with some extensions. Gain more knowledge in Class use and array prototypes. Use SASS for CSS. Make a working app!
Team strengths & collaboration styles (consider discussing your Pairin qualities here):
- Raisa: Confident in Javascript and array prototypes. Patient, and willing to discuss problems that come up.
- Ben: Willing to work as long as needed. Patient, willing to work seperately and together depending on tasks at hand.
How we can use our strengths to overcome obstacles:
- Raisa: Ability to never give up helps push through problems that come up.
- Ben: Patience and willingness to push through issues, as well as ask for help when needed.
Schedule Expectations (When are we available to work together and individually? What constraints do we have?):
- Start with codewars or jsfun after class, and then stay on average until around 6pm. Try to finish as much during the week as possible, and move into the weekend if needed.
Communication Expectations (How and often will we communicate? How do we keep lines of communication open? How will we make decisions as a team?):
- Often, especially when we aren't pair programming. Primarily using slack, or working directly together.
Abilities & Growth Expectations (Technical strengths and areas for desired improvement):
- Raisa: Improve Javascript skills, OOP, and communication skills.
- Ben: Improve general Javscript skills, array prototype use, classes, OOP, testing.
Workload Expectations (What features do we each want to work on?):
- Divide up classes, after we've gone through with a short plan on what each should do. Plan out what CSS should look like and then impliment it as a pair. Divide up css based on each class and work on it that way using SASS.
Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests/Debugging and Problem-solving Techniques):
- Use Trello to identify each person's individual task. Using SASS we'll be able to commit CSS chunks and avoid conflicts. Comment on pull requests, and discuss before committing.
Expectations for giving and receiving feedback:
- Blunt and direct is best.
Project management tools we will use (GitHub projects or Trello are popular tools):
- We are using Trello for this project.