What have you learned about the use of agile vs. waterfall in software projects? Agile is great for things that you need to learn about while on the project and waterfall is more like everything is thought out before hand with no learning
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.)? We were agile most of the way through, meeting up after school and over the weekend as much as we could but at the end i kind of fell off because of some stuff I had to do at home and I didnt communicate the reason why which prolly coulda been better.
What role did you take on in the project? I don't know what role I took. I created some code, had some ideas, tried to learn things.
What changes would you make to your approach in future team projects? Ummmm, not much, we had good meet up. We had changes to the things we wanted to change each time.
How does retro function in a team project? Not sure, its hard to do a full retro on the timeline we have but I think we did well
In your team retro, how did you engage in the feedback process? What principles of feedback did you use in these conversations? We didn't neccessarily talk about feedback. So not at all I guess.
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? Not great. I think I'm okay at comminicating thing about the project but not actual feedback. I'll try to communicate feedback when I think about it I guess
Complete; these are good starting reflections, but I would encourage you to think more critically about the roles you take on in team projects to be able to describe them in interviews.