Under the hood and working with .Net, TDD, Software Design, and Agile Stuff
I've written a couple posts on teams and the desire for multi-skilled people and eliminating specialists. I hope I made my case, but it doesn't matter because Tate Stuntz did it for me in fantastic style in The demise of the Gantt Chart in Agile Software Projects. Please focus on why he says Gantt charts can be rendered unnecessary rather than flying off the handle by saying that Agile projects don't plan. You can, and have to, change the way you might be working in order to achieve any gains from an Agile process. The way you write code. How you divide responsibilities in the team. When you do certain activities. How you collaborate. It all needs to be put up for discussion and analyzed to make a successful shift to working in an Agile manner.
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#.
