Mourouganandame Arunachalam wrote:
My question is, when we open (released often to the customer) the testing as soon as the code is ready, will not increase the complexity of the development? Will it not create room for the user to think in multi dimentional on his initial requirement and keep on change his base requirement?
Yes, if I understand you correctly, that is exactly what will happen. And that's a good thing - we will learn earlier what the user *really* needs. That puts us in a positition where we are able to produce what is actually needed, instead of what we initially thought would be needed.
I think this will lead to explode the initial requirement and ends with unmanageable project.
No, it's not unmanageable - it just needs to be managed differently. In fact, the idea is rather simple: you don't plan more in detail than the next iteration (the next one to four weeks). What happens after that is totally open to what you will have learned until then. (There is some less detailed planning for a bigger time span, but no commitment to details. Changing the plan then is not a big deal.)
With other words, requirements don't really explode - they just change, and change in priority.
Does that help?