Requirements management (RM) is defined as a set of activities to gather requirements, prioritized requirements (triage), and documenting requirements. The requirements would be a product of compromise between marketing (representing users), developers who build the software, and finance department who make the budget. In this paper we would like to show how to understand RM process in less than ideal world. Requirements are not a product of compromise. Requirements are product of power struggle between those 3 parties. The three parties would try to win the struggle and imposing their own agenda (including requirements) into the final products. We argue that Actor Network Theory could explain such phenomena better.