What are each of our learning goals for this project? What drives us in this project?
We want to come out of the end of this project with a funcitoning application completed within the timeframes we have set. We would like to have a complete understanding of the code written, and have that code be DRY with no bugs.
What is your collaboration style? How do you feel about pair programming vs. divide-and-conquer approaches?
When writing code, we will be driver/navigator alternating between group members daily. Should we come across something we do not know how to solve or make work, we will divide and conquor the research, coming back together to compare solutions and notes. This will ensure that no member of the group is left behind and also that we keep to our timeframes.
How do you communicate best? How do you appreciate receiving communication from others?
If what we need to talk about anything involved, we will endeavor to have a video/voice call with a healthy dose of written summaries in the Slack group we have made.
How would you describe your work style?
Naomi: I have a tendancy to hyperfocus and sometimes I have to be reminded to pull back and take a big picture. Scheduled poms are not my thing, I like to work until I am tired and then break for about twenty. I prefer to talk the entire time that I am working through a problem.
Amy: I'm more introverted, so I can prefer silent working space. I tend not to verbalize until my thoughts are clear, and that I am understanding everything. I like to write out code I don't understand in order to gain a better understanding of the content.
Brigette: I tend to talk everything out loud. I'm more of a research before writing kind of person, especially when syntax is shakey. I like going back over code that we wrote that day and seeing if I can understand it all by the end of the session.
What are each of our strengths? How can our strengths complement each other?
Naomi: I am very persistent. I will keep going at something until I solve it, and it is hard to frusterate me.
Amy: I am also presistent. I am getting better at knowing when to step away.
Brigette: I'm gonna third that persistence thing.
Getting the feeling that we will be UNSTOPPABLE.
What’s gone well or poorly in your previous projects?
Project to freetime to solo study balance was off with all of our previous projects.
How will we set direction and make decisions as a team?
Communially with as much communication as needed to reach a consesus.
How will we overcome obstacles?
By researching, discussing, and if needed, calling on mentors.
What do you need (resources, environment, communication) to do your best work?
Good internet!
What scheduling restraints do you have? What are your scheduling preferences?
Break inbetween school and project time! 2-2.5hrs outside of scheduled class time MAX. Will keep communication up to make sure we are all on the same page with our work schedule, and what we are on track to accomplish.
What do you identify as being your biggest strength(s) technically, as they relate to this project? Where do you feel you could use improvement in your technical skills, as they relate to this project? How can our team help support you in improving these skills?
Brigette: HTML and CSS! I could improve on JS, and team will help by working through things with me
Naomi: I am moderately profeciant in JS and I have a background as a proofreader, so I am good at spotting issues with symantix. I want to learn about local storage.
Amy: I'm feeling more confident in JS and I also want to improve in JS. I also want more experience with seperating the DOM and the data model.
What tools do you want to use to manage the project?
Slack, Zoom, Github, and mentors!
How do you want the group to solve problems when members run into issues with features of the project?
Open and honest communication with no judgement! Reflective listening also.
How do you know if a project is successful? How can we achieve that as a group?
If it works with no bugs up to the minimum completion level! And the HTML and CSS are solid. Also, for all of us to have a solid understand of all code written and to be able to explain all lines of code in the project.
Doing daily retros after each session!
How will we recognize each other's successes and celebrate them?
Shouting. Lot of affermitive shouting.