The dictionary meaning of Agile is quick moving. Now how does that apply to software? The Agile development methodology considers software as the most important entity and accepts user requirement changes. Agile advocates that we should accept changes and deliver them in small releases. Agile accepts change as a norm and encourages constant feedback from the end user.
Figure: Agile
The figure below shows how Agile differs in principle from traditional methodologies.
Figure: Change of Agile thinking
- It’s not necessary to have hi-fi tools and processes but a good team interaction can solve a lot of problems.
- A working software is more important than documentation.
- The management should not just pay attention to customer contracts rather interact with customers and analyze the requirements.
- In traditional methodologies, we pledge to stick to our plans but Agile says “If the customer wants to change, analyze and change your plans accordingly”.
Below are the principles of the Agile methodology:
- Welcome changes and adapt to changing requirements.
- A working software is the main measure of progress.
- Customer satisfaction is the most important thing and can be attained by rapid, continuous delivery of useful software.
- Day to day meetings between business people and the development team is a must.
- Business and developers must work together. Face to face communication is the most important thing.
- Deliver and update software regularly. In Agile, we do not deliver software in one go, but rather deliver frequently and deliver the important features first.
- Build projects around teams of motivated and trustful people.
- Design and execution should be kept simple.
- Strive for technical excellence in design and execution.
- Allow teams to organize themselves.
Excellent post but I was wondering if you could write a little more on this topic? I’d be very thankful if you could elaborate a little bit more. Kudos!