Project: Battleship
Group Member Names: Trevor Nodland, Peregrine Balas
What are each of our learning goals for this project? What drives us in this project? T: Satisfy project learning goals outlined in the Turing Battleship Project. P: Explore working in a pairing. T: Learning how to work with Git and GitHub better. T: Drive is to get top scoring on the project. P: To complete a larger scale project than previously faced with.
What is your collaboration style? How do you feel about pair programming vs. divide-and-conquer approaches? P: Overview high level concepts, understand what we're trying to do and then work out how to do it. T: Favors starting with Paired programming P: Same. Leaving Potential to divide-and-conqure later once more developed.
How do you communicate best? How do you appreciate receiving communication from others? T: Face-to-face, in person. Looking at problems togther. P: Same.
How would you describe your work style? T: Short bursts of hyper-focus, remove distractions P: Same
What are each of our strengths? How can our strengths complement each other? P: Strong listener, open to trying other ways than I might think of on my own/trying out ideas we aren't sure will work. T: Strong listener, not getting stuck in too many different options. Trying out an idea rather than overthinking. T/P: Both good listeners. Comlementary strengths of being open to ideas and implementing them.
What’s gone well or poorly in your previous projects? T: Well - Applying TDD. Poorly - Didn't finish Iteration 2. P: Well - Get through iteration 4. Poorly - Didn't flesh out Iterations to meet requirements for 4 scoring in Rubric for all categories.
How will we set direction and make decisions as a team? P: Whiteboarding T: Psuedocoding Working on high level concepts and moving down into low level functionality
How will we overcome obstacles? P: Studying - as a pair and individually on any concepts that are beyond our initial understanding. T: Relying on each other for help first, then going to others after.
What do you need (resources, environment, communication) to do your best work? P: Removing obstacles, open/honest communication, time to eat/sleep/unwind. T: Same.
What scheduling restraints do you have? What are your scheduling preferences? T: Open schedule from restraints. Afternoon/evening is preferred. P: Open schedule from restraints. Morning from 8 to 9 works and afternoon/evenings.
What is your style for giving feedback? Does anything ever hold you back from giving feedback? T: Taking others feelings into account and sometimes holding back from being critical in favor of being kind. P: Same. Sometimes I won't know how to best give feedback constructively and will delay.
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? T: Strength - Engraining understanding of TDD. Needs Improvement - Vocabulary/terms and ideas behind the vocabulary. Help - by sharing ideas. P: Strength - Practicing TDD and exercises. Needs Improvement - Implementing ideas/Restraining ideas to first satisfy MVP. Help - Keeping what we need to do vs. what we'd like to do for the project seperate.
What tools do you want to use to manage the project? P: Possibly - Waffle.io (I haven't tried it yet though), Slack for sure to communicate, and GitHub (obviously). T: Same.
How do you want the group to solve problems when members run into issues with features of the project? T: Check with each other first, then out to others P: Same. Google searches are a personal favorite.
How do you know if a project is successful? How can we achieve that as a group? P: Full understanding of what we've made and meeting all goals/requirements. Feeling good about that too. T: Same. Diligent, communicative
How will we recognize each other's successes and celebrate them? P: Pacing, reviewing, checking-in for understanding along the way and appreciating each of our starting points. T: Same
Day 1 Agenda: P: Review project T: Start coding
This looks great! Glad to see the thorough convo!