Skip to content

Instantly share code, notes, and snippets.

@blackknight75

blackknight75/setting_expectations.markdown

Forked from Carmer/setting_expectations.markdown
Last active February 21, 2017 21:27
Show Gist options
  • Save blackknight75/ca835a0212e78d7c60114ec380a3dab4 to your computer and use it in GitHub Desktop.
Save blackknight75/ca835a0212e78d7c60114ec380a3dab4 to your computer and use it in GitHub Desktop.
Download ZIP
Setting Expectations
Raw
setting_expectations.markdown

Setting Group Expectations

Group Member Names: Spencer Carter, Brandon Randall, Daniel Olson

  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? Spencer: No Monday late night after 9:30, No Early mornings unless necessary. Late nights are good. Brandon: Nothing later than 2am. Late nights in group ok. No inqueries between 8:30 - 10:30pm(family time) Dan: Weekend days are sporadic and cannot guarantee times during the day but late night is very ok. Weekdays ok until 9pm and then after 10:30pm onwards is ok.(family time) Leave campus by 8pm.

  2. How will group members communicate? How often will communication happen, and how will open lines of communication be maintained? Slack(primary), text/phone call for emergency/urgency

  3. Which feature(s) does each group member want to work on? Which feature(s) does each group member not want to work on? Spencer: Want:Styling, Not Want: Managing Waffle.io Brandon: Want:Styling, Not Want: Nothing Dan: Authentication/Authorization, Not Want: Nothing

  4. Work style? Work in proximity of team. Pairings with all team members when necessary.

  5. What does each group member hope to get out of the project? Spencer: Concepts click with confidence. Overall app wrokflow. Brandon: Strive for understanding and ability to code with minimal referencing. Dan: Understanding sessions and how they interact with the app.

  6. 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? Project Management: Waffle.io Branch names that corespond to user stories each team member will work on respective branch and create PR's when feature/story is finished Meaningful comments on all PR's Pr's will be reviewed by all other team members and agreed upon before merging to master.

  7. What is expected of group members when they run into problems implementing a feature? Pomodoro. Reasearch/google. Reach out to team first. Mentor. Instructors. 30-45 minutes.

  8. How does each group member want feedback (both positive and constructive) to be delivered? Honest , constructive, feedback that moves the team forward.

  9. Is there anything else the group should know about personal work/communication styles? Brandon: Take breaks when a feature is completed. Victory lap. Dan: When stuck needs to get oxygen. I swear a lot. Very visual learner. Spencer: Headstrong/bullish at times. Extroverted. Talks through thinking.

  10. How we will work with mentors? Team pairings with mentors ok. Teachback what learned from mentors in individual communications/sessions.

  11. Stand-ups/Daily Retros? 8:40 Checkin to plan the day and check on last nights progress/challenges/roadblocks, review waffle cards. Before leaving campus, What did you accomplish today(high point), what you will be working on that evening and handling challenges from the day.

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