One way to do this is to point out how the requirements are vague, lack context and fail to state how the requirement will benefit the business. Point out how i

One way to do this is to point out how the requirements are vague, lack context and fail to state how the requirement will benefit the business. Point out how it is sloppiness in documenting requirements that leads to scope creep, cost overruns and ultimately, failure of the business. Tell management that if they really want to give developers responsibility for finding out what is needed then they should fire all the business analysts, project managers and product managers that are not doing their jobs properly. Alternatively, they could accept new processes that make sure requirements are clearly written and include acceptance criteria.