Skip to content

Instantly share code, notes, and snippets.

@Ryanspink1
Forked from case-eee/dtr_expectations.markdown
Last active January 28, 2017 22:40
Show Gist options
  • Save Ryanspink1/97c21c66104313556492391a13a4d010 to your computer and use it in GitHub Desktop.
Save Ryanspink1/97c21c66104313556492391a13a4d010 to your computer and use it in GitHub Desktop.
Group Work Expectations

Group Expectations

Group Member Names: Ryan Spink, Ashley Schauer, Charlotte Moore

Project Manager:Ashley Schauer

Defining the Relationship (DTR) Questions:

  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? ###Charlotte No major schedule restrictions. Weekends are harder to book, but possible. Has to be home by 8pm/9pm. ###Ashley No mornings. Needs to be home by 8pm/9pm. Available at home via ScreenHero if needed. Unavailable Friday evening and Saturday. ###Ryan No mornings. No hard stop time. Available at home via ScreenHero if needed. Unavailable Friday evening. Likes check ins at the end of every day. ###Group Work evenings after class until hard stop at 8pm/9pm. Meet on Sunday afternoon at noon at Turing. Will check in with each other every work day.

  2. What does each group member hope to get out of the project? ###Charlotte Success is completing the project. Focus on learning how to work in a group and collaborate. Develop a better understanding of how to work in a group. ###Ashley Develop a better understanding of how to work in a group. Project success is 75% completion and 100% functionality on that. Challenged myself in learning something new. ###Ryan Cohesive group dynamic. Major goal is to gain a solid understanding of more advanced methods and functionality of ActiveRecord. Wants to improve on writing test code and maintaining good coverage. ###Group Project Goal -- 75% completion with 100% completion

  3. How will group members communicate? How often will communication happen, and how will open lines of communication be maintained? ###Ryan Very open with how he’s doing and very on top of conflict to deal with any problems. Very comfortable with both roles with pair programming. Contact right away if someone is stuck. Communicate with the other group members if the task is taking longer than expected. If there is disagreement on how to implement something, do some research to develop the idea and if both are still viable, do a round table. ###Charlotte DnC is more natural. More of an independent worker. Wants to work on collaboration skills, patience in “teaching” stuff to others, and communication skills. Finds critical feedback difficult because doesn’t like to hurt other people’s feelings. Would appreciate constructive feedback. Agrees with Ryan on how to resolve disagreement and conflict as a team. ###Ashley Can get very intense and can be very intimidating and dominating over conversations. Has trouble with pair programming because has difficulty not having control over the direction of something. Agree with Ryan on how to resolve issues. If emotions run high, we should give each other space to cool off. ###Group Contact each other via Slack.

  4. What is expected of group members when they run into problems implementing a feature? ###Group Contact right away if someone is stuck. Communicate with the other group members if the task is taking longer than expected. If there is disagreement on how to implement something, do some research to develop the idea and if both are still viable, do a round table.

  5. Is there anything else the group should know about personal work/communication styles? /br ####We feel that the previous questions have covered this.

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