From the Java side of the world, a dead on discussion on Agile Anti-Patterns. Been there, done that, gotten the tee shirt. I think I’d add:
- Overly long stand up meetings and/or iteration planning meetings
- Contention in iteration meetings
- Not doing retrospectives or not acting on retrospectives. It’s easy to skip when you’re under duress, but you shouldn’t.
- Not doing estimation together
- Not getting concrete acceptance criteria for a user story
- Not pushing completed stories to testing until late in the iteration
About Jeremy Miller
Jeremy is the Chief Software Architect at Dovetail Software, the coolest ISV in Austin. Jeremy began his IT career writing "Shadow IT" applications to automate his engineering documentation, then wandered into software development because it looked like more fun. Jeremy is the author of the open source StructureMap tool for Dependency Injection with .Net, StoryTeller for supercharged acceptance testing in .Net, and one of the principal developers behind FubuMVC. Jeremy's thoughts on all things software can be found at The Shade Tree Developer at http://codebetter.com/jeremymiller.
This entry was posted in
Uncategorized. Bookmark the
permalink. Follow any comments here with the
RSS feed for this post.