Too many responsibilities
Sam and I have been working on a single story for about two weeks now (i.e. way to long). One of the things that we have done is refactored a class that had more responsibilities than any class has any right to have. Where there used to be one class, there are now about fourteen classes, and there are still at least five more begging to be created, but we will probably leave that for another day since we are already way over budget. Unfortunately, I have to admit that I was the original author of this monstrosity of a class.
One result of the refactoring that we have done is that it has shown me how much I have learned in the past year about not only what the single responsibility princple really means, but also, how to break these multi-responsibility classes into better factored code. SRP is not one object that drives an entire screen, but one that truly has just a single, small responsibility.