benjamin-firth · September 12, 2019 14:40 · allisonreusinger · Sep 16, 2019
diff --git a/gistfile1.txt b/gistfile1.txt
 Agile & Feedback Reflection 

 Benjamin Firth

 Check Yo Self Project / Mod One
 ________________________________

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

 -Agile is much more reflective.  It's a constantly looping process with a lot of outside feedback.
 In reall application this can feel like it takes more time, but in reality the time it saves in negating errors makes up for it in the end.

 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 relide heavily on GitHub Projects, so that we could break up larger sections in to more manageable tasks.  From there we could delegate more effectively, and then circle back if things needed changing or weren't working out.

 What role did you take on in the project?

 -I was in charge of the Project board, and keeping things up to date and organized.  Sometimes this did mean reeling us in, and making sure that we refocussed on our goals and tasks at hand.

 What changes would you make to your approach in future team projects?
 -I would break up project tasks into even smaller portions, but keep them under larger categories.  That way a person could work through something incrimentally while going after big sections in the long run.

 How does retro function in a team project?

 -Retro's need to be planned, so that they aren't brushed off for continued work.  Especially with the agile workflow, it's important to retro early and often and after the push.  That way we can learn from our mistakes and triumphs and improve going into the future.

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

 -We based our retros largely on personal wins, challenges, and things we think could improve the groups functionality as a whole.  This way we learned what works for each other, and what we can change based on that.

 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 want to give more actionable feedback, that isn't biased by my enjoyment working with others.  Sometimes I worry something might come across the wrong way, so I don't say it.  I want to be able to phrase things better so that people can learn from my thoughts, and I can learn from their communication about it.  I would say I definitely improved on this skill during this project.
	Agile & Feedback Reflection

	Benjamin Firth

	Check Yo Self Project / Mod One
	________________________________

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

	-Agile is much more reflective. It's a constantly looping process with a lot of outside feedback.
	In reall application this can feel like it takes more time, but in reality the time it saves in negating errors makes up for it in the end.

	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 relide heavily on GitHub Projects, so that we could break up larger sections in to more manageable tasks. From there we could delegate more effectively, and then circle back if things needed changing or weren't working out.

	What role did you take on in the project?

	-I was in charge of the Project board, and keeping things up to date and organized. Sometimes this did mean reeling us in, and making sure that we refocussed on our goals and tasks at hand.

	What changes would you make to your approach in future team projects?
	-I would break up project tasks into even smaller portions, but keep them under larger categories. That way a person could work through something incrimentally while going after big sections in the long run.

	How does retro function in a team project?

	-Retro's need to be planned, so that they aren't brushed off for continued work. Especially with the agile workflow, it's important to retro early and often and after the push. That way we can learn from our mistakes and triumphs and improve going into the future.

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

	-We based our retros largely on personal wins, challenges, and things we think could improve the groups functionality as a whole. This way we learned what works for each other, and what we can change based on that.

	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 want to give more actionable feedback, that isn't biased by my enjoyment working with others. Sometimes I worry something might come across the wrong way, so I don't say it. I want to be able to phrase things better so that people can learn from my thoughts, and I can learn from their communication about it. I would say I definitely improved on this skill during this project.