Practical Agile
A long time ago we had in our heads the idea of creating webinars on Agile.
My colleague, Sergey Andrzheevsky, is an experienced and well-known scrum master who participates in various conferences and round tables where he shares his experience in Agile projects - he tells a lot of “tasty” and interesting things to his listeners. It was he who asked me to publish this article on Habré (he does not have his account here yet), because We were able to launch our webinar series (the first one took place on May 27 - Using Offshore Agile in Exigen Services , and on June 21 was the second part - Important points when switching to Agile, July 19 will be the third - Introduction to Extreme Programming (eXP) practices .
Today, flexible methodologies are best adapted to the ever-accelerating development of technology, the emergence of new development tools and the ever-changing customer requirements. Flexibility is now of particular importance due to the general trends in the development of information systems - global mass Internet services, Web 2.0 with its concept of “permanent beta version”, reorientation from software products to information services (which are by definition more flexible and dynamic), the popularity of SOA architectures etc.
')
In the modern world, it is almost impossible to imagine a software development project that is being carried out according to traditional “rigid” methodologies, planned for 2-3 years ahead, since no one can predict how the outside world will change (and, accordingly, project requirements, technologies used and .d.) during this time. There is also another problem - a modern customer of an IT project rarely accurately represents what he needs. But if money was found for a project, then usually everything should be ready “yesterday”, and, as a rule, there is no time, effort or experience to prepare detailed specifications. In this typical situation, the use of Agile allows you to quickly start a project, thinking out the details already in the course of its implementation.
In addition, Agile can be used in a variety of projects - ranging from tiny student-based high-tech start-ups to serious industrial projects with a workload of tens of person-years. It is difficult to find another approach or methodology that would have such a breadth of use.
It is important to note that the time of individual developers has passed. Even if some ingenious lone programmer creates and launches a wonderful program on the market, nothing will prevent competitors from organizing a team that quickly implements similar functionality, and then, using the number of developers, can develop a product faster than the original creator can do. Effective team work on an IT project becomes vital, and it’s about the work of the team, as a single efficient body, and not about the sum of the efforts of self-employed participants. Flexible methodologies allow to organize team work correctly.
Summarizing, we can say that Agile is:
PS Modern IT specialist is difficult to surprise with a high salary, people want the work to be really interesting. In Agile, a programmer who adds a new functionality immediately sees it working in the application and at the customer, which significantly improves motivation, since the result of labor is visual and used. Flexible methodologies because of their focus on teamwork, informal communication, a minimum of bureaucracy, and constant changes make the process of work truly exciting.
Thus, we can add the 4th item to our results: Agile is a personal motivation for the participants.
My colleague, Sergey Andrzheevsky, is an experienced and well-known scrum master who participates in various conferences and round tables where he shares his experience in Agile projects - he tells a lot of “tasty” and interesting things to his listeners. It was he who asked me to publish this article on Habré (he does not have his account here yet), because We were able to launch our webinar series (the first one took place on May 27 - Using Offshore Agile in Exigen Services , and on June 21 was the second part - Important points when switching to Agile, July 19 will be the third - Introduction to Extreme Programming (eXP) practices .
The use of Agile methodologies (SCRUM, XP, etc.) is becoming increasingly popular in the IT industry. Why is this happening? And how does it work?
Today, flexible methodologies are best adapted to the ever-accelerating development of technology, the emergence of new development tools and the ever-changing customer requirements. Flexibility is now of particular importance due to the general trends in the development of information systems - global mass Internet services, Web 2.0 with its concept of “permanent beta version”, reorientation from software products to information services (which are by definition more flexible and dynamic), the popularity of SOA architectures etc.
')
In the modern world, it is almost impossible to imagine a software development project that is being carried out according to traditional “rigid” methodologies, planned for 2-3 years ahead, since no one can predict how the outside world will change (and, accordingly, project requirements, technologies used and .d.) during this time. There is also another problem - a modern customer of an IT project rarely accurately represents what he needs. But if money was found for a project, then usually everything should be ready “yesterday”, and, as a rule, there is no time, effort or experience to prepare detailed specifications. In this typical situation, the use of Agile allows you to quickly start a project, thinking out the details already in the course of its implementation.
In addition, Agile can be used in a variety of projects - ranging from tiny student-based high-tech start-ups to serious industrial projects with a workload of tens of person-years. It is difficult to find another approach or methodology that would have such a breadth of use.
It is important to note that the time of individual developers has passed. Even if some ingenious lone programmer creates and launches a wonderful program on the market, nothing will prevent competitors from organizing a team that quickly implements similar functionality, and then, using the number of developers, can develop a product faster than the original creator can do. Effective team work on an IT project becomes vital, and it’s about the work of the team, as a single efficient body, and not about the sum of the efforts of self-employed participants. Flexible methodologies allow to organize team work correctly.
Summarizing, we can say that Agile is:
- flexibility, adaptability, risk reduction;
- scalability, breadth of use;
- focus on effective teamwork;
PS Modern IT specialist is difficult to surprise with a high salary, people want the work to be really interesting. In Agile, a programmer who adds a new functionality immediately sees it working in the application and at the customer, which significantly improves motivation, since the result of labor is visual and used. Flexible methodologies because of their focus on teamwork, informal communication, a minimum of bureaucracy, and constant changes make the process of work truly exciting.
Thus, we can add the 4th item to our results: Agile is a personal motivation for the participants.
Source: https://habr.com/ru/post/95423/
All Articles