Q: What would be the right approach or main reasons when convincing a client to switch from the classic Waterfall to Agile? What would be his main benefits (business wise)?
Some of the first folks said:
the client needs to feel the pain of waterfall first, or they won't have a compelling reason to make the shiftor something like it. This bothers me greatly.
Doing waterfall first can help, but do we really want to say that Agile can only be sold when the pain of waterfall has been felt?Your thoughts?
I'd start with these two points...
1- you can cancel the project at the end of any iteration if you are not happy and still have delivered business value. With waterfall this typically only happens at the very end.
2- You can change the scope as you learn and see your product grow and there are options for still delivering business value at dates before the end of the project.