Group Member Names:
- 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?
- JP lightning talk Friday
- Aaron prep computability theory
- How will group members communicate? How often will communication happen, and how will open lines of communication be maintained?
- Slack group (private)
- Which feature(s) does each group member -want- to work on? Which feature(s) does each group member -not want -to work on?
- Start project together with all four teammates
- Credit card processing (Steve)
- Design/appearance principlies for HTML & CSS (Hector, Aaron, JP)
- Machine Learning (Hector)
- What does each group member hope to get out of the project?
- 3's, know every code of line, specificity in communication (JP)
- Make it manageable for pivot, be more aware of the user experience (Aaron)
- Design, pairing soft skills (Hector)
- ActiveRecord & Testing (Steve)
- 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?
- Switch midway through features 1 *3:30, fill in eachother, 4:15 * ? with new partner
- What is expected of group members when they run into problems implementing a feature?
-
30 mins solving problem, seek help
- How does each group member want feedback (both positive and constructive) to be delivered?
- Feedback, direct and harsh (JP, Hector)
- Tap In & Tap Out for driver/navigator
- Narrate your thoughts when driving (JP)
- Is there anything else the group should know about personal work/communication styles?
- stick note feedback for group members Friday morning (+ and delta)