Sprint 4 Retrospective
The Work Done
The skeleton code of the backend from the previous week has now been fully fleshed out into a working (possibly buggy) system. Bugs may be discovered when this backend is connected with the frontend of “Four Line Dropper”. Through some (manual) testing, the backend does handle requests made in JSON, and always responds with JSON regarding errors or expected data.
Unfinished Tasks
Again, the tasks that are unfinished actually have a dependency on future tasks. Since these dependent tasks are recurring, it probably is a “code smell” of User Stories and tasks that have not been sufficiently decomposed enough to avoid this problem. I may rework/split up some User Stories before starting on the next Sprint.
Anyways, the current Sprint is basically “done”, but dependencies on future tasks prevent it from being “officially done” with all tasks.
What’s Next
As mentioned earlier, I may have to rework the User Stories and Tasks to follow the “INVEST” acronym better. Then I will attempt to connect the frontend to the backend as the goal of the next Sprint.
Post Retrospective Notes
I’ve decided to keep the User Stories as-is, since the User Stories / Tasks that depend on others should be completed by the end of Sprint 5, except “AI Implementation” (AI can still be tweaked indefinitely, so it may just be marked done at the end of the project). As long as I have time to finish the required tasks, Everything post Sprint 5 should be “extra” as the main expected functionality should be finished (unless some bugs are discovered).