1. What have you learned about the use of agile vs. waterfall in software projects?

The agile process provides more feedback more often, allowing for quicker corrections and adjustments.

2. 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 met every day at the end of the day (if we hadn't already met) to make sure we all had clear goals for the work to be accomplished that evening. The next time we were together, we would review and merge what we had done, as well as provide help if anyone was stuck. We also created a slack group for the project to allow for easier communication.

3. What role did you take on in the project?

I kept the project organized. I contributed significantly in the testing aspect of the project.

4. What changes would you make to your approach in future team projects?

-I will be more diligent in maintaining a clean master branch on github.

5. How does retro function in a team project?

We retroed every day at least once to get an idea for how everyone was feeling about the current state of the project. At the final retro (as well as throughout the project), we shared how each member had brought their own strengths to the project.

6. In your team retro, how did you engage in the feedback process? What principles of feedback did you use in these conversations?

We discussed aspects of the project that were going (went) well and that were going (went) poorly. We tried to use specific language without making assumptions to give feedback for each other.

7. 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?

My ability to provide feedback is not great, but by being intentional this project, I have seen improvement already. Giving feedback is less awkward and is more direct in a kind way. I want to continue improving in this aspect.