Skip to content

Instantly share code, notes, and snippets.

@hmorri32

hmorri32/rales_engine_DTR.md

Last active November 27, 2017 23:05
Show Gist options
  • Save hmorri32/e9927fd4a71fae50afdab33f0235a362 to your computer and use it in GitHub Desktop.
Save hmorri32/e9927fd4a71fae50afdab33f0235a362 to your computer and use it in GitHub Desktop.
Download ZIP
Raw
rales_engine_DTR.md

Setting Group Expectations

Group Member Names: EMILY WISE && HUGH MORRISON

  1. When are group members available to work together? What hours can each group member work individually? Are there any personal time commitments that need to be discussed? After school hours, no restraints, no late nights at school. Early mornings are a no go, for working collaboratively.

  2. How will group members communicate? How often will communication happen, and how will open lines of communication be maintained? In person preferably, VIA slack and or text. Lines of communication should be open most of the time. Slack works but via phone is best for urgent situations.

  3. Which feature(s) does each group member want to work on? Which feature(s) does each group member not want to work on? Emily -> A Hugh -> B

  4. What does each group member hope to get out of the project? Building upon our git knowledge, using activerecord over ruby and levelling up in that regard. Understanding namespaced routes. Keeping controllers skinny and presentable. Further understanding URL queries and parameters. Understanding REST conventions as it pertains to building APIs. Following TDD/BDD.

  5. What is the agreed upon Git workflow? What project management tool will be used? What is the agreed upon procedure for conducting code reviews before merging into master: who will review pull requests, and when? GIT: REBASE workflow - follow Brooke's guidelines. Utilize PR template. Collaborative code reviews. Project Management: Waffle.

  6. What is expected of group members when they run into problems implementing a feature? Reach out to eachother before reaching out to others. Collaborative workflow is generally preferable. We're both stubborn so let's check up on eachother.

  7. How does each group member want feedback (both positive and constructive) to be delivered? Instantaneously and directly! Or via slack if we need to collect our thoughts and put them in writing.

  8. Is there anything else the group should know about personal work/communication styles? Communication is important. Check in often.

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