Apa iku user story lan apa iku acceptance criteria?

Question

Accepted Answer

A **user story** adalah deskripsi singkat lan gampang dimangerteni saka fitur sing diceritakake saka perspektif pengguna. Kajikeneng *sapa* sing pengin kejilmaan, *apa* sing dikarepake, lan *mengapa*. **Acceptance criteria** ndefenisi apa artine "rampung" kanggo cerita kasebut — kondisi apa sing kudu dipenuhi supaya bisa katampa.

## Standar format

```text
As a [type of user]
I want [some goal]
so that [some benefit].

Example:
  As a returning customer
  I want to save my shipping address
  so that I don't re-enter it every order.
```

Bagian "so that" paling penting — nyatakake nilai, sing mbantu tim nemokake solusi sing luwih apik tinimbang sing dimangerteni kanthi literal.

## Acceptance criteria

```text
Given a logged-in customer with a saved address
When they reach checkout
Then the saved address is pre-filled
And they can edit it before confirming

✓ Testable and unambiguous
✓ Defines done — no "I thought you meant..."
```

## Cerita sing apik ngetutik INVEST

Independent, Negotiable, Valuable, Estimable, Small, Testable. Cerita sing gedhe banget nganti ora bisa diestimasi utawa ditunggani ing sprint kudu dipecah.

## Mengapa iki penthing

Cerita njaga tim fokus ing *nilai pengguna* tinimbang dhaftar tugas teknis, lan invite parupaduan tinimbang ngruwuhi solusi.

Acceptance criteria sing jelas nyegah gesekan delivery paling umum: ngunduh sesuatu sing teknis bisa tapi ora apa sing bener-bener dikarepake.