agile-project-reflection.md

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

Both are viable options for project management. However, generally speaking, waterfall leaves little space to correct later on in the project - and often includes an expensive backflow when things don't match up with the spec docs. Agile, like it's name, provides the team more flexibility to make adjustments throughout the process. Feedback is emphasized as the project is shown to customers, only to iterate through the process again for more improvements.

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

Our project management tool of choice was Trello. We added all the tasks on a board and split them up into separate columns. We held retros after each day of work, to review what we complete, where we struggled, and how we could potentially help each other out.

What role did you take on in the project?

In different situations I took on different roles. At times I acted as a leader, and delegated task to others. We all took turns being driver and navigator. Other times I took a more supportive role, trying to uplift the team with my positivity.

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

Overall, I think we as a team did a great job, and for that reason, I am confident that we will receive a good evaluation. That said, I think we could have delegated tasks better to split up work, get more done, and ultimately save ourselves time. In future projects, I hope to be aware of this in the moment, and take it upon myself to have a discussion with my teammate about how we could better make use of the time.

How does retro function in a team project?

After each work day we would always come together to discuss what we were able to complete that day, how we felt about it, and when we would meet next. This was a great way to benchmark the project and minimize stress, as we were always aware of where we stood.

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

Both of my teammates were easy to work with and very open to coachable feedback. After someone was able to complete an important piece of the project, I tried to make sure they were recognized with appreciative feedback.

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?

At times I have trouble communicating negative feedback to team members. I think Turing has created a space for me that encourages these hard conversations and promotes coachable feedback. For that reason, I feel more comfortable receiving feedback, and giving it to others. In my experience, other members of my cohort are very accepting to my feedback, whether positive or negative, and ultimately it provides a space to have a deeper conversation.

Great reflection here -- you have lots of great details to talk through your work process, nice job!