Under the hood and working with .Net, TDD, Software Design, and Agile Stuff
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 D. Miller
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 previously worked as a systems architect building mission critical supply chain software for a Fortune 100 company and learned agile development practices as a .Net consultant at ThoughtWorks, one of the pioneers of agile development. Jeremy is the author of the open source StructureMap (http://structuremap.sourceforge.net) tool for Dependency Injection with .Net and the forthcoming StoryTeller (http://storyteller.tigris.org) tool for supercharged FIT testing in .Net. Jeremy's thoughts on just about everything software related can be found on his weblog "The Shade Tree Developer" at http://codebetter.com/blogs/jeremy.miller, part of the popular CodeBetter site. Jeremy is a Microsoft MVP for C#.
