Skip to content

Instantly share code, notes, and snippets.

@livecodelife

livecodelife/setting_expectations.markdown

Forked from Carmer/setting_expectations.markdown
Last active July 25, 2016 21:56
Show Gist options
  • Save livecodelife/d7887564ddddaad7b54e9a2a00de833f to your computer and use it in GitHub Desktop.
Save livecodelife/d7887564ddddaad7b54e9a2a00de833f to your computer and use it in GitHub Desktop.
Download ZIP
Setting Expectations
Raw
setting_expectations.markdown

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?

    Work after class, set a goal to finish and work until we hit that goal. Some members may have to leave for a bit after class to take care of pets but will come back

  2. How will group members communicate? How often will communication happen, and how will open lines of communication be maintained?

    Have a stand up before starting work each day. Communicate in an outspoken manner. Switch drivers/navigators regularly

  3. Which feature(s) does each group member want to work on? Which feature(s) does each group member not want to work on?

  4. What does each group member hope to get out of the project?

  5. 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?

  6. What is expected of group members when they run into problems implementing a feature?

    Don't get hung up on one feature, don't get attached to your code

  7. How does each group member want feedback (both positive and constructive) to be delivered?

    Be open, address things quickly.

  8. Is there anything else the group should know about personal work/communication styles?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment