Agile = 4 + 12
Many are trying to understand - what is agile? Agile or not? Is there a team aguil in Russia? Where can I find the Agile team in Moscow? To answer such questions, you need to understand - what is agile? Such questions make me somewhat confused. Firstly, because each one by this means completely different. Secondly, I didn’t see the true adjayl of the teams :)
But everything is in order. There are two approaches to defining Agile :
Agile (short definition)- This is a development process in which the team is guided by 4 values and 12 principles. It is a very simple definition if your team has held a meeting and has confirmed that you are guided by 4 + 12 in your decisions and drive these values and principles - you are an agile team. And no matter what practice you use. You can work on waterfall (when all stages are consecutive) or incrementally, but if you adhere to the 4 + 12 formula, you are a true agileist. Some say that agile is flexibility and following the principles and manifest is not necessary. They are right. But then please call it differently. For example, a “flexible approach”, or “Agile-2” or something else. But Agile - has no other interpretations, it's 4 + 12. This is not even 4 + 11, not 3 + 12. Such combinations can also be - but their name is different. Unfortunately, I don’t know which one.
Agile (a complex definition) is a development process that is written about in agile magazines. Adage is a certain subculture in the IT community, which of course is guided by the formula 4+! 2. But unfortunately, many go beyond the scope of this formula, or vice versa, narrow. And all this diversity is covered by the capacious word Agile. And a touch of “flexibility” is given. Which is not really laid down in the classical sense. But this gives rise to a wide variety of interpretations, conjectures and trends. The “extreme programming” direction alone is sometimes interpreted — we write without documentation and 24 hours a day. Extremely! Not that word :)
So, Agile = 4 + 12. 4 values are listed in the manifest and I have already mentioned before:
Agile Manifesto
•Individuals and interactions over processes and tools.
• Working software over comprehensive documentation.
• Customer collaboration over contract negotiation .
• Responding to change over following a plan.
The 12 principles detail abstract beliefs and specify how to interpret the values embodied in the manifest. I will gradually give my interpretation of these principles and I will be glad if you express your point of view.
And at the end of the post I would like to know your opinion about Adail. What do you think Agil is? Are you Agile team? What does Agile mean to you and your team?
But everything is in order. There are two approaches to defining Agile :
Agile (short definition)- This is a development process in which the team is guided by 4 values and 12 principles. It is a very simple definition if your team has held a meeting and has confirmed that you are guided by 4 + 12 in your decisions and drive these values and principles - you are an agile team. And no matter what practice you use. You can work on waterfall (when all stages are consecutive) or incrementally, but if you adhere to the 4 + 12 formula, you are a true agileist. Some say that agile is flexibility and following the principles and manifest is not necessary. They are right. But then please call it differently. For example, a “flexible approach”, or “Agile-2” or something else. But Agile - has no other interpretations, it's 4 + 12. This is not even 4 + 11, not 3 + 12. Such combinations can also be - but their name is different. Unfortunately, I don’t know which one.
Agile is 4+ 12
Agile (a complex definition) is a development process that is written about in agile magazines. Adage is a certain subculture in the IT community, which of course is guided by the formula 4+! 2. But unfortunately, many go beyond the scope of this formula, or vice versa, narrow. And all this diversity is covered by the capacious word Agile. And a touch of “flexibility” is given. Which is not really laid down in the classical sense. But this gives rise to a wide variety of interpretations, conjectures and trends. The “extreme programming” direction alone is sometimes interpreted — we write without documentation and 24 hours a day. Extremely! Not that word :)
So, Agile = 4 + 12. 4 values are listed in the manifest and I have already mentioned before:
Agile Manifesto
•Individuals and interactions over processes and tools.
• Working software over comprehensive documentation.
• Customer collaboration over contract negotiation .
• Responding to change over following a plan.
The 12 principles detail abstract beliefs and specify how to interpret the values embodied in the manifest. I will gradually give my interpretation of these principles and I will be glad if you express your point of view.
And at the end of the post I would like to know your opinion about Adail. What do you think Agil is? Are you Agile team? What does Agile mean to you and your team?