In 90% of cases, the customer initially has a poor idea of ​​what he wants to get

[mstakh.i.mo.mi]

The Pitfalls of Agile Methodology This methodology does not describe requirements management processes well. Moreover, it does not have such a concept, since flexibility does not imply long-term planning. Because of this, there is no stage of work on a development plan or a product roadmap. The plan is made only for the next iteration, following which the customer accepts the software and sets new requirements. This approach leads to the product changing dramatically, and additional requirements often do not correspond to the structure and architecture of the product that the audience is already using.


and understanding comes to him during the work. Then the development turns into a gambling data vietnam formalized and legalized bureaucracy, in which the product is refined until the money runs out or the customer gets tired of the process. However, the customer knows what awaits him and decides whether to pay for the development or not. While the team only fulfills his requirements, using the Agile methodology as a basis.


However, in real life, chaos, missed deadlines and rush jobs cannot be avoided, which leads to new requirements that negatively affect the result. This is because Agile requires solving problems quickly and using the simplest approaches possible. As a result, when writing code, the requirements of the platform on which the product is created are not taken into account. The latter is overgrown with an endless number of workarounds, defects, and thus a not very stable and unsafe design is obtained.