Shambling Towards Perfection

So clearly I fell off the sprint-wagon. Things got a bit away from me at the start of the semester, and so I just haven't been doing the formal sprint stuff. I've been working on bugs and configuring Tomcat, plus getting the first draft of my paper written. But I need to get organized again in order to finish what needs finishing before I present my project May 3 (only 3 weeks away, ack!), so I'm going to restart with sprinting and all that for the little time I have left.  So for sprint 8, I did finish all but one task, Fix weird errors when project only has one user (instructor is the only student). For two other tasks, I'm not sure how long it took to finish them because I didn't write it down (the beginning of my slide into not being scrummy): Update the application to handle errors nicely and Change code to use connection pooling. I finished the rest normally: Add columns/tables to database to support task dependency/subtask relationships (1), Add co...

The goal for sprint 8 is to make any necessary database schema changes and to add as many features (not just making the UI prettier) as possible. The sprint backlog items are: Priority Description Points 600 Add columns/tables to database to support task dependency/subtask relationships. 2 590 Add columns to user table to support lockout after failed login attempts. 2 580 Add checks for authorized access to all CRUD operations. 3 570 Wrap create statements and the fetching of the ID in one database transaction to prevent incorrect results (if necessary). 2 560 Update the application to handle errors nicely. 5 550 Check all error-related redirects to make sure they work properly. 1 540 Add try/catch blocks for parseInt calls and handle errors appropriately. 1 530 Fix weird errors when project only has one user (instructor is the only student). 2 520 Change code to use connection pooling. 3 This is a total of 21 hours, which I think I can do by the middle of next week. If...