Skip to content

Instantly share code, notes, and snippets.

@KevDev90
Last active September 3, 2019 22:05
Show Gist options
  • Save KevDev90/126f5c7e1c7906c8f901e43cfa874248 to your computer and use it in GitHub Desktop.
Save KevDev90/126f5c7e1c7906c8f901e43cfa874248 to your computer and use it in GitHub Desktop.
Check Yo'Self DTR
Project:
Group Member Names: Kevin Johnson, Alex Roth, Cameron MacRae
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 shoot for at least proficient in all categories but would like to excel if possible. Make sure we fully complete each iteration before we move onto the next one. If we recieve good feedback, and become comfortable with the new learning materials.
Team strengths & collaboration styles (consider discussing your Pairin qualities here):
Cameron and I both utilize the strategic thinking leadership style whereas Alex utilizes moreso of the relationship building and influencing leadership styles so we think those styles should blend well as a whole. We would like to maintain constant communication and set daily goals for what we'd like to achieve. We would like to do mostly driver-navigator while we're at turing and implement more of a ping-pong style while we're at home at night.
How we can use our strengths to overcome obstacles:
Cam will utilize his executing and I will utilize my strategic thinking to set on overall framework of what we need to accomplish and I think Alex is going to help keep the communication open and positive with his relationship building qualities.
Schedule Expectations (When are we available to work together and individually? What constraints do we have?):
We'd like to stay at turing for an hour or two to discuss our goals for the evening and decide what working methods to implement on that given night. Communicate to each other when instances come up and make sure we're hitting our deadlines.
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'll be communicating through slack mostly all of the time, we'll message each other and keep each other updated as we progress through our goals. If something comes up in our daily lives that limits our ability to meet a goal on any given night then we will convey that to the team.
Abilities & Growth Expectations (Technical strengths and areas for desired improvement):
We would like to work on keeping our JS code DRY, and staying efficient with our time and not going down too many rabbit holes. We would all like to become more familiar with the newer array prototype methods that we're still learning.
Workload Expectations (What features do we each want to work on?):
Cam would like to utilize more JS whereas Alex and I are more comfortable implementing semantic HTML, and we would like to collaboratively work on CSS at times. We are also wanting to divide and conquer and ping pong certain tasks throughout the project.
Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests/Debugging and Problem-solving Techniques):
We're going to make it a point to not merge our own pull requests. We're also going to try to always make new branches when working on new parts of the project. And we're going to work on using specific naming conventions for branches and commits.
Expectations for giving and receiving feedback:
We want to be able to establish open and honest feedback. We are going to remain respectful of our teammates while also giving constructive feedback without being too overly critical.
Project management tools we will use (GitHub projects or Trello are popular tools):
Github projects.
Day 1 Agenda:
Wireframe, DTR memo, Project management board, establish our project repo, create our GH pages link.
Additional Notes: It's going to be great!
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment