Q. What have you learned about the use of agile vs. waterfall in software projects? A. I learned that I enjoy the agile workflow more because it allows you to focus in on key parts of a project. And spend less time worrying about the minute details that may not effect the project as a whole. Waterfall does seem useful in some cases, but I learned that Agile is what will help most during my stay at Turing, and potentially in my professional career.
Q. How did you and your group approach project management in this project (what tools did you use, how did you hold each other accountable, etc.)? A. We used Trello to break down all the goals for the project. We chose to work together once every 1-3 days, and have retro's each day to keep everyone in the know regarding new changes/challenges within the project.
Q. What role did you take on in the project? A. We all shared the same responsibilities in varying degrees. I think my role was to handle the .js tasks, and work with the team on ensuring all the functionality fit into the overall vision that Edward had drawn out for the project.
Q. What changes would you make to your approach in future team projects? A. I think spending more time checking in on the team's contributions. We trusted that everyone's code was good so long that it worked, but we could have spent more time in our daily retro's discussing the 'why' and 'how' behind our code submissions.
Q. How does retro function in a team project? A. We chose to do daily retro's to ensure everyone was on the same page and working on their specific tasks. I really enjoyed this aspect of the project, as we were always taking everyone's 'temperature' to ensure they weren't overburdened or stressed. In your team retro, how did you engage in the feedback process? What principles of feedback did you use in these conversations?
Q. How would you describe your ability to communicate feedback? How has this experience affected your communication skills? How do you want to improve in your ability to communicate feedback? A. For me personally, I liked communicating with the group about project details. However, I think that I can be a little more critical or assertive when discussing the team's code submissions.
Great reflections here! I appreciate the specifics on your group's process and ways you'd like to continue to improve