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...

As I was about to work on one of the items for the sprint I realized it'd be a LOT easier if I cleaned up my code first. I've been meaning to do this and it really should have gone in as a sprint backlog item, so I added an unplanned item to the sprint. Basically I ended up with a ton of unused database-related methods, since I rewrote large portions of the data access layer. I didn't remove things as I went along just in case something somewhere needed them; I didn't want to break anything as I went along. But at this point I need to get rid of those methods and clean things up! Being an Eclipse user, I wondered if there were a plug-in to help with this task. So I discovered UCDetector . This thing is great for cleaning up small projects like mine. I just had to tell it to detect, and presto! I had a list of methods that weren't being used. It also had some recommendations on classes/methods/etc. that could be made less public. Very cool. Anyway I thought this ...