How do you view the situation when there are no analysts in the team?

If there are no analysts in the team, developers and other project participants have to take on some of their functions to ensure understanding of requirements and goals.

In such a situation, it is important:

• To actively interact with the customer or end users to clarify requirements.
• To conduct your own analysis of requirements, formulate user stories and acceptance criteria.
• To use prototyping and demonstrations of intermediate results to obtain feedback.
• To document all agreements and changes to avoid misunderstandings.

Thus, the absence of analysts requires more communication and proactivity from the team, but with the right approach, the project can be successfully implemented.