Created
May 31, 2019 14:08
-
-
Save CLLane/93c256f8cab22cebd51f5c8337117eed to your computer and use it in GitHub Desktop.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
# What have you learned about the use of agile vs. waterfall in software projects? | |
- I have learned that while waterfall has been a industry standard for years the agile | |
method of approaching problems is more dynamic and results in less backtracking. We | |
implemented an agile approach to this most recent project with sprints being 1 or 2 days | |
long and found that the progression and final product exceded our expectations. | |
# 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 utilized Trello, and made a strong attempt to retro at the end of each sprint. | |
As a whole I feel like we stuck to our DTR and modified our approach to problems | |
as they came up. | |
# What role did you take on in the project? | |
- In my project I took the role of moderator and also a bit of an anchor in the sense | |
that I tried to actively keep things from going off topic. I did a lot of refactoring | |
also a fair amount of writting new code. I tried to keep us on task and keep open avenues | |
for letting our stress and anxiety to be released. | |
# What changes would you make to your approach in future team projects? | |
- I would be more rigid in our break time and also be more conscience about how long | |
spend on a problem before we seek help. | |
# How does retro function in a team project? | |
- Retro is supposed to be a time to revisit your past sprint, and speak about what went | |
well and what didnt. It should be a time to speak about pertinent issues and your change in | |
needs going into the next sprint. | |
# In your team retro, how did you engage in the feedback process? | |
# What principles of feedback did you use in these conversations? | |
- We made it a point to give eachother time to speak, we highlighted the things we agreed | |
upon and spoke about the things we didnt both see as needing to be worked on. We were careful | |
to make sure things were not brushed over and if there was an reason to speak on a topic it was | |
worth our time. | |
# How would you describe your ability to communicate feedback? | |
- I feel that I am honest and open with my communication, but sometimes there can be a bit of curtness to my style. | |
# How has this experience affected your communication skills? | |
- I have had to explain myself from time to time, and have become more conscience of this attribute. | |
# How do you want to improve in your ability to communicate feedback? | |
- I would like to find that balance of feeling fulfilled in my by feed back, but also | |
package it in a more receptive package. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Great reflections here, and I appreciate the specifics on your group's process and what you'd like to improve. Nice work!