I found Agile interesting because throughout my time at Turing thus far I've been using a modified version of Agile. And it works.
In essense my project partners and I have chosen to select important tasks together at the start of every day. We work together on each issue, usually testing, then creating, then improving the design.
We stay late, then before we part ways we would outline tasks we wanted to try that night using Github issues. Every morning we regroup, prioritize, get feedback on things we aren't certain about, and repeat the cycle.

### What went well:

Communication. Deciding which parts of the project to accomplish next.  Getting outside feedback from more advanced students/instructors.
Getting user feedback. My last project had a cool feature that took 3-5 seconds to load once clicked. My friends in the Backend pointed out that they had no idea if anything was happening and would click multiple times.
To fix this we added a loading animation and no one has since clicked the button more than once!

### What could be improved:

To skip a phase if it takes too long. My last project saw my partner and I stay until midnight on a Friday to get an extension feature to work.
This resulted in a dramatic burnout and high levels of fatigue even 10 days later. Not a mistake I want to repeat.