Retrospective

What went well:
+ Really enjoyed sprint planning session, having milestones and a plan - direction is key
+ QA was very good (thanks @katbow), verbose style helped learn new things or even just different ways of doing things
+ Asking questions on why things were done rather than specifically saying ‘this is wrong’ was great as sometimes things were done in an unusual way for a reason
+ Really enjoyed using pre-commit module for 100% test coverage. Doing tests as we go along rather than having to spend 2 days at the end doing them was much better
+ Also very enjoyable to use a module you wrote yourself
+ Generally good team vibes
+ Having acceptance criteria was very helpful in understanding what is the minimum we can do to fulfil that criteria and create the first iteration
+ Generally we know we prefer more pairing so will look to continue to have a good balance of pairing (especially on more complex features) and individual work for future sprints

Things to be improved
+ Would have been good to do the sprint planning before _anything_ started (there were two days of research and planning before @iteles was in the country and available to do the planning)
+ Having the [bullet points in the readme](https://github.com/dwyl/library/tree/8fae148b0874057a633ac2836f5c839a8a920441#what) turned into user stories with acceptance criteria earlier would have been helpful, this level of clarity made a difference and made things more tangeable
+ More consistency of timing of standup (@iteles was travelling for two of the days so this had to be move) - allows you to architect your day (and if something you've planned for doesn't happen, it leaves you feeling unproductive)
+ More time for a build overall, felt a bit rushed - could have been partially resolved by more accurate time estimates and a buffer for bugs, which would have led to a smaller sprint scope
+ Clarity on whether times estimates are paired or individual and what happens if we do something individually that has a paired estimate