Abstract
In software engineering, the programmer depends on precise descriptions of the system to be built. To get these descriptions, analysts condense the knowledge about the domain from observations and discussions with the users, the people that will eventually work with the software. The users have to communicate their knowledge about the domain and express their needs. With TBPM we have shown that it is possible for end users to express themselves by means of process models. We now transfer these findings to other fields in software engineering. We investigated in the discipline of requirements engineering, especially in the context of agile software development approaches. From practitioners we learned that during the first iterations, code tends to be thrown away completely since the initial requirements gathering phase is intentionally kept lean. We therefore introduced the concept of need-finding iterations and tackle this problem in our research. We develop a holistic workshop methodology to kick off agile software development projects in which a shared understanding among stakeholders is to be fostered. Discussions that would arise after a software prototype has been implemented are encouraged to be conducted at an earlier stage by making use of an adequate modeling solution. We propose story prototypes which essentially enrich user stories with control flow information and thereby are enhanced to show the big picture rather than just individual aspects of the system to be built. In such a kickoff workshop we encourage a detailed need-finding together with the customer by means of shared model building.
This is a preview of subscription content, log in via an institution to check access.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
References
Alexander IF, Stevens R (2002) Writing better requirements. Addison-Wesley, London
Boehm B, Basili V (2005) Software defect reduction top 10 list. In: Foundations of empirical software engineering: the legacy of Victor R. Basili, p 426
Broß J, Noweski C, Meinel C (2011) Reviving the innovative process of design thinking. In: ICIW 2011, The 6th international conference on internet and web applications and services, pp 142–149
Chen PP (1976) The entity-relationship model – toward a unified view of data. ACM Trans Database Syst 1(1):9–36
Cohn M (2004) User stories applied: for agile software development. Addison-Wesley, Boston
Davis A et al (2006) Effectiveness of requirements elicitation techniques: empirical results derived from a systematic review. In: 14th IEEE international conference requirements engineering, pp 179–188
Diehl M, Stroebe W (1987) Productivity loss in brainstorming groups: toward the solution of a riddle. J Pers Soc Psychol 53(3):497
Dumas M, ter Hofstede A (2001) UML activity diagrams as a workflow specification language. In: The unified modeling language. Modeling languages, concepts, and tools, S.76–90
Edelman J, Grosskopf A, Weske M (2009) Tangible business process modeling: a new approach. In: Proceedings of the 17th international conference on engineering design, ICED’09
Fowler M, Scott K (2000) UML distilled: a brief guide to the standard object modeling language. Addison-Wesley, Reading
Fried J, Hansson DH (2010) ReWork: change the way you work forever, Ebury
Gabrysiak G, Giese H, Seibel A (2009) Interactive visualization for elicitation and validationn of requirements with scenario-based prototyping. In: Requirements engineering visualization (REV), 2009 4th international workshop on, pp 41–45
Gabrysiak G, Giese H, Seibel A (2011) Towards next generation design thinking: scenario-based prototyping for designing complex software systems with multiple users. Des Think 219–236
Gausemeier J, Plass C, Wenzelmann C (2009) Zukunftsorientierte Unternehmensgestaltung–Strategien, Geschäftsprozesse und IT-Systeme für die Produktion von morgen, Hanser Fachbuch
Grosskopf A, Weske M (2010) On business process model reviews. In: Workshop proceedings of ER-POIS: empirical research on process oriented information systems affiliated to CAiSE10, pp 31–42
Keller G, Nüttgens M, Scheer A-W (1992) Semantische Prozessmodellierung auf der Grundlage “Ereignisgesteuerter Prozessketten (EPK)”. Institut für Wirtschaftsinformatik, Saarbrücken
Laue R, Gadatsch A (2010) Measuring the understandability of business process models – are we asking the right questions? In: Proceedings of the 6th international workshop on business process design (BPD 2010)
Lin L, Geng X, Whinston AB (2005) A sender-receiver framework for knowledge transfer. MIS Quart 29:197–219
Luebbe A (2011) Tangible business process modeling – design and evaluation of a process model elicitation technique. Ph.D. dissertation, Hasso Plattner institute for IT systems engineering, University of Potsdam
Luebbe A, Weske M (2011) Determining the effect of tangible business process modeling. In: Plattner H, Meinel C, Leifer LJ (eds) Design thinking – studying co-creation in practice. Springer, New York
Martin RC (2003) Agile software development: principles, patterns, and practices. Prentice Hall, Upper Saddle River
Moody DL (2009) The “physics” of notations: toward a scientific basis for constructing visual notations in software engineering. IEEE Trans Software Eng 35:756–779
Object Management Group (2011) Business process model and notation (BPMN) 2.0
Object Management Group (2012) Unified modeling language (UML) 2.5
Patig S (2008) A practical guide to testing the understandability of notations. In: Proceedings of the 5th on Asia-Pacific conference on conceptual modelling, vol 79, pp 49–58
Pohl K (2010) Requirements engineering: fundamentals, principles, and techniques. Springer, New York
Recker J, Dreiling A (2009) Does it really matter which process modeling grammar we use? An experimental study on understanding process models. Inform Software Tech
Royce W (1970) Managing the development of large software systems. In: Proceedings of IEEE WESCON, vol 26. Los Angeles
Russell N et al (2006) On the suitability of UML 2.0 activity diagrams for business process modelling. In: Proceedings of the 3rd Asia-Pacific conference on conceptual modelling, vol 53, pp 95–104
Schwaber K (2004) Agile project management with Scrum. Microsoft Press, Redmond
Smith P, Reinertsen D (1998) Developing products in half the time: new rules, new tools. Wiley, New York
Soni N, Soni A (2011) Agile release planning. Arete Solutions LLC
Steinberg DH, Palmer DW (2003) Extreme software engineering a hands-on approach. Prentice-Hall, Upper Saddle River
Van Der Aalst WMP, Ter Hofstede AHM (2005) YAWL: yet another workflow language. Inf Syst 30(4):245–275
Wohed P et al (2006) On the suitability of bpmn for business process modelling. Lect Notes Comput Sci 4102:161
Zeichick A (2004) UML adoption making strong progress. Software development times, 15 Aug 2004
Author information
Authors and Affiliations
Corresponding author
Editor information
Editors and Affiliations
Rights and permissions
Copyright information
© 2014 Springer International Publishing Switzerland
About this chapter
Cite this chapter
Guentert, M., Luebbe, A., Weske, M. (2014). Sharing Knowledge Through Tangible Models: Designing Kickoff Workshops for Agile Software Development Projects. In: Leifer, L., Plattner, H., Meinel, C. (eds) Design Thinking Research. Understanding Innovation. Springer, Cham. https://doi.org/10.1007/978-3-319-01303-9_13
Download citation
DOI: https://doi.org/10.1007/978-3-319-01303-9_13
Published:
Publisher Name: Springer, Cham
Print ISBN: 978-3-319-01302-2
Online ISBN: 978-3-319-01303-9
eBook Packages: Business and EconomicsBusiness and Management (R0)