Skip to content

Instantly share code, notes, and snippets.

@akintner

akintner/dtr_expectations.markdown

Forked from case-eee/dtr_expectations.markdown
Last active December 2, 2016 03:38
Show Gist options
  • Save akintner/27d4c337f30371ac69f20c26ad3bf48b to your computer and use it in GitHub Desktop.
Save akintner/27d4c337f30371ac69f20c26ad3bf48b to your computer and use it in GitHub Desktop.
Download ZIP
Group Work Expectations
Raw
dtr_expectations.markdown

Group Expectations

Group Member Names: Lucy, Amy, Nick E, Jason

Project Manager: Jason

Defining the Relationship (DTR) Questions:

  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? Amy: available most days after class and morning from 8:20 or so onward until 6PM, during weekends I'm in Colorado Springs, but I can do anything remotely Lucy: no real time restraints, tomorrow night (Friday) being home at a reasonable time, weekends 10-4 are good (usually in Saturday and Sunday around then) Jason: few errands for tomorrow so want to leave at a reasonable time, Saturday free all day, no Sunday time, on Slack a lot Nick: usually at school 8 in mornings and like to leave at 5:45 at the latest, 7:30-10PM are night times availble, likes to have at least half of one day off on the weekend

  2. What does each group member hope to get out of the project? Amy: I like the real-worldyness of this, so I hope to gain some insight into how we might use the tools we're learning for actual work applications. I'm also psyched to do more CSS (because I'm not very good at it yet). Lucy: it would be cool if this also looked good because I want to get some portfolio stuff to potentially show employers, steady workflow Jason: looking forward to maybe getting this up on heroku, Capybara seems fun to use Nick: echo what Amy said, getting to know RSpec better, getting used to forms

  3. How will group members communicate? How often will communication happen, and how will open lines of communication be maintained? Slack, Waffle, frequent little re-DTRs; lots of worktime next week will be useful; we will try to do daily stand-ups; probably one bigger meeting on Monday or Tuesday to assess progress since we'll be doing a lot of solo work on the weekends

  4. What is expected of group members when they run into problems implementing a feature? be upfront and just admit it, directly asking for help if needed, timeboxing problems to one pomodoro before asking for help

  5. Is there anything else the group should know about personal work/communication styles? Amy: I am absolutly useless after about 9PM (NOT a late night person), and I don't function well in long stretches of intense work; like to take time to ponder problems (might need to walk away for a bit) Lucy: wants to do an event next Tuesday if we're on track Jason: likes to be open and upfront about everything (side note: apparently Jason loves RedBull, like really LOVES it) Nick: happy to work solo, happy to pair in groups of two; likes to actually take some time to chew on things if a real problem arises

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