Skip to content

Instantly share code, notes, and snippets.

@Tristan-Holtz
Created October 7, 2019 21:14
Show Gist options
  • Save Tristan-Holtz/4c2622c904b15e6cfe77a60cacc0b8e3 to your computer and use it in GitHub Desktop.
Save Tristan-Holtz/4c2622c904b15e6cfe77a60cacc0b8e3 to your computer and use it in GitHub Desktop.

Group Member Names: Tristan Holtz, Kevin Johnson.

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 would like to finish the project and not skip any iterations along the way. We want to keep our communication constant and stay open with one another on our goals and progress throughout the project. If we’re learning first and foremost, and also if we’re making progress that is up to our standards.

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

We both have a imaginitve-inspirational trait in common so I feel like that’s a great start to establishing a good connection with each other. We’re both on the same page pretty much with our schedules. We would like to stay at turing until around 6pm or so most days, and also try to come in an hour or so early before class to get some additional work time.

How we can use our strengths to overcome obstacles:

Our pairin qualities are very complimentary to each other. Tristan has an inspirational leader trait whereas I have more of a can-do attitude and I feel like those strengths are going to mesh together very well. And we both of the qualities of being a good teammate that is going to bode well for us in the long run.

Schedule Expectations (When are we available to work together and individually? What constraints do we have?): We would like to spend roughly 3 hours a day doing driver-navigator and then doing some additional work on our own at night and then stay in good contact with each other.

Communication Expectations (How and often will we communicate? How do we keep lines of communication open? How will we make decisions as a team?):

We’re going to balance communicating on slack and via our phones as well when we’re not working to stay on the same page. And we will have plenty of in person communication time to plan out our plan of attack for the day.

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

Tristan would like to improve on his JS whereas I would like to improve on my CSS a lot more.

Workload Expectations (What features do we each want to work on?):

We want to begin working today so that we can establish an effective timeline and dive further into the project so that we can get a better idea of what’s going on.

Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests/Debugging and Problem-solving Techniques): We’re going to try and push to branches when working separately and submit pull requests to review each others code. Use console.log’s within our functions and clearly read and follow our error messages.

Expectations for giving and receiving feedback:

We’re both open to recieve criticism if necessary but we would like to do so respectfully.

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

We’re going to try to use github projects on this project.

Day 1 Agenda:

We’re going to attempt to wireframe and crank out our HTML, as well as begin styling some CSS, and also bust out a rough timeline of our plan of attack for the project.

Additional Notes:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment