What does this group do when two or more members disagree (ex. on a technical approach, a technology choice, etc)? Do you vote? Does the whole group get involved? Do you get someone else to decide?
- Call open discussion until issue is resolved. If nothing has been resolved, bring in a instructor or fellow to assist.
What does this group do when a member is frustrated? What strategy do you use to talk about it? What do you do if you’re the frustrated person? What do you do if you’re the person someone is frustrated with?
- Be open. Take a break and grab coffee. Make sure we talk to each other.
What does this group do when we merge our work together? Do we do it together? Do we require sign off from someone else?
- Everyone does merge after stand-up meetings. Whenever there is a pull request, it is a must that everyone reviews the code.
When does this group ask for help? After 10 minutes? 15? 20? After everybody’s tried to solve the problem? What strategies do we use before we ask for help?
- After 15 minutes of struggle, call groupmates, and then instructor afterwards if the problem is still not solved.
How do we pair? What do we do when two group members pair with each other? Do members of a pair decide their own norms? Do they do things like keep a timer to switch positions? How often do we switch partners?
- Up to the pair, depending on situation. When two group members pair, try to be clear on implementation goals. If working alone, make sure there are lots of comments on the code so that others can understand
How does this group approach work “after hours” (i.e. after normal class hours and weekends)? Is it okay to work on your own after hours? How do we keep the group informed? Do we only work after hours when we can pair? When the entire group is present?
- Please communicate any updates with scheduling. If working on the weekends on campus, those who can't participate work remote and communicate well on Slack channel.
- 10:30am after REACTO.