Project:
Group Member Names: Chadrick Dickerson, Ian Holladay.
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?):
- Have a working application
- Implement ES6 classes that communicate to each other as needed
- Write modular, reusable code that follows SRP (Single Responsibility Principle)
- Implement a robust testing suite using TDD
- Use object and array prototype methods to perform data manipulation
Team strengths & collaboration styles (consider discussing your Pairin qualities here):
- Chadrick is a good communicator although more passive, pays attention to detail, and may tend to look deeper than necessary into a task.
- Ian feels more comfortable being assertive, and feels he can help Chadrick to develop more positive assertive communication qualities.
- Chadrick can assist Ian in being more positively assertive in communication.
How we can use our strengths to overcome obstacles:
- Chadrick is compassionate and understanding, and seeks to ensure that his teammates are getting their fair share of experience.
- Ian's assertiveness can assist the team and forging ahead in moments of uncertainty.
- We will watch out for when either of us are feeling in need of a break mentally or physically.
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):
- Chadrick has plans after 3pm on Saturday.
- Ian would like to get as much done sooner than later, and Chadrick agrees.
- Starting at 10am on Saturday and Sunday.
- 6 hours on Sunday
- Wednesday Ian has a mentor meating from 4-5pm, a repeater happy hour from 4:15 to 5:15pm on Monday.
- Start around 5:45 or 6pm on Monday.
- Tuesday all afternoon.
- We intend to have everything done other than the Readme by Wednesday.
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?):
- We will stay in communication via slack, and mobile.
Abilities & Growth Expectations (Technical strengths and areas for desired improvement):
- Chadrick hopes to grow stronger in understanding of ES6, arrow functions, and array.prototypes/iterator methods, as well creating srp code.
- Ian wants to grow in his ability of having good professionalism, workflow, and iterator methods.
Workload Expectations (What features do we each want to work on?):
- We expect to contribute to he project equally, and help eachother understand our approaches along the way.
- We would to devote as much time as we are mentally and physcially able to in order to get the project completed in a speedy yet quality-abundant fashion
Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests/Debugging and Problem-solving Techniques):
- We commit small and frequently, For Html 1 commit when completed, once commit per each srp testing code block, other commits as needed.
Pomodoro Break Schedule:
// - We expect to work 1 hour to 1.5 hours with longer poms in between. // This is our previous agreed upon pop breakdown // //
- We now agree 45-50 minute work sessions with 10-15 minute breaks.
Expectations for giving and receiving feedback:
- We will be empathetic and thoughtful when we give eachother feedback. We will speak up when we don't understand a line of code and focus on that until we understand.
Additional Remote Considerations:
- If slack is not working, we can use Tuple or Zoom.
Project management tools we will use (GitHub projects or Trello are popular tools):
- we will use github projects.
Day 1 Agenda:
- buid project board
- Get into pseudocoding if time alots it.
Additional Notes: