Abstract
This chapter defines the aim of the Interaction Room—fostering understanding between stakeholders and focusing their communication on those aspects that are critical to the success of a project—and describes key principles that shape the Interaction Room method. These principles include for example involving domain experts, favoring relevance over completeness, favoring clarity over precision, defining value and effort drivers, managing late as well as early requirements, revealing uncertainties early, making cost changes transparent, and building trust between stakeholders.
This is a preview of subscription content, log in via an institution.
Buying options
Tax calculation will be finalised at checkout
Purchases are for personal use only
Learn about institutional subscriptionsPreview
Unable to display preview. Download preview PDF.
References
Behrens CA (1983) Measuring the productivity of computer systems development activities with function points. IEEE Transactions on Software Engineering 9(6):648–652. doi:10.1109/TSE.1983.235429
Biffl S et al (2006) Value-based software engineering. Springer
Boehm B (1981) Software engineering economics. Prentice Hall, ch 21
Boehm B et al (2000) Software cost estimation with COCOMO II. Prentice Hall
Constantine LL, Lockwood LAD (1999) Software for use: A practical guide to the models and methods of usage-centered design. Addison-Wesley, ch 5
Curtis B, Krasner H, Iscoe N (1988) A field study of the software design process for large systems. Comm ACM 31(11):1268–1287. doi:10.1145/50087.50089
Denne M, Cleland-Huang J (2003) Software by numbers: Low-risk, high-return development. Prentice Hall
Gold-Bernstein B, Ruh W (2004) Enterprise integration: The essential guide to integration solutions. Addison-Wesley
Langley A (1995) Between ‘paralysis by analysis’ and ‘extinction by instinct’. Sloan Management Review 36(3):63–76
Lehman MM (1989) Uncertainty in computer application and its control through the engineering of software. Journal of Software Maintenance 1(1):3–27. doi:10.1002/smr.4360010103
McCabe TJ (1976) A complexity measure. IEEE Transactions on Software Engineering 2(4):308–320
McConnell S (2006) Software estimation: Demystifying the black art. Microsoft Press, ch 18.2
McMenamin SM, Palmer JF (1984) Essential systems analysis. Yourdon
Pohl K, Rupp C (2015) Requirements engineering fundamentals: A study guide for the certified professional for requirements engineering exam – Foundation level – IREB compliant. Rocky Nook
Wohlin C, Aurum A (2006) Criteria for selecting software requirements to create product value: An industrial empirical study. In: Biffl S et al (eds) Value-based software engineering. Springer, pp 179–200
Author information
Authors and Affiliations
Corresponding author
Rights and permissions
Copyright information
© 2016 Springer International Publishing Switzerland
About this chapter
Cite this chapter
Book, M., Gruhn, V., Striemer, R. (2016). A Room for Ideas. In: Tamed Agility. Springer, Cham. https://doi.org/10.1007/978-3-319-41478-2_2
Download citation
DOI: https://doi.org/10.1007/978-3-319-41478-2_2
Published:
Publisher Name: Springer, Cham
Print ISBN: 978-3-319-41476-8
Online ISBN: 978-3-319-41478-2
eBook Packages: Computer ScienceComputer Science (R0)