Group Member Names:
Jordan Williams, Sebastian Sloan, David Holtkamp, Steven Anderson
Goals and Expectations for the Project (What does each group member hope to get out of this project? What do we want to achieve as a team? How will we know that we're successful?):
Group: as a team we hope to build on the foundation of our API skills and further develop new skills with new technologies. One of our primary goals is to make sure we collaborate effectively, help each other, and communicate well. Our gauge for success is if all group members have a good experience while working on this project, and also that we meet all criteria with minimum scores of 3.
Team strengths & collaboration styles (consider discussing your Pairin qualities here):
Group: as a team we are all very open, straightforward, and desire clear communication. We are all interested in working in pairs or as an entire group for the majority of tasks, but each individual also needs time to work through productive struggle on their own.
How we can use our strengths to overcome obstacles:
Group: as a team we are all very dedicated people who are committed to doing what it takes for us to achieve the desired results, and we feel that applying that level of focus to the project will allow us to tackle any issue we face.
Schedule Expectations (When are we available to work together and individually? What constraints do we have?):
Group: as a team we all agree that taking some time during lunch is an opportunity to recharge. Hard stop times:
Sebastian = 9:00pm Dave = 10:00pm Steve = Whenever Jordan = When the project is over
We are all very comfortable with each other's schedules, and these times are merely to display the ideal conditions.
Communication Expectations (How and often will we communicate? How do we keep lines of communication open? How will we make decisions as a team?):
Group: as a team we discussed each of our ideal communication styles, and there is consensus that we all appreciate open and straightforward communication. We will primarily use Slack for text communication and we will use Zoom for video calls.
Abilities & Growth Expectations (Technical strengths and areas for desired improvement):
Sebastian = API consumption structure and abstraction Dave = Whatever I need to master to finish the mod Steve = Whatever I need to master to finish the mod Jordan = All of the things
Workload Expectations (What features do we each want to work on?):
Group: TBD. We'd all like to contribute as much as we can.
Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests/Debugging and Problem-solving Techniques):
Group: PRs are to merged by someone other than who created them All features should be branches All PRs need to pass TravisCI before being merged into master All PRs should follow the PR template
Expectations for giving and receiving feedback:
Group: Specific, actionable, kind We are all open to regular feedback, and would appreciate it
Project management tools we will use (GitHub projects or Trello are popular tools):
Group: Asana
Additional Notes:
Group: We're going to punch this project in the face.