Tamed Agility in Developing Mobile Business Systems
Mobile systems are determined by requirements which tend to change over time. Agile approaches seem to address this, but fail to provide reliable project plans, budget estimations and capacity forecasts. Thus, mobile enterprise applications demand for tamed agility, reconciling advantages of agile development and plan-driven approaches. In this paper, this tradeoff is addressed. The Interaction Room method is introduced as a low-tech method to support value-oriented development of mobile applications.
KeywordsMobile systems agile development modeling team interaction
Unable to display preview. Download preview PDF.
- 3.Whitehead, J.: Collaboration in software engineering: A roadmap. In: Proc. Future of Software Engineering (FOSE 2007), pp. 214–225. IEEE Computer Society (2007)Google Scholar
- 7.Burge, J., Carroll, J., McCall, R., Mistrík, I.: Rationale-based software engineering. Springer (2008)Google Scholar
- 8.Schwaber, K., Beedle, M.: Agile Software Development with Scrum. Prentice Hall (2002)Google Scholar
- 9.Pavlovski, C.J., Zou, J.: Non-functional requirements in business process modeling. In: Proc. 5th Asia-Pacific Conference on Conceptual Modeling (APCCM 2008), pp. 103–112. Australian Computer Society (2008)Google Scholar
- 10.Bocciarelli, P., d’Ambrogio, A.: A BPMN extension for modeling non-functional properties of business processes. In: Proc. 2011 Symposium on Theory of Modeling & Simulation (TMS-DEVS 2011), pp. 160–168. Society for Computer Simulation (2011)Google Scholar