Skip to content

Instantly share code, notes, and snippets.

@njgheorghita
Forked from drod1000/expectations.md
Created January 3, 2017 20:39
Show Gist options
  • Save njgheorghita/9f333fdf4b5dc6cea7e9ce97a965130e to your computer and use it in GitHub Desktop.
Save njgheorghita/9f333fdf4b5dc6cea7e9ce97a965130e to your computer and use it in GitHub Desktop.
Group Expectations

Setting Group Expectations

Group Member Names: Drew, Laszlo, Nick G

Project Manager: Daniel

Defining the Relationship (DTR) Questions:

  • When are group members available to work together? What hours can each group member work individually?

We'll get here at 9 AM and work whenever we have worktime. We're all open to staying here after school and we'll determine how much we'll work individually

  • Are there any personal time commitments that need to be discussed?

We'd like to get the initial setup today and be able to take the day to work on other tasks but other than that we're all pretty open.

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

Daily Stand Up every morning to make sure that everyone's on the same page. We'll try to work in the same room even if we're working individually so that we can walk over whenever we need to talk to each other. If anyone is working remote we'll use Screenhero and Slack.

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

Too early to tell. We'll discuss this whenever we get the stories.

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

  • 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?

We'll use Waffle as a project management tool. As for code reviews the person submitting a pull request is expected to make sure that all tests are passing. All of the team members will then comment on the pull request to okay it and the last one will merge it. The person submitting a pull request should never merge their own pull request.

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

Reach out to other team members whenever they run into problems implementing a feature

  • How does each group member want feedback (both positive and constructive) to be delivered?
  • 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