Mike Cohn was worrisome about Iterative Waterfall poping up these latest years:
“Because they’re trying to be agile, they do this with user stories. But rather than treating the user stories as short placeholders for future conversations, each user story becomes a mini-specification document”
He even noticed :
In some companies, it’s the programmers who force this way of working. They take an attitude of saying they will build whatever is asked for, but you better tell them exactly what is needed at the start of the sprint.
This happens especially in some parts of big Corporates who have been infected by Waterfall methodology for so many years. Contrary to Startup World, especially when not in direct contact with mass consumers, the pressure of competition is less harsh, programmers have a real power and impose the way they want to work.
Why? Because they do not have the Agile Mindset and they want their specs written by Business Users or rather some Business Analysts before doing any prototype. It is obvious that this violates the very purpose of Agile Manifesto which focuses on the need for Collaboration :
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
So what are the dangers of applying such process?
To be continued …