The subject of this post is probably not a suitable indicator of what's in this entry. I was intending to talk about Agile testing and then shifted gears to begin with trying to shed some light on the basic question - what is Agile ? In subsequent posts, i hope to focus more on testing in an agile context.
What is Agile (in the context of Software development) ? Is it a buzzword ? Is it what the dictionary defines "agile" to be - adaptable, able to move quickly, respond quickly ? Well if the dictionary definition were true, then i'd say almost everyone involved with producing software would want to be agile.
Agile refers to a collection of methodologies that enable agility in producing software. Common agile methods include Scrum, XP, etc. The Agile manifesto describes the values of the agile community. These are listed below.
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
While agile methods do not intend to do away with the items on the right, they lay a greater emphasis on the items on the left and that can present a significant difference in how software is produced vis-a-vis the non-agile / traditional models of development (and testing).
What is Agile (in the context of Software development) ? Is it a buzzword ? Is it what the dictionary defines "agile" to be - adaptable, able to move quickly, respond quickly ? Well if the dictionary definition were true, then i'd say almost everyone involved with producing software would want to be agile.
Agile refers to a collection of methodologies that enable agility in producing software. Common agile methods include Scrum, XP, etc. The Agile manifesto describes the values of the agile community. These are listed below.
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
While agile methods do not intend to do away with the items on the right, they lay a greater emphasis on the items on the left and that can present a significant difference in how software is produced vis-a-vis the non-agile / traditional models of development (and testing).
