Abstract
Well-defined requirements articulating user expectations and needs are a key to successful implementation of software development project. However, business process experts often lack experience in requirement definition, are ill-equipped to interact directly with system developers and sometimes are even unable to agree upon common understanding of the expect end-product. To mitigate this issue, projects frequently involve a so called “bridge person” – a team member with an objective to facilitate smooth communication among technical and non-technical individuals. The objective of this paper is to evaluate “bridge person” importance and summarize aspects that impact selection of a right “bridge person” type in particular software development project. The paper summarizes information about the role of “bridge person” and presents the survey of industry’s perception of this role.
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
Standish Group: Standish Group 2015 Chaos Report. https://www.infoq.com/articles/standish-chaos-2015
Attarzadeh, I., Siew, H.: Project management practices: success versus failure. In: Proceedings of the 2008 International Symposium on Information Technology (2008)
Stepanek, G.: Software Project Secrets: Why Software Projects Fail. Apress, New Zealand (2005)
Kumari, S., Pillai, A.: Requirements elicitation issues and project performance: a test of a contingency model. In: Proceedings of the 2015 Science and Information Conference (2015)
Liao, H.: Requirement elicitation of enterprise informationization from view of VCA. In: Proceeding of the 2010 International Conference on Networked Computing (2010)
Noraini, C., Abdullah, M.: Requirement elicitation: identifying the communication challenges between developer and customer. Int. J. New Comput. Architectures Their Appl., 371–383 (2011)
Arif, S., Khan, Q., Gahyyur, S.: Requirements engineering processes, tools/technologies, & methodologies. Int. J. Rev. Comput., 41–56 (2009–2010)
More, J., Stieber, A.J., Liu, C.: Breaking Into Information Security. Syngress, USA (2016)
Haron, A., Sahibuddin, S.: The strength and weakness of requirement engineering (RE) process. In: 2nd International Conference on Computer Technology and Development (2010)
Eleiche, A.M., Ahmad, I., Elish, M.O.: Design requirements in software and engineering systems. Ind. Eng. Manage. Syst., 70–81 (2012)
Wiegers, K., Beatty, J.: Software Requirements. Microsoft Press (2013)
Hickey, A., Davis, A.: A tale of two ontologies: the basis for systems analysis technique selection. In: 9th Americas Conference on Information Systems (2003)
International Institute of Business Analysis: A guide to the business analysis body of knowledge (BABOK). International Institute of Business Analysis (2015)
Young, R.R.: The Requirements Engineering Handbook. Artech House Print on Demand (2003)
Darvill, L.: The importance of personal skills for the expert business analyst. Analysts Anonymous 11 (2012)
Lazdāne, G.: Projekta vadība un Biznesa analīze – duets vai solo? http://www.slideshare.net/IIBA_Latvia_Chapter/ba-pv-21112013lnpva
IEEE Computer Society: Guide to the Software Engineering Body of Knowledge (SWEBOK). IEEE Computer Society Press (2014)
ISO/IEC 12207:2008 Systems and software engineering – Software life cycle processes (2008)
Project Management Institute: A Guide to the Project Management Body of Knowledge (PMBOK). Project Management Institute, Inc. (2013)
Yu Beng, L., Wooi Khong, L., Wai Yip, T., Soo Fun, T.: Software development life cycle agile vs traditional approaches. In: 2012 International Conference on Information and Network Technology (2012)
Larman, C.: Agile and Iterative Development: A Manager’s Guide. Addison-Wesley Professional (2004)
Paetsch, F., Eberlein, A., Maurer, F.: Requirements engineering and agile software development. In: 12th IEEE International Workshops on Enabling Technologies: Infrastructure for Collaborative Enterprises (2003)
Gregorio, D.D.: How the Business Analyst Supports and Encourages Collaboration on Agile Projects. IEEE (2012)
Technology evaluation centers: what is decision matrix? http://www.rfp-templates.com/What-is/Decision-Matrix
Triantaphyllou, E., Mann, S.H.: Using the analytic hierarchy process for decision making in engineering applications: some challenges. Int. J. Ind. Eng. Appl. Pract., 35–44 (1995)
Author information
Authors and Affiliations
Corresponding author
Editor information
Editors and Affiliations
Rights and permissions
Copyright information
© 2017 Springer International Publishing AG
About this paper
Cite this paper
Bormane, L., Bērziša, S. (2017). Role of “Bridge Person” in Software Development Projects. In: Damaševičius, R., Mikašytė, V. (eds) Information and Software Technologies. ICIST 2017. Communications in Computer and Information Science, vol 756. Springer, Cham. https://doi.org/10.1007/978-3-319-67642-5_1
Download citation
DOI: https://doi.org/10.1007/978-3-319-67642-5_1
Published:
Publisher Name: Springer, Cham
Print ISBN: 978-3-319-67641-8
Online ISBN: 978-3-319-67642-5
eBook Packages: Computer ScienceComputer Science (R0)