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?):
Day by day make incremental progress on iterations, working collaboratively whether that be solo or together.
Team-Goals: Be respectful of each other's time
We are both flexible and able to work off the strengths of the other.
JimJames: I work best alone, where I am able to focus and can accomplish things quickly. Once I have an understanding of the problem I am an effective communicator so I can explain the problem I am trying to solve.
Roger: I can adapt to the person I am working with, to work in whatever way works best for them.
Unfortunately, we are both sick at the current time of this project. But we are both men of our words, and will help the other as obstacles arise, making sure that we both make it through and no one gets left behind.
Schedule Expectations (When are we available to work together and individually? What constraints do we have?):
JimJames: My schedule is open, and willing to work around whatever works for Roger.
Roger: I just had a kid, so worktime is going to be limited when I get home but available to work after school.
Communication Expectations (How and often will we communicate? How do we keep lines of communication open? How will we make decisions as a team?):
We have agree to communicate daily, and once we break for that day and return home, utilize Slack to update any issues or push any changes. Will delegate responsbilities before leaving for the day. If we work past what we agreed upon, slack will be used to notify any changes.
JimJames: I have received some early feedback regarding improvement on my array prototype methods usage, so would like to demonstrate fluency on those methods. As well as hone a good git workflow with my partner.
Roger: Utilize more jquery over last time, to minimize variable declarations.
JimJames: I was doing some research into JQuery widgets to display the data in a aesthetically pleasing, and intuitive way. Would be down to work on that together, or tackle that on my own. Also anything that is tedious and just needs to get it done, I can take those tasks own as well.
Roger: Together we can layout out the groundwork for the class structure but I can build out all the testing as we build out each iteration.
Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests/Debugging and Problem-solving Techniques):
JimJames: Have yet to find a happy medium on Git workflow, but think that we should commit often and make many pull requests. Communicate as much as possible on what features we are working on an keep track of all files that are being changed to avoid merge conflicts as much as possible. Would rather do a 100 small merge conflicts than one massive one.
Roger: I can work to whatever is easiest for my partner, and I will push up my changes and pull down. If there any any merge conflicts I would suggest trying to resolve them before trying to push to master to avoid any overwriting. Also peer review any PRs is best practice.
Be open to receiving direct feedback without being offended, but the person giving feedback should adhere to decency and politeness.
If either of us are rubbing each other the wrong way to be able to bring it to the other's attention without pushback or defensiveness. Respect the other person's perspective. For the most part, not worried about offending each other, but in the event of any issues have agreed on this format of discourse to bring to light and resolve any issues.
Github Projects
Day 1 Agenda: Flesh out DTR Get after it tomorrow for wireframing and repo setup
Additional Notes: