Kako postupite kada zahtjevi nisu jasni?

Question

Accepted Answer

Dvosmislenost je norma u stvarnom radu. Žele vidjeti da **aktivno smanjujete neizvjesnost** umjesto da se zamrznete ili tiho nagađate i gradite krivo.

## Kako se pristupiti

```text
1. Ask the questions that change what you'd build
2. Find the goal behind the request (the "why")
3. State your assumptions in writing and confirm them
4. Build a thin slice, demo early, adjust fast
```

## Rad primjer

```text
S: A ticket said "add a dashboard" with no detail on metrics or users.
T: Building blind risked weeks of wasted work.
A: I asked who'd use it and what decision it drove, wrote down three assumptions,
   and built a clickable prototype of the top two metrics first.
R: The demo surfaced that they actually needed exports, not charts. We pivoted
   after two days instead of two weeks.
```

## Dobro vs slabo

```text
✓ Clarifies the "why," states assumptions, demos early
✗ Building the full thing on a guess
✗ Refusing to start until everything is spec'd
```

## Zašto je to važno

Jasne specifikacije su rijetke; inženjeri koji uspijevaju su oni koji mogu kretati se kroz maglu.

Nalaženje osnovnog cilja vas sprječava da gradite upravo ono što je traživano ali ne ono što je bilo potrebno.

Prikaz tankog sloja ranog превращаjourpretvaranja skupih nagađanja u jeftine, brze korekcije.