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?):
We each hope to walk away from this project having a greater understanding of what's going on. To expedite this, we plan on working side-by-side, and limiting independent work (working through small, testable chunks); comprehension over perfection - we want to leave feeling confident and competent.
We have overlapping qualities, so we are planning to be mindful of our gaps and ensure that we are communicating effectively. Working together will help us fill the gap of someone who uses a relationship-building leadership style.
We envision an obstacle being that we are missing an individual that is centered on relationship building, however, we are all focused on ensuring that we comprehend the task at hand and are navigating through the JS together.
Schedule Expectations (When are we available to work together and individually? What constraints do we have?):
We all have availability after school, so we plan to make the most of it while we are all in the same place. We plan to dedicate at least 2 hours of focused project work after school, but we are flexible with extending that time if need be.
Communication Expectations (How and often will we communicate? How do we keep lines of communication open? How will we make decisions as a team?):
If we treat each other with respect and are honest about expectations, we should be good. We have agreed to notify each other of updates as we come across them, while acknowledging that we are not expected to reply. Katie will turn off notifications for Slack around 930.
We all fell pretty comfortable with HTML and CSS, and want to prioritize our understanding of JavaScript, while improving out use of Flexbox and Grid.
We plan on this being as much of a collaborative effort as possible, so we are hoping to build the foundation together and will delegate extensions once this is achieved.
Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests/Debugging and Problem-solving Techniques):
We forsee this becoming more relevant once we have the foundation of our site built. As we will largely be working together, we are less concerned about merge requests, though we imagine the relevance will change once we are able to work on extensions.
We each appreciate honesty, and when delivering feedback, we agree that it should be done with kindness, mutuality, respect.
Trello
We have each reviewed our itemized tasks on trello, and we have each left comments regarding how we think we may be able to accomplish them. We do this in the hope that on Day 1 we can start on the same page, and move forward together tackling the HTML first, then progressing into JS.
N/A