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?
GROUP DECISION: Weekends we will be here.
Kris: gets here around 6am, prefer to leave around 6-6:30pm, rather not be here for 14 hours unless last day. Prefer to work side by side. Yoseph: "Meh" about the weekends. Similar to Kris. Patrick: Getting here early at 6am, have a dog and lease is up...so may leave after wrap up some days.
-
How will group members communicate? How often will communication happen, and how will open lines of communication be maintained? Kris: Pretty good with Slack. Won't check Slack after 6 or 7pm. Go to bed pretty early. Patrick: Also, alright with Slack when not here. Go to bed early as well, around 9ish. Yoseph: Good with Slack, will get back within exactly 20 seconds if you message him.
-
Which feature(s) does each group member want to work on? Which feature(s) does each group member not want to work on? Kris: Like to be involved as much as possible. Know that this is for us to learn. Pass on styling. Wants to work on advanced routing and nested resources.
Patrick: Filled a larger role in former projects than necessary. Will try to fall back into a test writing role, want to work on security.
Yoseph: Better understanding of how everything works (advanced routing and database relationships), really enjoys UX, UI, and Front End.
-
What does each group member hope to get out of the project? Kris: Learn, use this project to repeat concepts to solidify learning. Yoseph: Knowledge about front-end design. Patrick: Group members learning from this experience, looking back and being satisfied with the way our group worked together.
-
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?
By the book with Git workflow - follow best practice and guidelines. Someone ELSE receive pull request when pushing a branch, (GOAL: Other person leaves a comment on the merged code, so that we know they actually reviewed the code) Checkout as many branches as you need.
- What is expected of group members when they run into problems implementing a feature?
Don't be afraid to say something/ask for help from other group members. Don't try to be a hero.
- How does each group member want feedback (both positive and constructive) to be delivered?
If possible, face to face. Don't be a jerk. If constructive, try to include some positive feedback.
- Is there anything else the group should know about personal work/communication styles?
Kris: At some point, will get frustrated - it's not directed towards anybody. Don't take anything personally. Yoseph: Expect to receive high-fives after small victories. Patrick: If I'm not able to be here all the time bc of current life circumstances, just know that I'm going to do my best with the time I do have.
Project Manager: Patrick
- Project management tools: Heavy TDD workflow, wireframes for views, WaffleIO, ERDs and Schema designers so everybody is on the same page with visualizing concepts.