Group Member Names:
Nick - PM
Colleen
Craig
- 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?
We agreed that none of use or morning people so the majority or work time will be in the afternoon. Agreed to try to limit weekend work to one day at the building but we have to come in a second day we would prefer to start a little later. We have open availability. We will default to working together but will assign individual work if we think that will help productivity.
Craig: No life.
Colleen: No life.
Nick: No Life.
- How will group members communicate? How often will communication happen, and how will open lines of communication be maintained?
We set up a slack DM for group communication. Start off each work session with a stand-up and finish with a retro. Nick will take the lead on setting up project management tools.
- Which feature(s) does each group member want to work on? Which feature(s) does each group member not want to work on?
We all want to be proficient in every aspect of the project. Craig has volunteered to take the lead the styling portion of the project.
- What does each group member hope to get out of the project?
Better understanding of how the different elements of a web app interact. Proficiency in using activerecord. Successful group collaboration. Proficiency in Git Workflow.
- 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?
Nick will own the forked repo. Post to slack when submitting a pull request and someone will acknowledge that they are reviewing it. Catch up branches at the end of each day to help avoid merge conflicts. Commit to using waffle to drive development by connecting it to github.
- What is expected of group members when they run into problems implementing a feature?
Reach out for help. Timebox your struggle. Reach out to outside knowledge.
- How does each group member want feedback (both positive and constructive) to be delivered?
Give constructive feedback. We're all a little uncomfortable with critiqueing other's works so we need to make sure create an environment the facilitates that. We all agreed that we are comfortable recieving feedback.
- Is there anything else the group should know about personal work/communication styles?
Craig: Likes to work through problems individually and then bring back his new knowledge back to group.
Colleen: It is important to her to fully understand the code that is being written.
Nick: Agrees with both Colleen and Craig about their work styles.
PM Role: Stand-up Retro, communication lead, waffle management, initiate goals discussions for each work session.