<humor>
The customer knows what he wants; developers know how to build it and nothing will change along the way? If that’s your context you should take look on waterfall manifesto or attend some conferences.</humor>
Otherwise agile manifesto is way to go.
But is there actually anything good on waterfall or v-model?
It seems that it easier to sell and buy projects with predefined focus and clear ending than “we just do what you want”-kind of deal. Are we bold enough to share the risk with customer and can customer participate enough for "Money for Nothing, Change For Free".
Or do auditors like so much the verification and validation that there's no way to use agile methods on certified quality management system?
Most of time we have to do some compromise between traditional and agile methods, but I think that's actually good thing. Isn't it actually more agile to use even waterfall if customer really wants that than selfishly trying to push scrum?
No comments:
Post a Comment