Agile is the ability to create and respond to change. Agile Software Development is a time boxed, iterative approach to software delivery that builds software incrementally from the start of the project, instead of trying to deliver it all at once near the end. Agile Project Management is a structured and iterative approach to project management and/or product development.

Agile Manifesto

… in 2001 at Utah’s Snowbird ski resort, 17 software developers got together to discuss lightweight software development methods and produced the groundbreaking Agile Manifesto…

We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value:

That is, while there is value in the items on the right, we value the items on the left more.

12 Principles Behind the Agile Manifesto

  1. Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
  2. Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.
  3. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.
  4. Business people and developers must work together daily throughout the project.
  5. Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.
  6. The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.
  7. Working software is the primary measure of progress.
  8. Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.
  9. Continuous attention to technical excellence and good design enhances agility.
  10. Simplicity–the art of maximizing the amount of work not done–is essential.
  11. The best architectures, requirements, and designs emerge from self-organizing teams.
  12. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.

Agile Alliance is a global nonprofit organization dedicated to promoting the concepts of Agile software development as outlined in the Agile Manifesto

The Disciplined Agile toolkit provides straightforward guidance to help organizations choose their way of working in a context-sensitive manner, providing a solid foundation for business agility.

SAFe for Lean Enterprises is a knowledge base of proven, integrated principles, practices, and competencies for Lean, Agile, and DevOps.

What is Agile ALM?

The basic idea behind agile development is the attempt to develop better software by reducing communication borders, and at the same time introducing shorter iterations of development and review. This enables development teams so react faster to changing conditions, may it be changes in the market or changes in the customer's mind about what the final product should be like.

  • Agile Requirements Management
  • Agile Project Management
  • Agile Development
  • Agile Test Management

What is Hyper Agile?

Hyperagility seeks to drive an agile culture further, beyond the walls of any one product team or project, embedding it into the organisational DNA. This is hyperagility.

Agile Glossary Description
Backlog RefinementBacklog refinement is when the product owner and some, or all, of the team examine backlog items to ensure they're appropriate, prioritized, and ready for delivery.
Daily Stand-upThe daily stand-up is a brief check-in that allows the development team to share the current state of affairs and identify any roadblocks.
Definition of doneThe definition of done is an agreed-upon set of tasks needed to finish an iteration's product increment.
IterationDevelopment timebox. Most teams conduct 1-to-4-week iterations.
PlanningIteration begins with planning. Planning defines what can be accomplished in an iteration and how.
Product BacklogA product backlog is a list of the new features, changes to existing features, bug fixes, infrastructure changes, or other activities that a team may deliver to achieve a specific outcome. The product backlog is the single authoritative source for things that a team works on.
Product incrementAfter a development period or timebox, a software product increment is produced.
RetrospectiveEnd-iteration retrospectives are held. The team reflects on the iteration and identifies improvements during the retrospective.
ReviewThe review shows customers and stakeholders the team's iteration work and compares it to the initial commitment.
  • agile/agile.txt
  • Last modified: 2022/08/17 14:43
  • by Henrik Yllemo