- Listen to our monthly AppSec Stats Flash podcast
- LEARN MORE
Agile is a project management style that applies a cross-functional approach throughout the software development lifecycle (SDLC). Involving multiple methodologies, Agile describes a set of values and principles for software development under which requirements and solutions evolve through the collaborative effort of self-organizing cross-functional teams.
The Manifesto for Agile Software Development describes the central values and principles applied in an Agile approach. It is a popular evolution of more traditional project management styles, such as the waterfall model. It emphasizes cross-functional teams, communication, collaboration, and self-accountability rather than siloed, progressive teams. Agile allows teams to quickly and proactively respond to changes and problems. Two of the most popular Agile approaches adopted are Xp (eXtreme Programming) and Scrum.
The following 12 Principles are based on the Agile Manifesto.
Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
Welcome changing requirements, even late in development. Agile processes harness change for the customer’s competitive advantage.
Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.
Businesspeople and developers must work together daily throughout the project.
Build projects around motivated individuals. Give them the environment and support they need and trust them to get the job done.
The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.
Working software is the primary measure of progress.
Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.
Continuous attention to technical excellence and good design enhances agility.
Simplicity–the art of maximizing the amount of work not done–is essential.
The best architectures, requirements, and designs emerge from self-organizing teams.
At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behaviour accordingly.