Agile – what is it ?

Introduction
During skimming over job offers you can notice one of requirements: ‘Agile’. It is interesting issue and in this post I’m gonna give you a little explanation what is going on…

Firstly, I would like to come back to 2001. 17 practitioners who work on a daily basis in small, self-organizing teams, in cooperation with the client, an atmosphere of mutual respect, focus on early and regular provision of working software to the client and care for technical excellence. They operate based on the so-called lightweight methods. They  were meeting to talk about the specifics of the light methods they use, exchange experiences and opinions, go skiing and have a good time. Within 3 days they did much more than they expected. First of all, they found a common denominator for all these methods and decided that the common name “light methods” is not appropriate. They recognized that the term “agile” better reflects their specificity. This is the beginning of the term ‘Agile methods’. They also form the Agile Programming Manifesto, commonly referred to as the Manifesto for Agile Software Development, which is to emphasize the four values ​​on which all agile, agile methods of work are based.

Working  in Agile
How it looks like in reality ? I tried to show quintessence below. Thus:
#1 Client satisfaction
Recipient is happy because he get earlier, working, a good quality software.
—     —     —    —    —   —     —     —    —    —   —     —     —    —    —   —     —     —    —    —   —
#2 Motivating work environment
People want to work, develop software cause they have needed things. They have support and feel confident.
—     —     —    —    —   —     —     —    —    —   —     —     —    —    —   —     —     —    —    —   —
#3 Direct communication
Conversations in the style ‘face to face’. Business persons and programmers are still in the touch.  They have a chance to dispel all doubts.
—     —     —    —    —   —     —     —    —    —   —     —     —    —    —   —     —     —    —    —   —
#4 Working software = progress
The key is simplicity, or the art of minimizing the amount of work necessary.
—     —     —    —    —   —     —     —    —    —   —     —     —    —    —   —     —     —    —    —   —
#5 Requirements are not constants
Changes could be even in final stage of produce software.
—     —     —    —    —   —     —     —    —    —   —     —     —    —    —   —     —     —    —    —   —
#6 Efficiency is constantly enhancing
A team regularly analyze what they should to change to be more productive.
—     —     —    —    —   —     —     —    —    —   —     —     —    —    —   —     —     —    —    —   —