Created
November 6, 2018 17:27
-
-
Save geoffreyadebonojo-zz/aa9aa2209c7e549ea07ea252ba317bd9 to your computer and use it in GitHub Desktop.
This file contains 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
| 1. Agile is more reactive to changes downstream, as the production is always being re-evaluated, from design, to implementation. | |
| 2. We used Waffle and Slack. We were aggressive about everyone staying on the same page-- it made debugging much quicker. | |
| 3. I made sure everybody was talking to one another, and that everyone's responsibilities were clear. | |
| 4. I plan to embrace the role of coordinator earlier in the process. | |
| 5. It's a chance to celebrate what you did right, and to make plans to improve what you did wrong. | |
| 6. We made sure to be actionable, specific and kind in our feeback. | |
| 7. I would describe my ability to give feedback as mixed. I excel at appreciation feedback. This experience has improved my willingness to show appreciation for my teammates. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Complete. This shows an understanding of agile and how to implement it, and I would encourage you to go deeper with the specifics when in interviews to both demonstrate that you're competent in implementing a strong work process and also to show that you stand out from other junior devs in your understanding here.