- What have you learned about the use of agile vs. waterfall in software projects?
- Waterfall can be time consuming and expensive when using it for projects. Agile is better in the way that you can find out early enough through the process when to stop and rethink where the project stands and how to better it.
- 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 worked together and apart and used the project folder in our github to check off what needed to be done first and chose together who would take over what part of the project;
- What role did you take on in the project?
- No special part, we all worked equally as hard in every part of the code and we were more of a flat group.
- What changes would you make to your approach in future team projects?
- No changes, I believe we worked really well on our parts individually and together.
- How does retro function in a team project?
- We checked in with eachother in the mornings to see how things were going or slacked chatted in our slack group chat.
- In your team retro, how did you engage in the feedback process? What principles of feedback did you use in these conversations?
- We all worked just as hard and did really great, we also had a lot of laughs about our struggles through the project together so I have no negative feedback to give out. We all did great, we made a great team.
- 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?
- I was clear and to the point of what I wanted, and my teammates were good at understanding and listening. As well as having the same goals of not only learning through this but doing their best for the project.
This is a good start; for future reflections as you prepare for interviews, I would appreciate some more specifics and examples