Group Member Names: Adrienne, Chelsea, Allan
-
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? None of us have scheduling conflicts (Allan has one meet-up per week).
We'll go home at 7 every night, if we need or want to work individually after that, we will do that. Allan has a side project he's working on after 7. We'll be here over the weekend. -
How will group members communicate? How often will communication happen, and how will open lines of communication be maintained? Slack and in person.
-
Which feature(s) does each group member want to work on? Which feature(s) does each group member not want to work on?
Adrienne: Sending emails! Chelsea might want in on this.
We all don't like styling - we'll do it together. Allan will take the lead on this, and experiment with JS.
-
What does each group member hope to get out of the project?
Chelsea: become more comfortable with knowing when to drop down to model tests, writing clean views, git workflow
Allan: Learn some cool styling stuff. Adrienne: Get more comfortable with RSpec. Maybe playing with APIs. -
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, Waffle. We'll decide who will review on a case by case basis, as soon as they're no longer WIP. -
What is expected of group members when they run into problems implementing a feature?
Talk about it with the team - before they go to someone else. -
How does each group member want feedback (both positive and constructive) to be delivered?
In writing at the end of the project, verbally during the workflow. Mid-project verbal check-in. -
Is there anything else the group should know about personal work/communication styles?