Prikupljanje zahtjeva je proces pronalaženja onoga što zapravo treba biti izgrađeno — i zašto — prije nego što se krene s gradnjom. Najveća greška koju prave mlađi developeri je doslovno primanje zahtjeva bez razumijevanja osnovnog problema.
Kako pristupiti tome
1. ASK WHY → understand the problem behind the request, not just the request
2. TALK to the real users / stakeholders, not just the requester
3. CLARIFY scope → what's in, what's out, what "done" looks like
4. SURFACE assumptions and constraints (deadlines, budget, tech limits)
5. WRITE IT DOWN → confirm your understanding back to them
