yaleksandrova · June 5, 2019 20:37 · May 31, 2019 · May 31, 2019 · May 31, 2019 · May 31, 2019
diff --git a/FeedbackReflection.md b/FeedbackReflection.md
@@ -1,4 +1,4 @@
-##What have you learned about the use of agile vs. waterfall in software projects?##
+## What have you learned about the use of agile vs. waterfall in software projects?
 
 We used a Waterfall approach because thats what we felt worked best for our group. 
 Waterfall is a linear approach to software development. In this methodology, the sequence of events is something like this:
@@ -13,27 +13,27 @@ Waterfall is a linear approach to software development. In this methodology, the
 
 We focused on finishing each stage before we began the next one. 
 
-##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.)?
+## 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 GitHub project manager, where we created cards for each phase and would take on tasks individualy and move them to according stages as we worked through them. Of course discussng on which part each team memeber was working on. 
 
-##What role did you take on in the project?
+## What role did you take on in the project?
 I would say my role was more in executing. I enjoy implementing solutions and work hard to deliver set goals.
 
-##What changes would you make to your approach in future team projects?
+## What changes would you make to your approach in future team projects?
 I truly enjoyed working with my team. However, it was a bit of a challenging at first to adjust to each others working style, so i would allow people to work which ever way the prefer. 
 
 
-##How does retro function in a team project?
+## How does retro function in a team project?
 We had clear and effective communication to set goals for Idea Box project, which included discussing what needed to be done, created action cards and were able to easily adapt to any changes. We effortlessly moved through the stages from:
 Forming to Storming to Norming to Performing and Adjourning. 
 
 
-##In your team retro, how did you engage in the feedback process? What principles of feedback did you use in these conversations?
+## In your team retro, how did you engage in the feedback process? What principles of feedback did you use in these conversations?
 We had clear communication and understood that if there were any critisism it was only constructive critisism and nothing personal. This way we were able to improve our learning as a team and coding process as well as the end result for the project. 
 
 
-##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?
+## 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 believe it is important to communicate clearly and with empathy. During communication i focus on listening, observing and empathizing. It is also helpful to understand the differences when I communicate through face-to-face interactions, phone conversations or digital communications, like email and social media. 
 
 

diff --git a/FeedbackReflection.md b/FeedbackReflection.md
@@ -1,4 +1,4 @@
-##What have you learned about the use of agile vs. waterfall in software projects?
+##What have you learned about the use of agile vs. waterfall in software projects?##
 
 We used a Waterfall approach because thats what we felt worked best for our group. 
 Waterfall is a linear approach to software development. In this methodology, the sequence of events is something like this:

diff --git a/FeedbackReflection.md b/FeedbackReflection.md
@@ -1,25 +1,42 @@
-What have you learned about the use of agile vs. waterfall in software projects?
+##What have you learned about the use of agile vs. waterfall in software projects?
 
-The Waterfall Methodology
-Waterfall is a linear approach to software development. In this methodology, the sequence of events is something like:
+We used a Waterfall approach because thats what we felt worked best for our group. 
+Waterfall is a linear approach to software development. In this methodology, the sequence of events is something like this:
 
-Gather and document requirements
-Design
-Code and unit test
-Perform system testing
-Perform user acceptance testing (UAT)
-Fix any issues
-Deliver the finished product
-In a true Waterfall development project, each of these represents a distinct stage of software development, and each stage generally finishes before the next one can begin. There is also typically a stage gate between each; for example, requirements must be reviewed and approved by the customer before design can begin.
+-Gather and document requirements
+-Design
+-Code and unit test
+-Perform system testing
+-Perform user acceptance testing (UAT)
+-Fix any issues
+-Deliver the finished product
 
-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 focused on finishing each stage before we began the next one. 
 
-What role did you take on in the project?
+##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 GitHub project manager, where we created cards for each phase and would take on tasks individualy and move them to according stages as we worked through them. Of course discussng on which part each team memeber was working on. 
+
+##What role did you take on in the project?
+I would say my role was more in executing. I enjoy implementing solutions and work hard to deliver set goals.
+
+##What changes would you make to your approach in future team projects?
+I truly enjoyed working with my team. However, it was a bit of a challenging at first to adjust to each others working style, so i would allow people to work which ever way the prefer. 
+
+
+##How does retro function in a team project?
+We had clear and effective communication to set goals for Idea Box project, which included discussing what needed to be done, created action cards and were able to easily adapt to any changes. We effortlessly moved through the stages from:
+Forming to Storming to Norming to Performing and Adjourning. 
+
+
+##In your team retro, how did you engage in the feedback process? What principles of feedback did you use in these conversations?
+We had clear communication and understood that if there were any critisism it was only constructive critisism and nothing personal. This way we were able to improve our learning as a team and coding process as well as the end result for the project. 
+
+
+##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 believe it is important to communicate clearly and with empathy. During communication i focus on listening, observing and empathizing. It is also helpful to understand the differences when I communicate through face-to-face interactions, phone conversations or digital communications, like email and social media. 
+
 
-What changes would you make to your approach in future team projects?
 
-How does retro function in a team project?
 
-In your team retro, how did you engage in the feedback process? What principles of feedback did you use in these conversations?
 
-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?
diff --git a/FeedbackReflection.md b/FeedbackReflection.md
@@ -0,0 +1,25 @@
+What have you learned about the use of agile vs. waterfall in software projects?
+
+The Waterfall Methodology
+Waterfall is a linear approach to software development. In this methodology, the sequence of events is something like:
+
+Gather and document requirements
+Design
+Code and unit test
+Perform system testing
+Perform user acceptance testing (UAT)
+Fix any issues
+Deliver the finished product
+In a true Waterfall development project, each of these represents a distinct stage of software development, and each stage generally finishes before the next one can begin. There is also typically a stage gate between each; for example, requirements must be reviewed and approved by the customer before design can begin.
+
+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.)?
+
+What role did you take on in the project?
+
+What changes would you make to your approach in future team projects?
+
+How does retro function in a team project?
+
+In your team retro, how did you engage in the feedback process? What principles of feedback did you use in these conversations?
+
+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?
No results found