| DTR: Define the Relationship | |
| Project: ENIGMA | |
| Group Member Names: Liam Barstad, Tim Joo | |
| Project Expectations: What does each group member hope to get out of this project? Both of us want to get more experience learning the nuances of working together in pair programming and getting better with algorithms. | |
| Goals and expectations: In the context of scoring rubric, our goal is to hit 4's across the board but our expectation is to hit 3's across the board. Liam's goal is to have our code readable, accessible, clean, and concise. Tim's goal is to have clean code, his expectation is to having working code. | |
| Team strengths: We have a mix of strengths and we believe that our team strength is that we'll dissect the problems in different ways and analyze different solutions for those problems. | |
| How to overcome obstacles: An emphasis on open communication, leveraging mentors and asking people for help is going to extremely important to overcoming obstacles. Also reviewing prior lesson plans and pooling strengths and resou |
| DTR: Define the Relationship | |
| Project: ENIGMA | |
| Group Member Names: Liam Barstad, Tim Joo | |
| Project Expectations: What does each group member hope to get out of this project? Both of us want to get more experience learning the nuances of working together in pair programming and getting better with algorithms. | |
| Goals and expectations: In the context of scoring rubric, our goal is to hit 4's across the board but our expectation is to hit 3's across the board. Liam's goal is to have our code readable, accessible, clean, and concise. Tim's goal is to have clean code, his expectation is to having working code. | |
| Team strengths: We have a mix of strengths and we believe that our team strength is that we'll dissect the problems in different ways and analyze different solutions for those problems. | |
| How to overcome obstacles: An emphasis on open communication, leveraging mentors and asking people for help is going to extremely important to overcoming obstacles. Also reviewing prior lesson plans and pooling strengths and resou |
| Over the course of the last month, I have seen how my strengthsfinder attributes are pronounced in my interactions with classwork and other students | |
| I have found it interesting seeing myself and my actions through that lens, and it has given me a greater appreciation of myself, as well as highlighting | |
| areas in which I need to improve. My top three strengths are learner, command, and analytical. the learner archetype is one that I hope to embody, along | |
| with humility and a great lust for knowledge and an eagerness to accept new challenges. I feel as though Turing has helped bring out these qualities in me | |
| by introducing me to a vast wealth of information and opportunities to gain literacy in the wide world of programming. I strive to be a dutiful learner; tenacious | |
| and enthused. To contrast, I have found that the command archetype has the potential to work against me. Left unchecked, I can have a tendency to exert too much | |
| control over a situation. Command is nothing without communication and the ability to h |
Group Member Names:
Group members can meet on weekdays until 7-8, preferring afternoons on weekends. Aaron will have to leave sometimes after school to watch his dog.
| Currently, I am doing well at staying on top of group discussions and completing my share of the workload pre-emptively to | |
| minimize the stress later. I can be reliable, and helpful at answering questions. I have also become much better at pairing and | |
| using the driver/navigator workflow to tackle problems faster. I am using my command trait in better ways, i.e. being less | |
| territorial and authoritative, and being more inclusive. I have found it easier to work collectively and prop other members up | |
| rather than divide myself to my own work. I would like to continue to develop this trait, to the point where I can seamlessly | |
| pair and collaborate on tasks that require knowledge that team members have not yet fully integrated. As a team mate, I have | |
| noticed that, if I am left to my own devices, I will sometimes move forward to fast and neglect to leave space for my team mates | |
| to work on and learn the material. This, I believe, is a failure of communication on my part, and I should always take the time | |
| to run my pla |
| Date of feedback conversation: | |
| 8/24/17 | |
| How did you prepare for the conversation? | |
| I had thought through what the outcomes of our project had been, where each team member needed to improve, and what they did | |
| well. | |
| How did the conversation go for you? What was easy about the conversation? What was more difficult? |
| (paraphrased and adapted from previously written and misplaced reflection) | |
| This module, we have integrated the use of waffle cards effectively, most evident in our current project Little Shop. I think | |
| what made it easier to use waffle was the fact that, on this project, the spec was divided into user stories. User stories are | |
| small, bite-sized chunks, that group members are not shy pulling down and completing. When the project was in whole iterations, | |
| the tasks were often open-ended and more difficult to track progress. Regardless, more thought should have been given to dividing | |
| bike-share more effectively. I have found since that it is much more effective to work in the same room with group members, but | |
| seperately. That way, questions can be asked and answered quickly, but the whole group time is not spent laboriously going over | |
| the plan. I enjoy the agile workflow, as it allows for greater compartmentilization and makes sure that each part of the program | |
| is working before moving on to the next. It also me |
| Name of contact | |
| Alex Schaefer, Ryan Tyler, Bekah Lundy | |
| Date of contact | |
| 9/15/17 | |
| Outcome (i.e., did you get a response? If not, what is your follow-up plan? Did you meet? When? What was the result?) |
| ### [Project Title] | |
| BlindChat | |
| ### Pitch | |
| This is an app that will match people at random (I will also make a version that matches based off gender, orientation, and interests, to test its viability | |
| as an actual dating app) and place them into a blind chatroom with each other, at which point they will have to talk to each other for a certain amount of | |
| time to reveal each other's photos. |
| ### [Project Title] | |
| JamHQ | |
| ### Pitch | |
| JamHQ will be an application designed in the same breath as sites like Facebook and LinkedIn to allow musicians to share, collaborate, | |
| and connect directly with venues and producers. | |
| ### Problem |