Information Systems (IS) requirement risks are one of the most important sources that contribute to project problems, such as escalation of project cost and schedule. Early identifying and managing requirement risks is therefore an important task to avoid project complexity and increase chance of project success. Earlier research has identified various requirement risks in IS project. However, there has been little research on explaining the emergence of requirement risks. This paper proposes some initial insights into the origins of requirement risks based on a case study of an IS project having requirement risks. The results of this study suggest that the emergence of requirement risks can be identified and explained from various IS development (ISD) practices and some organisational behaviours perspectives. Moreover, requirements risk can occur not only in the requirement collection and analysis phase, but also in the later phases of the ISD. Conclusion and implications for future research are also provided.