PD and joint application design: a transatlantic comparison
Communications of the ACM - Special issue Participatory Design
Value-based software engineering
ACM SIGSOFT Software Engineering Notes
Security Requirement with a UML 2.0 Profile
ARES '06 Proceedings of the First International Conference on Availability, Reliability and Security
A BPMN Extension for the Modeling of Security Requirements in Business Processes
IEICE - Transactions on Information and Systems
Extending BPMN for Supporting Customer-Facing Service Quality Requirements
ICWS '10 Proceedings of the 2010 IEEE International Conference on Web Services
Seeing the forest and the trees: focusing team interaction on value and effort drivers
Proceedings of the ACM SIGSOFT 20th International Symposium on the Foundations of Software Engineering
Hi-index | 0.00 |
Large-scale information system evolution projects often place high demands on both business and technical stakeholders' cognitive and communication skills. Especially if the need for evolution is not confined to a particular feature, but affects the whole value chain, finding dependencies and interrelationships between processes and components is challenging as it requires cross-departmental understanding. These issues can be even more challenging for management stakeholders who need to make high-level and far-reaching decisions on implementation strategies despite not being deeply involved in the technical details. One of the main problems in such projects is that the stakeholders who have expert knowledge typically have only little methodical experience, while the method experts lack the business experience. In this paper, we report on experiences and lessons from a large systems evolution project in a German insurance company, where we applied a new approach -- the so-called "Interaction Room" -- to improve stakeholders' understanding of the project's risks and dependencies in a pragmatic way, without overwhelming them with a heavyweight analysis method.