- Project:
2DoBox Pivot
- Group Member Names:
Nick Svetnicka & Christie Lynam
- Project Expectations:
Nick: I am hoping to get more experience using GitHub. This includes creating an issues list and always developing on branches to better understand the merge and conflict resolution process. I also am hoping to do a mix of pair programming and either side by side or solo development, to build more muscle memory by driving. On my last 2 projects I was more of the navigator, and feel that it should be more balanced, so both partners get experience in both roles.
Christie: OMITTED
- Schedule Expectations:
We’ve decided that ideally, we will work primarily during the week after classes, for 3-4 hours. We are both willing to work on the weekends, but would prefer to have one day of relaxing / solo coding.
- Communication Expectations:
Sharing cell numbers would be ideal, as it can help with more immediate questions/concerns. And to leverage Slack for non-immediate communication or live session communication.
- Abilities Expectations:
Nick: I feel strong in my Javascript and Jquery skills, and am hoping to push the limits of Dom manipulation to learn more about css, and how to leverage things like the data attribute.
Christie: OMITTED
- Workload Expectations:
We’re in agreement that working on a complex feature should primarily be done as a pair, and only minor refactors or adjustments when we’re on our own. We will address individual feature contributions when required, or as we evaluate our progress against deadline.
- Workflow Expectations:
We’ve decided to store all of our to-do’s for the project in the GitHub issues section. And only make commits to the master branch if it’s something very minor and it’s clear that both partners have no working branches. All significant work should be created against a branch, even when pair programming. All branches will be merged through a pull request reviewed by the other person.
- Expectations for giving and receiving feedback:
Noting the successful and admirable qualities in each other will help us understand our strengths, but equally important is to acknowledge areas we see room for growth. We are both accepting in receiving some tough love.
- Agenda to discuss project launch:
Review current state of application, both in terms of existing functionality, and identifying incomplete features. Discuss strategy for bringing the application to a working state. Plan our approach for adding in the additional features.