Unawezaje kutatua ombi la kubadilisha kila hewa katikati ya Sprint?

Question

Accepted Answer

Kiwango chaguo katika Scrum ni **kulinda Lengo la Sprint**: hakuna mabadiliko yanayoongezwa ambayo yanahatarisha. Lakini Scrum sio mgumu — kile cha upeo cha kazi kinaweza *kuzungumzwa upya na Product Owner*, na mabadiliko ya haraka yanayohitajika inaweza kushughulikiwa, na ushindi uliofanywa wazi.

## Mfumo wa uamuzi

```text
1. Does the new request threaten the Sprint Goal?
     NO  → can it wait for the next Sprint? Usually yes → backlog it.
     YES → talk to the Product Owner about trade-offs.
2. Is it a genuine emergency (prod down, legal, security)?
     YES → the PO may cancel/replace work; something must drop.
3. Make the trade-off visible: pulling X in means Y comes out.
```

## Mfano halisi

Katikati ya Sprint, uuzaji unataka ripoti "ndogo" mpya. Scrum Master anasaidia timu na Product Owner kuona si haraka, kwa hiyo inakwenda juu ya backlog ya Sprint inayofuata badala ya kutatanisha lengo la sasa.

## Mitego ya kawaida

- Kunyonya kazi ya ziada kwa kimya, kuua Lengo la Sprint na kufichwa.
- Kusema "hapana" kabisa bila njia — Product Owner anaweza kuzungumza upya kila wakati.
- Kuruhusu kila muhimu kuingiza kazi moja kwa moja, akisalia Product Owner.

## Kwa nini kuhusu

Kulinda Lengo la Sprint ndicho kinachofanya Scrum kuwa na hakika; sindio inayoingizwa kuhusu hugeeza Sprints kuwa orodha za kazi zenye fujo.

Kushughulika na mabadiliko kupitia Product Owner na ushindi uliofanywa wazi kuweka timu kuwa na mtazamo wakati wa kuwa na kauli kwa dharura za kweli.