In a perfect world, software development process begins with an analysis of problems and development requirements for future products. But what if this step was skipped? If the developers start their work immediately, having received oral explanations from the customer or manager as a separate non-formalized problems? What challenges does the team face in the future? How can the analyst understand and bring order to the chaos and uncertainty of the full process?
In my report, I want to talk about some challenges facing the team working without product requirements. What the analyst can do in such circumstances, how to organize the work with the requirements step-by-step and to provide a stable, predictable and streamlined process.