Skip to content

Instantly share code, notes, and snippets.

@liambarstad
Forked from Carmer/setting_expectations.markdown
Last active September 11, 2017 21:34
Show Gist options
  • Save liambarstad/e59766d7748d5dbee7cfa7e673eb5260 to your computer and use it in GitHub Desktop.
Save liambarstad/e59766d7748d5dbee7cfa7e673eb5260 to your computer and use it in GitHub Desktop.
Setting Expectations

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?

Group members can meet on weekdays until 7-8, preferring afternoons on weekends. Aaron will have to leave sometimes after school to watch his dog.

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

Communication can be done over slack when necessary for all group members. Pull requests, as a goal, will be reviewed and commented on by all members.

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

All members have expressed a desire to work partially in all aspects of the project.

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

Dennis would like everyone to integrate and understand all parts of the project. Aram would like to practice compartmentalizing logic effectively. Mike would like to acquire more general understanding. Liam would like to establish a good github workflow and work on staying organized and efficient in a 4 person group.

  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?

When an individual starts a task, they will always make note of it on waffle.io, and if the task can be broken into components, the person or people working on that card will break it up into smaller responsibilities.

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

Reach out for help if progress is not made on a problem after 30 minutes of work. Group members have many different resources and methods by which they can get assistance, and thus no specific convention needs to be agreed upon.

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

Respectfully, but not to the point to where any information is lost.

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

Working together in the same room but not on the same problem seems like it would maximize efficiency. An exception would be when there is a problem that is thoroughly challenging.

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