A lot has already been written on the difference between “Doing Agile” and “Being Agile”.“Doing Agile” boils down to using the agile terminology, because everybody should be agile, but in fact doing business as usual. “Being Agile” is however implementing a new culture, backed-up by a vision and a consistent set of practices. The latter …
The Agile Method is a particular approach to project management that is utilised in software development. This method assists teams in responding to the unpredictability of constructing software. It uses incremental, iterative work sequences that are commonly known as sprints.
Agile methodology is based upon 12 basic principles
- 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 maximising the amount
of work not done–is essential.
- The best architectures, requirements, and designs
emerge from self-organising teams.
- At regular intervals, the team reflects on how
to become more effective, then tunes and adjusts
its behaviour accordingly.