Skip to content

Instantly share code, notes, and snippets.

@ZaneMeroff
Last active March 23, 2020 18:06
Show Gist options
  • Save ZaneMeroff/f9cce4b6d2a11f2076d096075c60548b to your computer and use it in GitHub Desktop.
Save ZaneMeroff/f9cce4b6d2a11f2076d096075c60548b to your computer and use it in GitHub Desktop.

Dev.to DTR

A group project by Zack Nemeroff & Tyla Devon & Harrison Levin

DTR

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 wish to gain a better understanding of React and Rails. Our goal for MPV to be at least all threes.

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

  • One of our teams strengths is our ability to effectively communicate with one another regarding issues and work styles. We feel our collaboration style is working together to explain unfamiliar concepts, otherwise divide and conquer.

How we can use our strengths to overcome obstacles:

  • We intend to pair using driver/navigator. We will have a strong focus on communication throughout this project.

Schedule Expectations (When are we available to work together and individually? What constraints do we have?):

  • We can be reached via Slack during class time or 8 - 10pm weekdays. We will discuss exceptions.

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

  • We will communicate on a daily basis performing retros and discussing our plan for that day.

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

  • We wish to gain a better understanding of unfamiliar languages and platforms.

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

  • We're planning on working together through unfamiliar pieces of code and splitting up the workload on a daily basis.

Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests/Debugging and Problem-solving Techniques):

  • We will effectively use git rebase workflow.

Expectations for giving and receiving feedback:

  • We intend to be honest and polite when we address feedback to one another. Knowing that just because I disagree, doesn't mean I think I'm right and you're wrong. We will use the "compliment sandwich" technique as much as possible. Open, direct, and kind. Address problems sooner than later.

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

  • We will use GitHub Project Board.

the struggle is REAL

  • It is important to recognize when problems become larger or more complex than anticipated
  • Recognizing when we are avoiding difficult or less desirable tasks to complete
  • Make sure we take to time check in regularly on current progress
  • Not meeting deadlines or using time productively / getting partner help
  • We will let our PR know if we believe we are significantly behind at any time
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment