In general, in agile methodologies it is not common

[sujonkumar6300]

To find specific activities to develop the architecture. This can be associated with various factors such as:

The focus on activities that contribute to the development and delivery of a functional product, rather than activities focused on system design and documentation. The time required for architecture generation and documentation is often viewed as a secondary activity that is not part of the final product.
Most agile methodologies work with small teams and medium-sized systems. The importance Russia Mobile Database of defining the architecture may not be as obvious in such scenarios, where practices such as simplicity, which suggests focusing on the currently identified system elements and postponing adding complexity until it is needed (through code restructuring or “refactoring”), may work.
Despite this, some methods are already incorporating adaptations to their practices to include activities related to the definition of software architecture. For example, some teams using Scrum have included an initial iteration called “Sprint Zero.” In this iteration, a high-level architecture is generated that establishes how the system features will be implemented. Another example is the recommendation to include and manage non-functional requirements as user stories.

More information regarding agile methodologies and software architecture can be found in [5].