Agile S/w Development Methodology

Agile process is evolved in 90s. Agile, in literal, means the ability to move freely- ability to Adapt. Adapting to the changing requirements and adapting to the changing circumstances. AGILE allow for changing requirements throughout the development cycle and stress collaboration b/w s/w developers and customers and early product delivery.
The “Agile Manifesto” establishes a common framework for these processes: Value individuals and interactions over processes and tools, working software over comprehensive documentation, customer collaboration over contract negotiation, and
responding to change over following a plan. The processes most commonly considered agile include Extreme Programming (XP), Lean Development, Crystal and Scrum.

Scrum:
Scrum is an agile software development method for project management. The word scrum is derived from the Rugby game. Takeuchi and Nonaka noted that projects using small, cross-functional teams historically produce the best results, and likened these high-performing teams to the scrum formation in Rugby. Although Scrum was intended to be for management of software development projects, it can be used in running maintenance teams, or as a program management approach

Scrum terminology
Scrum Master: The person or persons in charge of the tracking and the daily updates for the scrum (equivalent to a project manager).
Scrum Team: A cross-functional team (developers, B.A.s, DBAs, and testers) responsible for developing the product.
Product Owner: The person responsible for maintaining the Product Backlog via continuous interaction with Clients and Stakeholders.
Story: A customer focused description of valued functionality.
Product Backlog: The stories to be completed.
Sprint: A time period (usually 2 to 4 weeks) in which development occurs on a set of stories that the team has committed to.
Burn Down Chart: Daily progress for a sprint over the sprint's length.