"To Agile or Not to Agile?". That is the question. Have you ever wondered or better yet, been confused by exactly what it means when your project manager mentions the fact that his/her projects are "Agile"? Have you ever questioned whether Agile software development truly has quantifiable benefits? Is the Agile trend ultimately leading to the downfall of "Waterfall". Well, this post will provide you with enough information about the basics of the Agile methodology with a focus on SCRUM, to help you continue your search.
History of Agile:
The Agile Manifesto was a document written in 2001 by a group seventeen people at a ski resort in Utah. At this meeting were software development professionals well versed in development methodologies such as SCRUM, Xtreme Programming, Feature Driven Development, and others. The main goal of this meeting was to come up with an alternative approach to documentation driven, long and heavy software development methodologies. This group named themselves the Agile Alliance and essentially came up with what's referred to as the "Agile Manifesto". The core of the manifesto states the value of the items on the left over those on the right.