megstang/Agile & Feedback

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

During the lecture with Jeff, I learned that the Agile approach is more appealing than waterfall. Agile is a process that everyone works on together, continueing to loop back to teh starting spot, add/adjust, and move on. Waterfall is used when you want to make $$$ quick, but there are flaws in this, and that is mainly that you would later need to redo everything once a mistake or addition was 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 used waffle.io to manage tasks, and we also did nightly standups over slack where we would each say what we did that day, and what we plan on doing tomorrow. This is something we tried out for the first time, and I really appreciated this.


What role did you take on in the project?

I'm unsure if this questions means technically or leadership-wise. I tried to check in with people frequently to make sure that we weren't duplicating each others code. With this project specifically, it's very easy to start making something, realize you need something else, and then build that. However, that "something else" could have been what a different person was working on. I also pushed for getting all of the cards on waffle in their proper columns.


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

I would have benefited from more paired work. We set up the whole project as all four of us, but then worked individually for the rest of it. I think it would have been good to split off into two and two and work that way. I wonder if it would have been more efficient that way too?


How does retro function in a team project?

It helps us all to be on the same page and to understand each other.


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

For the most part, we spoke about the Johenri (was that the name?) chart that we made for ourselves. It was interesting to see what we thought of ourselves and what others knew about us that we didn't know about ourselves. We also spoke about our appreciation for each of us during the project... we had good energy on our team, and we were all very encouraging of each other and we all appreciated that about the group.


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 feel like I am good with giving positive feedback, but I still struggle with coaching feedback. I think I mainly struggle with it becuase I know that when I get coaching feedback, I get triggered a bit, but overall I do appreciate it. I would like to improve with taking feedback and using it to better myself, and also giving constructive feedback as well.
	What have you learned about the use of agile vs. waterfall in software projects?

	During the lecture with Jeff, I learned that the Agile approach is more appealing than waterfall. Agile is a process that everyone works on together, continueing to loop back to teh starting spot, add/adjust, and move on. Waterfall is used when you want to make $$$ quick, but there are flaws in this, and that is mainly that you would later need to redo everything once a mistake or addition was 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 used waffle.io to manage tasks, and we also did nightly standups over slack where we would each say what we did that day, and what we plan on doing tomorrow. This is something we tried out for the first time, and I really appreciated this.



	What role did you take on in the project?

	I'm unsure if this questions means technically or leadership-wise. I tried to check in with people frequently to make sure that we weren't duplicating each others code. With this project specifically, it's very easy to start making something, realize you need something else, and then build that. However, that "something else" could have been what a different person was working on. I also pushed for getting all of the cards on waffle in their proper columns.



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

	I would have benefited from more paired work. We set up the whole project as all four of us, but then worked individually for the rest of it. I think it would have been good to split off into two and two and work that way. I wonder if it would have been more efficient that way too?



	How does retro function in a team project?

	It helps us all to be on the same page and to understand each other.



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

	For the most part, we spoke about the Johenri (was that the name?) chart that we made for ourselves. It was interesting to see what we thought of ourselves and what others knew about us that we didn't know about ourselves. We also spoke about our appreciation for each of us during the project... we had good energy on our team, and we were all very encouraging of each other and we all appreciated that about the group.



	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 feel like I am good with giving positive feedback, but I still struggle with coaching feedback. I think I mainly struggle with it becuase I know that when I get coaching feedback, I get triggered a bit, but overall I do appreciate it. I would like to improve with taking feedback and using it to better myself, and also giving constructive feedback as well.