Agile = 4 + 12
Many are trying to understand - what is agile? Adjay we or not? Are there any agile teams in Russia? Where can I find agile team in Moscow? To answer such questions you need to understand - what is agile? Such questions lead me into some confusion. First, because each means by this completely different. Secondly, true agile commands I did not see :)
But all in order. To determine Agile, you can use two approaches:
')
Agile (short definition) is a development process in which a team is guided by 4 values ​​and 12 principles. A very simple definition, if your team held a meeting and 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 incremental, but if you stick to formula 4 + 12 - you are a true agglist. Some say that agile is flexibility and the principles and manifesto are not necessary. They are right. But please call it differently. For example, "flexible approach", or "agile-2" or something else. But Agile has no other interpretations, it is 4 + 12. It's not even 4 + 11, not 3 + 12. Such combinations can also be - but their name is different. Unfortunately I do not know which one. So a brief and very capacious and complex definition -
Agile (complex definition) is a development process about which they write 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 are narrowed. And all this diversity is covered by the capacious word Agile. And attached shade of "flexibility." Which is not really laid down in the classic sense. But this gives rise to a large variety of interpretations, conjectures and trends. Only the “extreme programming” direction, as sometimes interpreted, is written without documentation and 24 hours a day. extreme! 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.
12 principles detail abstract beliefs and clarify how to interpret the values ​​laid down in the manifesto. 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 Adjail is? Are you a team? What does Adjail mean to you and your team?
But all in order. To determine Agile, you can use two approaches:
')
Agile (short definition) is a development process in which a team is guided by 4 values ​​and 12 principles. A very simple definition, if your team held a meeting and 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 incremental, but if you stick to formula 4 + 12 - you are a true agglist. Some say that agile is flexibility and the principles and manifesto are not necessary. They are right. But please call it differently. For example, "flexible approach", or "agile-2" or something else. But Agile has no other interpretations, it is 4 + 12. It's not even 4 + 11, not 3 + 12. Such combinations can also be - but their name is different. Unfortunately I do not know which one. So a brief and very capacious and complex definition -
Agile is 4+ 12
Agile (complex definition) is a development process about which they write 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 are narrowed. And all this diversity is covered by the capacious word Agile. And attached shade of "flexibility." Which is not really laid down in the classic sense. But this gives rise to a large variety of interpretations, conjectures and trends. Only the “extreme programming” direction, as sometimes interpreted, is written without documentation and 24 hours a day. extreme! 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.
12 principles detail abstract beliefs and clarify how to interpret the values ​​laid down in the manifesto. 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 Adjail is? Are you a team? What does Adjail mean to you and your team?
Source: https://habr.com/ru/post/75100/
All Articles