How business requirements communicate with technology in software development : case Integrify Oy
Nguyen, Quang Minh (2020)
Avaa tiedosto
Lataukset:
Nguyen, Quang Minh
2020
All rights reserved. This publication is copyrighted. You may download, display and print it for Your own personal use. Commercial use is prohibited.
Julkaisun pysyvä osoite on
https://urn.fi/URN:NBN:fi:amk-2020100821145
https://urn.fi/URN:NBN:fi:amk-2020100821145
Tiivistelmä
In the rush-to-market livelihood, some start-up companies pay less attention to the analysis phase for the project. It is one of the factors that can save the repairing cost of the final delivery. For building an application that matches customers’ expectations and brings value to the business, the developers should understand clearly the business objectives and goals. Thus, the transferring business requirements process to the development team is crucial to the initial phase before the implementation phase.
The thesis’s case study for the development idea is Integrify. A software development company, which provides talent services through training software development and machine learning programs for international talented people. Besides, they also provide consulting services. The thesis aims to help Integrify to enhance the process of transferring business requirements to developers. As they are a small company with a vision mission to grow their business and have a strong consultant team to get more complex and larger projects. Therefore, the developer can build their experience in software development through challenges.
The method used in the thesis is qualitative research, with an in-depth interview for gathering data. The interview is taken from both stakeholders of Integrify and external stakeholders from different companies. Thus, the understandings of different perspectives and experiences in the transferring process. The target groups are people working in three main role groups, such as project manager/product owner/project lead, developer, quality assurance/tester. To answer the main research question, the process diagram of transferring the business requirements of Integrify was illustrated from the interview with internal stakeholders. Along with three sub- questions are generated to support the research topic based on different stakeholders’ experiences sharing.
The research findings suggest the involvement and communication of Integrify’s internal process, and resources need. Additionally, the new way of documenting the business requirements as well as their content are given in the recommendation.
The thesis’s case study for the development idea is Integrify. A software development company, which provides talent services through training software development and machine learning programs for international talented people. Besides, they also provide consulting services. The thesis aims to help Integrify to enhance the process of transferring business requirements to developers. As they are a small company with a vision mission to grow their business and have a strong consultant team to get more complex and larger projects. Therefore, the developer can build their experience in software development through challenges.
The method used in the thesis is qualitative research, with an in-depth interview for gathering data. The interview is taken from both stakeholders of Integrify and external stakeholders from different companies. Thus, the understandings of different perspectives and experiences in the transferring process. The target groups are people working in three main role groups, such as project manager/product owner/project lead, developer, quality assurance/tester. To answer the main research question, the process diagram of transferring the business requirements of Integrify was illustrated from the interview with internal stakeholders. Along with three sub- questions are generated to support the research topic based on different stakeholders’ experiences sharing.
The research findings suggest the involvement and communication of Integrify’s internal process, and resources need. Additionally, the new way of documenting the business requirements as well as their content are given in the recommendation.