Skip to content

Instantly share code, notes, and snippets.

@vaidashi
Forked from Carmer/setting_expectations.markdown
Last active September 11, 2017 20:52
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 vaidashi/8a9f299eb69e1c85deeb82ee9e74ae47 to your computer and use it in GitHub Desktop.
Save vaidashi/8a9f299eb69e1c85deeb82ee9e74ae47 to your computer and use it in GitHub Desktop.
Setting Expectations

Setting Group Expectations

Group Member Names: Ash, Brandon, JP, Danny

  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?

No identiable constraints exist.

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

Slack and in person communication will be primary points of communication along with strong github and waffle workflow.

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

Incorporate a styling framework from the beginning and adapting as necessary.

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

More experience styling.

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

Waffle, all PR's will be reviewed before merging into master branch.

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

Communicate in person or through Slack on any concerns/problems that may arise.

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

In person or virtually.

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

All comfortable with various work styles.

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