Skip to content

Instantly share code, notes, and snippets.

@Maxscores

Maxscores/setting_expectations.markdown

Forked from Carmer/setting_expectations.markdown
Last active January 2, 2018 19:07
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 Maxscores/d7b3bb5e445a5bd8c5b3b91a4cea1337 to your computer and use it in GitHub Desktop.
Save Maxscores/d7b3bb5e445a5bd8c5b3b91a4cea1337 to your computer and use it in GitHub Desktop.
Download ZIP
Setting Expectations
Raw
setting_expectations.markdown

Setting Group Expectations

Group Member Names: Katy Welczyko, Zach Landes, Max Stackhouse

  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? Plan to get things divided up for individual work time by the end of the day. Katy - Leave by 6 Zach - None Max - Leave by 6

  2. How will group members communicate? How often will communication happen, and how will open lines of communication be maintained? Slack. Phone numbers. Stand-up at beginning of work-time Retros at end of day

  3. Which feature(s) does each group member want to work on? Which feature(s) does each group member not want to work on? Katy - Cart functionality cool, wants to improve route implementation with only things we need Zach - Testing skills. Let vs Before Max - External Services, Plan before All - Using a framework (Foundation), Unsplash (images)

  4. What does each group member hope to get out of the project? Katy - API Calls, Learn about asset pipeline, Carrierwave Zach - Git workflow, Well organized team environment Max - Plan a project before and execute

  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? PM Tool - Jira Git Workflow - Merge, PRs no code requests Code Reviews - PR with template, make to state what the PR has in it. Be explicit and verbose. Passing tests. Code reviews at beginning and end of day.

  6. What is expected of group members when they run into problems implementing a feature? Solutions oriented - this is what I've tried and this is what I'm thinking is going on. Provide research, example of failures, googles.

  7. How does each group member want feedback (both positive and constructive) to be delivered? Interpersonal in person, code in PR comments & in person

  8. Is there anything else the group should know about personal work/communication styles? Zach - Wants feeback, enjoys it Katy - Step up, step back Max - Can move through things fast and not explain my entire reasoning.

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