Scéal dom faoi thuras a rinne tú tionscadal i dtrioblóid a fhurtáil.

Question

Accepted Answer

Déanann sé seo tástáil ar **fhilleadh ar an stiúradh**: fáth theip tionscadail a dhiagnóisiú, cinntí deacra a dhéanamh, agus foireann dhíspeagtha a chruinniú. Taispeáin struchtúr, ní draíochta.

## Conas é a bhualadh

```text
1. Diagnose honestly — scope, technical, or people problem?
2. Stabilize — cut scope to a credible, shippable core
3. Rebuild trust with stakeholders via small, frequent wins
4. Re-energize the team with a clear, achievable goal
```

## Sampla oibrithe

```text
S: A project was three months late with a burned-out team and no clear end.
T: Leadership asked me to get it back on track.
A: I found the real issue was scope creep, not ability. I renegotiated to a
   focused MVP, set a weekly demo cadence to rebuild stakeholder trust, and
   protected the team from new requests.
R: We shipped the MVP in six weeks; stakeholders got value early and signed off
   on a realistic plan for the rest.
```

## Go maith vs lag

```text
✓ Diagnose, cut scope, rebuild trust, protect the team
✗ "I just told everyone to work harder"
✗ Blaming the previous lead with no plan
```

## Cén fáth a bhíonn sé tábhachtach

Tá diagnóis shimplí, gan locht, ag teastáil ó thionscadail i dtrioblóid — is gnách gur scóip nó soiléireacht atá sa chúis, ní iarracht.

Athbhunú na muiníne rannpháirtithe atá caillte ag tionscadal déanach le bheith ina gcóir beag agus go minic.

Foireann dhíspeagtha a dhíon agus a athbheochan is stíuradh é nach féidir a bhaint amach le soláthair amháin.