Re: Creepy Scope
Someone disagree with some of the points here.
Getting a list of requirements out of the client should not be hard, it all comes down to the person asking for the requirements.
As a contractor myself, if I get a particularly weak set of requirements, I will identify the team for whom I'm supposed to be building out a solution for and I will go to them, I will speak to them.
They are the ones that will be using the system, not their PM, not their bean counters etc etc.
In the initial meetings, if there is nobody present that is actively using the system that they're asking me to upgrade, design...whatever...I will see red flags and GTFO. Because that is a project that is about to have a low budget and a long running time coupled with a probably civil lawsuit at the end of it. Fuck that.
If you have access to the staff and you can keep proof of the project managers incompetence in your back pocket, it might be worth the risk, but otherwise...leave it. Don't even quote for it.