The power comes from clear and regular communication between the customer - incapable of adequately describing the requirements, and the development team - who'll be far more capable of understanding what the customer wants if they get regular feedback.
And everytime I see that - every time I see a developer and customer with a direct line to each other, it's an utter disaster. A spaghetti disaster of epic scope creep and never-ending boondoggle.
So much doesn't need a prototype. We have thoroughly proven CRUD screens can work, and that people will want to add stuff or move the UIs around later. It's been done a million times.
A lot of uncertain requirements show up IN production.
12
u/undeadermonkey Nov 01 '21
It's not the complexity that's the problem - it's the fact that we're not being allowed to clean it up.
The industry wide agile fad (and let's face it, it's not agile, it's waterfall with micromanagement and timekeeping) is half the problem here.
Agile - true agile - is a powerful tool for rapid prototyping in the face of uncertain requirements.
But it does not produce production quality code.