Regarding #3: I totally agree. One common excuse (from the client perspective) for changing or adding requirements after the project has entered some crucial phase: It's just a minor thing to add/change.
The truth is: Many major pain points used to be just "minor things". If it's small enough to be "minor" it shouldn't be a big problem to postpone it to a later release.
Another pattern to watch out for here is under-specified requirements: Things that look simple at first glance but turn out to be much more complex once you get to understand them better (which typically happens during the implementation phase).
Regarding #3: I totally agree. One common excuse (from the client perspective) for changing or adding requirements after the project has entered some crucial phase: It's just a minor thing to add/change.
The truth is: Many major pain points used to be just "minor things". If it's small enough to be "minor" it shouldn't be a big problem to postpone it to a later release.
Another pattern to watch out for here is under-specified requirements: Things that look simple at first glance but turn out to be much more complex once you get to understand them better (which typically happens during the implementation phase).
Thanks for the add on Sebastian! This would be valuable for all of us who are going through the journey