Use change to your advantage throughout the modern app lifecycle instead of resisting it by adopting agile practices with Visual Studio 2012.
When it comes to creating custom applications, too many of us live in denial. We want to believe that it’s possible to predict accurately how long a group of developers will take to build software that meets our requirements. We also want to believe that we can know what those requirements are up front, before we’ve seen any part of the application, and that the requirements won’t change during development.
Sadly, none of these things are true for most projects. We can’t predict how long development will take, largely because we can’t get the requirements right up front and we can’t stop them from changing. Because we deny these realities, many organizations still use software development processes that don’t work well.
Fortunately, this is changing. Agile development processes get more popular every day, primarily because they’re rooted in reality: They’re designed to accommodate change. Doing software development in this way can be scary at first, especially for the business leaders who are footing the bill. This needn’t be the case, however. The truth is that agile processes are usually better both for development teams and for the business people who pay them. To understand why this is true, we need to start by understanding what an agile process really is.