What have you learned about the use of agile vs. waterfall in software projects? The main takeaway is that agile can be more flexible while making a project in that it is more responsive to any changes that can or should be made.
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 tried implementing an agile method of getting feedback from one of our three different instructors (trying to rotate between them). The hope was that they would bring up a point that maybe we were heading in the wrong direction and we could course correcrt before going too deep in one direction.
What role did you take on in the project? Myself and one of the other two teammates were definitely storming and butting heads early on, but I think towards the end of the project I took on more of the leader position solely because I had the most knowledge of how to tackle the more advanced problems the project faced.
What changes would you make to your approach in future team projects? Read through the rubric more thoughroughly and have a team discussion on how the end goals will affect our early goals.
How does retro function in a team project? We we're taking mini-retors at the end of each day to discuss what went well and what could be improved.
In your team retro, how did you engage in the feedback process? What principles of feedback did you use in these conversations? We implemented whiteboarding to make sure everyone was on the same page as far as the project was going.
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? Hopefully next project it won't take a scheduled event for me to voice my opinions on how to improve workflow. I think it improved my communication skills because my input was well received and I don't think I will be as hesistant to voice my opinion.
Complete. Nice reflection here!