Business processes evolve throughout their lifecycle of change. Business Process Modeling (BPM2) notations such as BPMN are used to effectively conceptualize and communicate important process characteristics to relevant stakeholders. Agent-oriented conceptual modeling notations, such as i*, effectively capture and communicate organizational context. In this paper we argue that the management of change throughout the business process model lifecycle can be more effectively supported by combining notations. In particular, we identify two potential sources of process change, one occurring within the organizational context and the other within the operational context. As such the focus in this paper is on the co-evolution of operational (BPMN) and organizational (i*) models. Our intent is to provide a way of expressing changes, which arise in one model, effectively in the other model. We present constrained development methodologies capable of guiding an analyst when reflecting changes from an i* model to a BPMN model and vice-versa.