Agile Background
Agile Background
History: The Agile Manifesto. On February 11-13, 2001, at The Lodge at Snowbird ski resort in the
Wasatch mountains of Utah, seventeen people met to talk, ski, relax, and try to find common ground -
and of course, to eat. What emerged was the Agile 'Software Development' Manifesto.
Agile management, or agile process management, or simply agile refers to an iterative, incremental
method of managing the design and build activities of engineering, information technology and other
business areas that aim to provide new product or service development in a highly flexible and
interactive manner
Agile Software Development is an umbrella term for a set of methods and practices based on the
values and principles expressed in the Agile Manifesto. Solutions evolve through collaboration
between self-organizing, cross-functional teams utilizing the appropriate practices for their context.
Manifesto for Agile Software Development
We are uncovering better ways of developing
software by doing it and helping others do it.
Through this work we have come to value:
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.
6) Give them the environment and support they need, and trust them to get the job done.
7) The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.
10) The sponsors, developers, and users should be able to maintain a constant pace indefinitely.
11) Continuous attention to technical excellence and good design enhances agility.
12) 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.
Good Practice
1. Active user involvement is imperative
2. The team must be empowered to make decisions
3. Requirements evolve but the timescale is fixed
4. Capture requirements at a high level; lightweight & visual
5. Develop small, incremental releases and iterate
6. Focus on frequent delivery of products
7. Complete each feature before moving on to the next
8. Apply the 80/20 rule
9. Testing is integrated throughout the project lifecycle – test early and
often
10. A collaborative & cooperative approach between all stakeholders is
essential
Introduce ourselves to
Agile
the Agile Manifesto
Extreme Programming
(XP) is a software development
Scrumban methodology which is intended to
is an Agile management improve software quality and
methodology describing hybrids of responsiveness to changing
Scrum and Kanban and was customer requirements. As a type
originally designed as a way to of agile software development, it
transition from Scrum to Kanban. advocates frequent "releases" in
short development cycles, which
is intended to improve
productivity and introduce
checkpoints at which new
customer requirements can be
adopted.