The first time I listened to Scott Bellware’s interview on the Alt.Net podcast #17 “The State of Alt.Net” I was a little off put by Scotts dissatisfaction with the community… The Meeting I walked into this so called “concerns” meeting with nothing but uncertainty. How would it all play out? Would I be challenged about the implementation? Would I be required to do "forms over data”? How would the vendor be considered in all of this? How would these decisions effect the project scope? The one outcome I did not consider, nor did anyone who commented on the last post, is probably...

Note: I like to use lots of analogies. I understand that my situation is nothing like that of those who die for their respective causes. Also; I use the term “OOP principles” to generalize all the methodologies/tools/practices used in today’s application development. Introduction I work in a what is, too me maybe, a unique development environment. Our current organization structure does not have a technical architect. The developer position ladder ends at lead developer. Without a TA we are attempting to run the development process through a committee. With close to 30 developers spread...

First, as a point of reference, the agile manifesto is simply a set of four principles. Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan Scrum, LEAN, BDSM and XP are methodologies that are designed to help organizations become “Agile”. Each methodology consists of organizational practices and tools. It’s rather hard to put a concrete number on the Scrum ROI without executing two simultaneous projects with one using an agile methodology and...