New answers tagged

1

Here’s the iron rule: The customer is always right - if the customer pays. Now your job would be to bring them guidance. That needs to be agreed one level above your actual contacts, that they need to provide you with requirements and if they don’t, you can go to the person one level higher who tells them to help you. But most important is that you’re paid ...


3

What you describe is not uncommon. In fact, in most projects the customer does not fully know up front what their exact requirements are. This is why the infamous Waterfall Model almost never works. In any real-world project you will have changing requirements and new discoveries during the development process. The process has to be able to accommodate it. ...


0

January: MVP Model grew - I accepted the additional work. This is when you messed up. You created an expectation that the requirements can be changed at any point without impact to the delivery schedule. Take this as a lesson for your next engagement. You need to set up clear boundaries around how change requests will be accepted and how that will relate ...


Top 50 recent answers are included