Why Agile?

  Agile  

Agile has been around for some time and though it’s adoption by organizations has increased; it has its fair share of detractors. To name a few of the disadvantages: it is difficult to predict the project timeline at the beginning of the software development lifecycle, less focus on design and documentation, demanding time lines because of short development cycles and potential for scope creep.

Some of criticism against agile is valid and some is not. And even the staunchest agile supporters would agree that organizations should figure out what is the right “flavor” of agile that works best for them. Once this is figured out (not without trial and tribulations) there is potentially a bigger benefit to agile; that can bring about a more intrinsic change in the organization. It can have a much larger impact on an organization than just on the team working on an agile project. Here are few things that an agile project can foster in an organization:

Innovation: Most projects working on a waterfall methodology rely on a complete set of requirements before the project starts. Though the requirements can and do change and they do get implemented. At other times, may be because of “too good” a change control process or for fear of too much scrutiny and justification or simply too much work, some good ideas never come forward. Some of these ideas…

Please log in or sign up below to read the rest of the article.