Sprint 3 Retrospective
	Things to know at first:
The first two retrospectives are available in the product backlog values in separate columns. This retrospective is the first one to be split-off into its own document.
	About Sprint 3 (with notes about previous Sprints)
The first two Sprints had one task that was commented as “almost done”, but because of the definition of done, they were left as unfinished. The first was the “Game Logic Turn Implementation” which may change due to adding the “Networked Multiplayer” feature. So it was a dependency on a future task that kept this User Story from being marked completed. The second in the second Sprint was “AI Implementation”, because it could use more tweaking as improvement (which might never be considered done because of how much tweaking is possible). Long story short, Utility-based Game AI is simple and works well for this game where up to 7 possible moves can be made per turn, but can be tweaked in how it determines the utility for each move.

As for Sprint 3, issues in my personal life prevented me from finishing the tasks, and it turns out setting up the backend was more difficult than setting up the game AI. However, most of the “backbone” of Networked Multiplayer stuff was done (such as defining the database schema at the backend using sqlite, and the protocol for requests to the backend via http requests). So what’s left is mostly busywork, and not much extra planning should be needed.
	The Next Sprint
The goal for this week (Sprint 4 starting March 28th), is to finish the unfinished tasks from Sprint 3. As long as I allocate time for this, I predict most of the tasks should be finished. On a good week, perhaps all of the planned items for the Sprint will be finished.