Forked from rwarbelow/setting_expectations.markdown
Last active
November 9, 2015 17:25
-
-
Save robbielane/b4dd80962dde6a1f589e to your computer and use it in GitHub Desktop.
Setting Expectations
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
## Setting Group Expectations | |
Group Member Names: | |
1. 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? | |
- Robbie has kids sometimes. | |
1. How will group members communicate? How often will communication happen, and how will open lines of communication be maintained? | |
-create a slack channel | |
-make phone number's available | |
1. Which feature(s) does each group member *want* to work on? Which feature(s) does each group member *not want* to work on? | |
-Tyler backend | |
-Frotend will be done collaborative | |
1. What does each group member hope to get out of the project? | |
-tyler -learn the backend | |
-ross -build an app that doesn't look like a 'turing project' | |
-robbie -use best practices | |
1. What is the agreed upon Git workflow? Who will review pull requests, and when? What project management tool will be used? | |
-waffle is our friend. | |
-never push to master | |
-meaningful branch names and commits | |
-peer reviews -ping slack channel when a branch is ready. | |
1. What is expected of group members when they run into problems implementing a feature? | |
-Immeadietley ping group members. | |
- | |
1. How does each group member want feedback (both positive and constructive) to be delivered? | |
-just say it | |
1. Is there anything else the group should know about personal work/communication styles? | |
-start features together and delegate work. | |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment