Agile Workflow PD Reflection.md

Agile & Feedback Reflection Guidelines

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

• First off, it was a pleasure to have Jeff lead this lecture. I appreciate so much that he was able to review these concepts with our Mod 1 group. Agile and waterflow both have the same steps but vary in their approach to software development. Waterfall is a more linear progression from requirements, to design, to development, into testing and from there to deployment. The process results in a big outcome at the end which can quickly become outdated because the process is so long. The end result must be clearly defined at the beginning, there is no feedback on the product until the process is complete, and the product is never accountable to the customer until the very end. Alternatively, Agile workflow is more of an iterative, circular workflow than waterfall. It tightens the process, shortening the distance between the customer and the product, and allows the development team to course correct early. Agile workflow pushes quickly to a minimum viable product and improves from there based on user feedback and needs. While you are able to generate revenue earlier with Agile there is no real way to estimate the total cost of a project and your cross functional teams must work effectively in order for the agile workflow to function properly.

1. 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 team kicked off our project with a DTR. We discussed our expectations, our learning goals, and our availabilities and from there made agreements around the next two weeks of the project. We utilized three day sprints to drive our development and retro-ed following the first week of work as a group. I will request an additional retro following our project evaluation to ensure we tie up loose ends and address goals not met and to give the opportunity for feedback and appreciation.

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

• Interestingly I think we all shared equal roles and responsibilities throughout the project. I was able to both lead and follow, drive and navigate, coach and appreciate. We worked closely as a team on the development of the project and therefore I was happy to get additional experience with HTML, CSS and JavaScript. I was able to be consistent, reliable, and available. I was supportive, a friend, and an accountabilibuddy.

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

• I overall think that the project and the functioning of our team and my role on the team was successful. I want to keep myself focused on the people and stay away from getting too caught up in the code. I did a good job of listening to my needs while ensuring the commitments that I made to the team were satisfied.

1. How does retro function in a team project?

• Retros allow teams to improve quickly by giving the group an opportunity to self-correct and communicate early and often. It allows the team to reflect on moments of success and to discuss and learn from challenges recently encountered. They should be completed after sprints so that improvements can be identified and implemented on the next project phase.

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

• Our team put our feedback in three categories: things that were going well, things that can be improved, and things that we want to implement moving forward. We gave ourselves a moment, prior to discussing as a group, to reflect individually so that we were prepared to discuss as a group during the retro.

1. 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 think that I am fairly competent when it comes to giving feedback. I believe in the power of clear expectations and then holding people accountable to those expectations. I like for teams to function properly and for individuals to feel successful and appreciated. While I feel that I have the skills I will need to get more comfortable expressing myself to my new classmates and teammates. I will try to continue to develop these skills and work to provide both feedback and appreciation to my teammates.

Great reflection here! I really appreciate these notes on your process and your takeaways on agile, nice work!