Skip to content

Instantly share code, notes, and snippets.

@JoelLindow

JoelLindow/setting_expectations.markdown

Forked from Carmer/setting_expectations.markdown
Created August 17, 2017 15:03
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save JoelLindow/d4fdf36c18c1c21e22fec4f1e98a802a to your computer and use it in GitHub Desktop.
Save JoelLindow/d4fdf36c18c1c21e22fec4f1e98a802a 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?

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

  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?

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

  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