Advertisement

Role of “Bridge Person” in Software Development Projects

  • Līga Bormane
  • Solvita Bērziša
Conference paper
Part of the Communications in Computer and Information Science book series (CCIS, volume 756)

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.

Keywords

“Bridge person” Software development project Business requirements Stakeholders Requirements analysis 

References

  1. 1.
    Standish Group: Standish Group 2015 Chaos Report. https://www.infoq.com/articles/standish-chaos-2015
  2. 2.
    Attarzadeh, I., Siew, H.: Project management practices: success versus failure. In: Proceedings of the 2008 International Symposium on Information Technology (2008)Google Scholar
  3. 3.
    Stepanek, G.: Software Project Secrets: Why Software Projects Fail. Apress, New Zealand (2005)Google Scholar
  4. 4.
    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)Google Scholar
  5. 5.
    Liao, H.: Requirement elicitation of enterprise informationization from view of VCA. In: Proceeding of the 2010 International Conference on Networked Computing (2010)Google Scholar
  6. 6.
    Noraini, C., Abdullah, M.: Requirement elicitation: identifying the communication challenges between developer and customer. Int. J. New Comput. Architectures Their Appl., 371–383 (2011)Google Scholar
  7. 7.
    Arif, S., Khan, Q., Gahyyur, S.: Requirements engineering processes, tools/technologies, & methodologies. Int. J. Rev. Comput., 41–56 (2009–2010)Google Scholar
  8. 8.
    More, J., Stieber, A.J., Liu, C.: Breaking Into Information Security. Syngress, USA (2016)Google Scholar
  9. 9.
    Haron, A., Sahibuddin, S.: The strength and weakness of requirement engineering (RE) process. In: 2nd International Conference on Computer Technology and Development (2010)Google Scholar
  10. 10.
    Eleiche, A.M., Ahmad, I., Elish, M.O.: Design requirements in software and engineering systems. Ind. Eng. Manage. Syst., 70–81 (2012)Google Scholar
  11. 11.
    Wiegers, K., Beatty, J.: Software Requirements. Microsoft Press (2013)Google Scholar
  12. 12.
    Hickey, A., Davis, A.: A tale of two ontologies: the basis for systems analysis technique selection. In: 9th Americas Conference on Information Systems (2003)Google Scholar
  13. 13.
    International Institute of Business Analysis: A guide to the business analysis body of knowledge (BABOK). International Institute of Business Analysis (2015)Google Scholar
  14. 14.
    Young, R.R.: The Requirements Engineering Handbook. Artech House Print on Demand (2003)Google Scholar
  15. 15.
    Darvill, L.: The importance of personal skills for the expert business analyst. Analysts Anonymous 11 (2012)Google Scholar
  16. 16.
    Lazdāne, G.: Projekta vadība un Biznesa analīze – duets vai solo? http://www.slideshare.net/IIBA_Latvia_Chapter/ba-pv-21112013lnpva
  17. 17.
    IEEE Computer Society: Guide to the Software Engineering Body of Knowledge (SWEBOK). IEEE Computer Society Press (2014)Google Scholar
  18. 18.
    ISO/IEC 12207:2008 Systems and software engineering – Software life cycle processes (2008)Google Scholar
  19. 19.
    Project Management Institute: A Guide to the Project Management Body of Knowledge (PMBOK). Project Management Institute, Inc. (2013)Google Scholar
  20. 20.
    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)Google Scholar
  21. 21.
    Larman, C.: Agile and Iterative Development: A Manager’s Guide. Addison-Wesley Professional (2004)Google Scholar
  22. 22.
    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)Google Scholar
  23. 23.
    Gregorio, D.D.: How the Business Analyst Supports and Encourages Collaboration on Agile Projects. IEEE (2012)Google Scholar
  24. 24.
    Technology evaluation centers: what is decision matrix? http://www.rfp-templates.com/What-is/Decision-Matrix
  25. 25.
    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)Google Scholar

Copyright information

© Springer International Publishing AG 2017

Authors and Affiliations

  1. 1.Information Technology InstituteRiga Technical UniversityRigaLatvia

Personalised recommendations