These are the guiding practices that support teams in implementing and executing with agility.
- 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.
- Business people 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 behavior accordingly.
This information is from the Agile Alliance web site. If you are looking for helpful free Agile resources spend some time on this site. Additionally, should you chose to join the Agile Alliance, you can find outstanding training videos for your team.
Process Geek Note:
The document, formally called the “Manifesto for Agile Software Development,” was produced by 17 developers during an outing on Feb. 11-13, 2001, at The Lodge at Snowbird ski resort in Utah.
The developers, who called themselves the Agile Alliance, were seeking an overhaul of the software development processes that they saw as cumbersome, unresponsive and too focused on documentation requirements.
According to agilemanisfesto.org, the online home of the proclamation, the developers’ stated goal was not anti-methodology, but rather “to restore credibility to the word methodology.”
- Business people 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.
Leave a Reply