The architect is responsible for breaking the system into its component parts (subsystems, modules), defining protocols and adopting all difficult-to-modify solutions (for example, choosing a technology).An architect is needed on a project if it is a system or solution that combines several teams. Otherwise, the project risks "getting stuck" in the pit of processing and planks, postponing the release dates.