Group Member Names: Caleb Cowen, David Tinianow, Sonia Gupta, Ryan Flach
- 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?
Time committments: * Caleb is not available TR until 5:15 pm. Other than that, he is available. * David: cutoff at 8:30 generally. * Ryan: not stay too late, shuts down computer no later than 10 pm. * Sonia: TR after 4:45, any other time flexible.
Individually: evenings
Together time: 5:15 on Thursday, after wrap-up every other day.
- How will group members communicate? How often will communication happen, and how will open lines of communication be maintained?
Slack Channel (primary, in person), 10 Minute check-in in person each morning. Before the weekend we should have another meeting to check in to see how we will communicate.
- Which feature(s) does each group member want to work on? Which feature(s) does each group member not want to work on?
Need to read through the spec. -Hold off
- What does each group member hope to get out of the project?
Ryan: a better understanding of all the concepts being applied here, additional understanding of git workflow, project management with waffle, how to work in a group Caleb: knowing how to work in a bigger group David: Getting a sense of all the things without specializing, git workflow Sonia: Analysis, working in group, communication dynamic
- 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 workflow: Project Management Tool: Waffle Who reviews pull requests and when: pinging in slack channel, asking anyone to review, after 15-30 minutes if no one has grabbed it (assuming it's not late at night) then you can assign it to a particular person for review
- What is expected of group members when they run into problems implementing a feature?
First try to solve the problem on your own (or with the group) and then reach out for help. (Expect to have project done end of day Saturday)
- How does each group member want feedback (both positive and constructive) to be delivered?
David: Direct feedback, prefer one-on-one feedback to group feedback. Depending on the nature of it, in person, but if a code thing than can slack it. Caleb: Agrees with David, wants the feedback earlier rather than later. Ryan: Direct communication, wants to know earlier rather than later. Sonia: Direct communication, don't be mean.
- Is there anything else the group should know about personal work/communication styles?
Sonia: I tend to be a little slow on the uptake, may need to stop the group and ask us to step back and understand if we're working in a group. Ryan: May need to silo and think about some things. Once figured out can explain it. Caleb: Tends to move on quickly if he gets into typing something, can tell him to stop. David: Likes to work independently, has gotten better since being at Turing, getting better at thinking out loud. Can be uncommunicative at times, especially if it feels like shit is hitting the fan.