# PD Agile Feedback

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

Agile tends to result in a product that does what it's supposed to do and benefits the user. Waterfall tends to actually produce a product less often, and is more likely to circle endlessly and waste money.

### 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 used Trello and retrod periodically to ensure everyone was held accountable.

### What role did you take on in the project?

I was the planner, the one keeping everyone on track and delegating work for the most part.

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

More time working as a team in-person and less remote work. More time planning the overall structure of the project and high-level planning.

### How does retro function in a team project?

To inspect and adapt the process.

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

We did code reviews and gave appreciation feedback for the work we all did. We then offered suggestions on refactoring if neccessary in order to keep the project clean and functional.

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

This is a skill I'm trying to actively improve while at Turing, and I used many of the points we learned in the previous PD sessions in order to give feedback that would be taken well and used. Ensuring that what I said didn't make assumptions and was delivered in a way that did not feel aggressive or mean.