Skip to content

Instantly share code, notes, and snippets.

@cmacaulay
Forked from Carmer/setting_expectations.markdown
Last active January 27, 2017 05:55
Show Gist options
  • Save cmacaulay/877bc1e8834864f7867126e1aadcb484 to your computer and use it in GitHub Desktop.
Save cmacaulay/877bc1e8834864f7867126e1aadcb484 to your computer and use it in GitHub Desktop.
Setting Expectations

Setting Group Expectations

Group Member Names: Amara, Max, Cody, Casey

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?

  • Mostly after school and on the weekend, Cody and Amara are most productive in the morning while Max and Casey prefer to work in the evening. Prefer 9-4 for weekend work times to have evenings off.

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

  • Slack channel, phone numbers into the slack channel as an additional means of communication.
  • Slack - feel free to communicate whenever we have an idea, air on the side of more communication. If you are struggling, let us know.

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

  • Amara is crazy about user experience.
  • Max is interested in getting better at Active Record and figuring out how the website works, the dashboard.
  • Amara is intersted in maps.

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

  • Cody - getting a better understanding of Sinatra/Active Record. Try to be on the same page as the rest of the team and make sure we are all on good footing.
  • Amara - get more familiar with the new tools and platforms and style.
  • Max - improving using Active Record/data manipulation and dashboard type things. Knowing when to struggle alone with a problem and not pair.
  • Casey - using waffle, communicating about when I need to work alone.

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?

  • Starting off on our own branches
  • We will all push from our branches to a dev branch before merging to master
  • Waffle as a project management tool.
  • Use the slack channel to notify eachother about a pull request, one person will claim the responsibility of reviewing the code and merging to the dev branch. Casey will merge to master.

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

  • COMMUNICATE ASAP
  • Find resources together
  • Notifying our mentors

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

  • Daily retros ("standups")
  • What was done/sucesses for the day, what worked well, what isn't working well, what do we hope to achieve tomorrow
  • Time to touch base on what our goals are and how we're meeting them
  • Use the DTR as a reference point
  • Don't let things fester, address any issues as they come up, get issues out before they grow.
  • Be open to feedback
  • Say what needs to be said, be tactful about it. If you have a thought for someone, you should give it to them.

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

  • Amara - is a very direct, honest and straight-forward person. Can get pessismistic/whiney when things aren't going well.
  • Max - can be kind of intense.
  • Cody - intense/focused
  • Casey - NEEDS SLEEP or will get loopy. Always tries to bring the positivity.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment