Legacy V-cycles (needs - spec - code - test - integration - product) were such that everything was written down and planned in advance for months/years. So, if the customer had made an error, his/her needs had changed... you were basically screwed.
Agile advocates for Short V cycles while getting often user feedback. But it's a V cycle.
- PO speaks to the customer = get needs
- PO writes tickets, UX design something = specification
- And then it follows the classical cycle : develop, test, integrate, deliver.
What's remain around agile (ceremonies & co) feel much more like bullshit to me, and people follow it religiously without understanding the core idea of agile as they think V cycle is an insult.
Legacy V-cycles (needs - spec - code - test - integration - product) were such that everything was written down and planned in advance for months/years. So, if the customer had made an error, his/her needs had changed... you were basically screwed.
Agile advocates for Short V cycles while getting often user feedback. But it's a V cycle.
- PO speaks to the customer = get needs - PO writes tickets, UX design something = specification - And then it follows the classical cycle : develop, test, integrate, deliver.
What's remain around agile (ceremonies & co) feel much more like bullshit to me, and people follow it religiously without understanding the core idea of agile as they think V cycle is an insult.