Strategies of an IT Company for developing, testing and delivering Software for a

Large Fortune Global 100 Client

Vijay Sharma

Final Thesis Report

October 2024

1
 Declaration

I, Vijay Sharma, hereby declare that the dissertation “Strategies of an IT Company for
Developing, Testing and Delivering Software for a Large Fortune Global 100 Client”,
submitted to Liverpool Business School as a part of my MBA Program, is an original
work carried out by me under the guidance of my Thesis Supervisor Anil Ota.

I further declare that this dissertation has not been previously submitted for the
award of any degree, diploma, fellowship or any such similar titles. Any external
contributions, resources or references have been duly acknowledged and cited in the
dissertation.

I affirm that the content herein represents my work and adheres to academic
standards and ethical principles prescribed by Liverpool Business School.

2
 Acknowledgement

I would like to express my gratitude to my family for their support, understanding and
encouragement throughout the duration of my MBA Program with Liverpool business
school and upgrad. Their belief in my abilities provided me motivation during
challenging times.

I would like to extend sincere thanks to my thesis supervisor anil ota and faculty at
liverpool business school at upgrad and subject matter experts at upgrad whose
guidance have shaped the direction of my research. I am grateful to the insights
provided by Liverpool business school faculty and Upgrad subject matter experts
whose feedback played an important role in preparation of my thesis.

I would also like to acknowledge the help and support my colleagues and batchmates
in upgrad gave me in sharing knowledge and experiences which contributed to this
research.

I am thankful to management and employees of IT Companies that I studied whose

co-operation made this research successful. Their willingness to participate in
research gave important data for my analysis in my research.

Finally, I wish to provide appreciation to Liverpool John Moores University for

providing excellent academic environment and resources for me to prepare my
thesis.

Thank You All for motivation, encouragement, Support and having belief in me.

3
 Abstract

This thesis explains the strategies employed by an IT Company in development,

testing and delivery of software for its large fortune global 100 client. The primary
goal of this research was to analyse how different software development
methodologies, testing frameworks and delivery approaches impact the successful
execution of Large scale and complex IT Projects. The study focuses on agile and
waterfall methodology for software development, integration of automation and
manual testing practices and use of Devos and CI/CD pipelines as key components for
effective and timely delivery of software to the client of an IT Company.

The research methodology includes case study analysis, with quantitative data
gathered from project documents, surveys with IT Company employees. The findings
from this research highlights that hybrid methodology of waterfall and agile allows
flexibility to respond to client needs keeping a structured approach to project
planning. Combining automation and manual testing improves software quality
covering both functional and user experience aspects of the software being delivered
to the Client. Additionally, implementation of Devops practices through CI/CD
Pipelines enhances efficiency of delivering software to the client of the IT company.

There are key challenges like managing scope of the project, integration of software
developed with legacy systems and managing client expectations with project
constraints. This analysis suggests strong stakeholder engagement, robust testing
strategies and flexible software development approaches. This analysis is designed to
overcome these challenges faced by IT Companies.

This study provides valuable insights for IT Companies delivering software solutions
to large clients. It offers recommendations to adopt hybrid methodologies,
strengthen automation testing framework and improve the Devops practices. These
findings are expected to contribute to better project outcomes for future
engagements with large scale clients.

By examining case studies and conducting surveys through questionnaires, this study
aims to identify key factors that contribute to successful software project outcomes
in this context. This study further explores strategies like software architecture and
design principles, risk management, collaboration and communication and fostering
strong collaboration between IT Companies and their Clients. This study offers
recommendation for IT Companies emphasizing the need for ongoing innovation,
focus on delivering high quality software meeting evolving needs of Client’s Business.

4
Key Words: Software Development, Software Testing, Software Delivery, IT Company,
Fortune Global 100 Client, Agile Methodologies Automated Testing, Delivery Models.

5
 List of Figures

Figure 1 – Software Development Process Diagram…………………………………………………11

Figure 2 – Software Development Lifecycle……………………………………………………………..12
Figure 3 – Project Success Metrics and Client Satisfaction……………………………………….20
Figure 4 – Agile Scrum Framework…………………………………………………………………………..22
Figure 5 – Waterfall Software Development Methodology………………………………………23
Figure 6 – Devops and Continuous Integration/Continuous Deployment…………………23
Figure 7 – Collaborative Agile-waterfall Hybrid Model……………………………………………..24
Figure 8 – Quality Assurance Process Flow………………………………………………………………25
Figure 9 – Quality Assurance and Software Testing Pyramid…………………………………….26
Figure 10 – Automation Testing Process…………………………………………………………………..27
Figure 11 – Delivery Process followed by an IT Company…………………………………………28
Figure 12 – Stakeholder Management and Communication Flow…………………………….29
Figure 13 – Risk management Process…………………………………………………………………….30
Figure 14 – Software Testing Lifecycle……………………………………………………………………..45
Figure 15 – Risk Assessment Matrix…………………………………………………………………………48

6
 List of Abbreviations

Agile – Agile Software Development Methodology

AI – Artificial Intelligence
AT – Automation Testing.
CI/CD – Continuous Integration/ Continuous Deployment.
CRM – Customer Relationship Management.
Devops – Development and Operations
ERP – Enterprise Resource Planning
ET – Exploratory Testing.
Fortune Global 100 – List of largest Companies by Revenue.
IT – Information Technology
ITIL – Information Technology Infrastructure Library.
KPI – Key Performance Indicator
ML – Machine Learning
QA – Quality Assurance
R&D – Research and Development
ROI – Return on Investment
SAFe – Scaled Agile Framework
SDLC – Software Development Lifecycle.
SLA – Service Level Agreement
TDD – Test-Driven Development
UAT – User Acceptance Testing
UI – User Interface

7
 Table of Contents

Declaration……………………………………………………………………………………………………………..2
Acknowledgements…………………………………………………………………………………………………3
Abstract…………………………………………………………………………………………………………………..4
List of Figures…………………………………………………………………………………………………………..6
List of Abbreviations………………………………………………………………………………………………..7
Chapter 1 – Introduction…………………………………………………………………………………………11
1.1 Background of Study…………………………………………………………………………………………12
1.2 Problem Statement…………………………………………………………………………………………..13
1.3 Motivation behind the Study…………………………………………………………………………….14
1.4 Aims and Objectives………………………………………………………………………………………….15
1.5 Research Questions…………………………………………………………………………………………..16
1.6 Scope of the Study…………………………………………………………………………………………….16
1.7 Significance of the Study……………………………………………………………………………………17
1.8 Structure of the Study……………………………………………………………………………………….18
Chapter 2 – Literature Review………………………………………………………………………………….19
2.1 Introduction to Literature Review………………………………………………………………………19
2.2 Introduction to Software Development Life Cycle for Large Client……………………..19
2.2.1 Software Development Strategies…………………………………………………………………..22
2.2.2 Challenges in Software Development……………………………………………………………..24
2.3 Strategies for Requirement Gathering in Large IT Projects…………………………………25
2.4 Software Testing Strategies and Quality Assurance……………………………………………26
2.4.1 Software Testing Strategies…………………………………………………………………………….27
2.4.2 Challenges in Software Testing and Quality Assurance……………………………………27
2.5 Project Management and Delivery Strategies…………………………………………………….28
2.6 Communication and Project Management…………………………………………………………29
2.7 Challenges in delivering software to Large Fortune Global 100 Clients………………29
2.8 Conclusion to Literature Review………………………………………………………………………..30
Chapter 3 – Research Methodology…………………………………………………………………………32
3.1 Introduction to Research Methodology……………………………………………………………..33
3.2 Research Design…………………………………………………………………………………………………33
3.3 Data Collection Methods……………………………………………………………………………………34
3.3.1 Primary Data Collection………………………………………………………………………………….34
3.3.2 Secondary Data Collection………………………………………………………………………………36
3.4 Data Analysis Methods……………………………………………………………………………………..36
3.5 Research Validity and Reliability………………………………………………………………………..37
3.5.1 Validity…………………………………………………………………………………………………………..37
3.5.2 Reliability……………………………………………………………………………………………………….37
3.6 Ethical Considerations………………………………………………………………………………………37

8
3.7 Limitations of the Research………………………………………………………………………………38
3.8 Conclusion to Research Methodology………………………………………………………………38
Chapter 4 – Analysis and Implementation……………………………………………………………..40
4.1 Introduction to analysis and implementation…………………………………………………..40
4.2 Analysis of Software Development Strategies………………………………………………….40
4.2.1 Agile and Hybrid methodologies…………………………………………………………………..40
4.2.2 Devops Practices…………………………………………………………………………………………..41
4.2.3 Waterfall Methodology…………………………………………………………………………………42
4.2.4 Lean Development………………………………………………………………………………………..42
4.2.5 Development Phase – Tools, Framework and Practices Used………………………..43
4.3 Analysis of Software Testing Strategies…………………………………………………………….43
4.3.1 Automated Testing………………………………………………………………………………………..43
4.3.2 Manual Testing and User Accepting Testing (UAT)………………………………………….44
4.3.3 More Testing Strategies………………………………………………………………………………….44
4.3.4 Defect Management………………………………………………………………………………………45
4.4 Software Delivery Strategies……………………………………………………………………………..45
4.4.1 Basic Delivery Strategies…………………………………………………………………………………45
4.4.2 Stakeholder Communication and Collaboration……………………………………………..46
4.4.3 Delivery and Deployment……………………………………………………………………………….46
4.5 Analysis of Key Metrics………………………………………………………………………………………46
4.5.1 On time Delivery…………………………………………………………………………………………….47
4.5.2 Budget Adherence………………………………………………………………………………………….47
4.5.3 Defect Rates……………………………………………………………………………………………………47
4.5.4 Client Satisfaction……………………………………………………………………………………………47
4.6 Challenges Faced and Lessons Learned………………………………………………………………47
4.7 Data Analysis and Data Presentation………………………………………………………………….49
4.8. Conclusion to Analysis and Implementation phase……………………………………………55
Chapter 5 – Results and Discussions………………………………………………………………………..57
5.1 Introduction to Results and Discussions…………………………………………………………….57
5.2 Quantitative Results…………………………………………………………………………………………..57
5.3 Key Findings……………………………………………………………………………………………………….58
5.3.1 Strategy Effectiveness in Software Development…………………………………………….58
5.3.2 Strategy effectiveness in software testing……………………………………………………….59
5.3.3 Efficiency of Devops and (CI/CD)…………………………………………………………………….60
5.4 Summary of Key Findings…………………………………………………………………………………..60
5.5 Discussion of Findings………………………………………………………………………………………..61
5.6 Interpretation of Key Metrices…………………………………………………………………………..62
5.7 Challenges and Mitigation in the Project……………………………………………………………64
5.8 Implications for Practice…………………………………………………………………………………….64
5.9 Policy Implication governing software development on broader domain of IT…..65

9
5.10 Conclusion to Results and Discussion………………………………………………………………66
Chapter 6 – Conclusion and Recommendations……………………………………………………….67
6.1.1 Hybrid Methodologies…………………………………………………………………………………….68
6.1.2 Automation and Manual Testing Synergy………………………………………………………..68
6.1.3 Devops and CI/CD Implementation…………………………………………………………………68
6.1.4 Stakeholder Engagement and Communication……………………………………………….69
6.1.5 Challenges and Lessons Learned…………………………………………………………………….69
6.2 Summary of Findings…………………………………………………………………………………………69
6.3 Recommendations…………………………………………………………………………………………….70
6.3.1 Optimize Hybrid Methodology Transitions………………………………………………………70
6.3.2 Increase early investment in software testing automation………………………………70
6.3.3 Strengthen the CI/CD and Devops Practices…………………………………………………...71
6.3.4 Improve Stakeholder Management…………………………………………………………………71
6.3.5 Anticipate and Mitigate Legacy System Integration Issues………………………………71
6.3.6 Proactively Manage Project Scope Creep………………………………………………………..71
6.4 Future Research Directions………………………………………………………………………………..72
6.5 Contributions of this Study………………………………………………………………………………..72
6.6 Final Thoughts……………………………………………………………………………………………………73
References………………………………………………………………………………………………………………74
Appendix – Questionnaire Survey Form used to Collect Data…………………………………..82

10
 Chapter 1 – Introduction

In Today’s Rapidly evolving digital landscape, IT Companies face challenges in

delivering high quality softwares to their client within tight timelines and budget
constraints (Hutchinson, B. et al., 2021). This is particularly applicable to Large
Fortune Global 100 Clients, who often do have complex requirements and stringent
quality standards (Olszewska, J.I. et al., 2020). For meeting such challenges, IT
Companies have to employ effective strategies for software development, software
testing and delivery of software.

This thesis and study focuses on strategies used by IT Company for developing,
testing and delivering software for a large fortune global 100 client. This research
aims to identify key elements of software development lifecycle model, software
testing strategies and software delivery processes and challenges faced by them and
actions taken to overcome them.

Software development and software testing are important aspects of IT Companies

and delivering high quality software to their Client is essential for the success of
these IT Companies (Kyeremeh, K., 2021). Fortune Global 100 Companies have
stringent and complex software requirements and IT Companies have to adopt
effective strategies to meet their expectations and requirements. (Al-Saqqa, S. et al.,
2020).

Figure 1 – Software Development Process Diagram. (Garousi, V. et al., 2020)

The Software Development Landscape is continuously evolving. IT Companies are

facing increasing pressure to deliver high quality, secure, scalable and reliable
software solutions for their Clients, especially Large Fortune Global 100 Companies

11
(Qian, C. et al., 2023).
These Clients have complex requirements, global operations and high tolerance for
risks.
This thesis explores the strategies that an IT Company can implement to ensure in
providing a successful software development project for its large fortune global 100
client. It examines the best practices and methodologies for each phase of the
software development lifecycle focusing on effective communication, agile
approaches, rigorous testing methods and a secure deployment.

1.1 Background of the Study

In this digital era, development testing and delivery of software has become an
important process for IT Companies, especially those working with large fortune
global 100 clients (Bianchi, M. et al., 2020). These companies rely on cutting edge
software solutions to drive efficiency in business, enhance customer satisfaction and
experience and maintain a competitive advantage in their respective industries
(Shrikanth, N.C. et al., 2021). The complex requirements in these projects requires IT
Companies to follow comprehensive strategies that cover the entire software
development lifecycle, starting from requirement gathering till end at deployment
(Fitriyanto, G.A. et al., 2023). Understanding the strategies adopted by IT Companies
to manage such high value projects is important for identifying the best practices to
follow and addressing the challenges in delivering software to the fortune global 100
clients.

Figure 2 – Software Development Lifecycle (Tebes, G. et al., 2020)

The rapid advancements in technology has transformed the way businesses operate
with softwares playing important role in driving innovation and efficiency
(Vishnyakov, A. et al., 2022). Large Fortune global 100 companies increasingly rely on

12
software solutions to meet their complex needs and demand for high quality, reliable
and timely software delivery has become very important. IT Companies have to
develop test and deliver software solutions that align with the strategic objectives of
their Fortune Global 100 Clients (De Silva, D. and Alahakoon, D., 2022).

In today’s digital age, software development plays an important role in success of

large companies. Fortune global 100 companies rely heavily on customized software
solution to get competitive advantage (Goyal, R. and Mistry, P., 2020). IT Companies
that cater to these clients have to adopt effective strategies to develop test and
deliver software to meet the complex requirements of such Large Clients (Smart, J.F.
and Molak, J., 2023).

The rapid evolution of technology has significantly transformed the landscape of IT

Industry. Companies are continuously striving to develop, test and deliver high
quality software solutions to meet dynamic needs of large fortune global 100 clients.
(Morita, H. and Ahmed, W., 2024).
This study explores the strategies employed by IT Companies to ensure the successful
delivery of software projects, focusing on methodologies, tools and practices that
contribute to its effectiveness.

The rapid advancement of technology has led to increasing demand for software
solutions that cater to complex needs of large global enterprises. As a result, IT
Companies are facing challenges in developing testing and delivering high quality
software efficiently and cost effectively (Alazzawi, A. and Rahmatullah, B., 2023). This
study focuses on strategies employed by IT Company to deliver software to their
large fortune global 100 client.

1.2 Problem Statement

Despite of critical nature and importance of software development for large fortune
global 100 clients, IT Companies often face significant challenges in managing these
projects. Scope creep, communication breakdown, integration complexities and rapid
deliveries can lead to project delays, cost overruns, and subpar outcomes (Hasanah,
N. and Indriawan, M.N., 2021). Employees and project managers in IT Companies are
often under immense pressure to deliver the best high-quality software within
timelines and budget which can lead to burnouts and reduced job satisfaction and
job contentment (Bugayenko, Y. et al., 2023). Also, the rapidly evolving technological
landscape poses a challenge to keep up with latest tools technologies and
methodologies (Arvanitou, E.M. et al., 2021). This study seeps to investigate these
challenges and explore strategies that IT Companies can use to mitigate these

13
challenges and risks.

Challenges faced by IT Companies while working with Large Clients can include -
managing complex project requirements and stakeholder expectations, ensuring
timely delivery and keeping tight deadlines, maintaining high quality standards and
keeping low number of defects, addressing security and data privacy issues,
managing large teams and ensuring effective communication (Kuhrmann, M. et al.,
2021).

Despite advancements in technology, IT Companies do face numerous challenges in

developing, testing and delivering softwares. These challenges include managing
complex project requirements, ensuring software quality, meeting tight deadlines
and adapting to changing client needs (Strode, D. et al., 2022). Employees of IT
Companies often face issues like high work load, lack of adequate resources,
communication barriers which could impact project outcomes (Alami, A. et al., 2022).

The IT Company faces several issues in delivering software to its large client, including
managing complex requirements, ensuring quality assurance, and meeting right
deadlines. Additionally, the company must navigate cultural differences and
communication barriers when working with a large global Client (Ahmad, I. et al.,
2020).

The development, testing and delivery of software for large global clients presents
numerous challenges for IT Companies. These challenges may include managing
complexity of client requirements, ensuring integration across geographically
dispersed teams, maintaining high quality standards and adhering to strict deadlines
and budgetary constraints (Tam, C. et al., 2020). Additionally, the evolving
technological landscape and need to stay ahead of competition further adds
complexities to software development process (Weder, B. et al., 2022).
Understanding specific issues and pain points faced by IT Companies in this context is
crucial for identifying effective strategies and best practices.

1.3 Motivation Behind the Study

While there is substantial literature on software development, testing and delivery,

there is a noticeable gap in the research particularly focused on strategies used by IT
Companies to manage large projects for fortune global 100 clients (Persson, J.S. et al.,
2022). Previous studies have concentrated on medium sized projects, or generalized
software engineering practices without delving into requirements and demands of
large high-profile fortune global 100 clients (Decan, A. et al., 2022). This gap in the

14
literature highlights the need for a study that addresses the challenges and strategies
involved in such projects and provide insights that can be applied across the industry.

The literature for software development, testing and delivery strategies for large
fortune global 100 clients is relatively limited and there is a requirement for further
research to address these challenges and identify best practices. This study aims to
fill this gap by exploring strategies employed by IT Companies to develop test and
deliver software to these clients.

A Review of existing literature reveals lack of adequate research on specific strategies

adopted by IT Companies working with large fortune global 100 clients (Frluckaj, H. et
al., 2022). This study aims to fill this knowledge gap by exploring on the best
strategies and practices employed by IT Companies to deliver a successful software
project for their large fortune global 100 clients.

A review of existing literature reveals gaps in understanding the specific strategies

that IT companies use to overcome these challenges (Shastri, Y. et al., 2021). While
there is extensive research on software development methodologies, there is limited
focus on holistic approach that encompasses software development, software testing
and delivery of software for large enterprise clients (Sreekanth, N. et al., 2023). This
study aims to fill this gap by providing a comprehensive analysis of effective
strategies.

There is limited research on specific strategies used by IT Companies to deliver

software to large fortune global 100 enterprises. This study aims to fill this gap by
investigating the strategies employed by an IT Company to develop, test and deliver
software to its large fortune global 100 client.

1.4 Aim and Objectives

The aim of this study is to analyse and identify the strategies that IT Companies use
to develop, test and deliver software for Large Fortune Global 100 Clients.

Objectives of this study includes -

1. To examine the common challenges faced during software development lifecycle

for large clients.

2. To identify the best strategies and practices that contribute to successful delivery
of IT Software projects.

15
3. To evaluate the impact of these strategies on project outcomes including timelines,
budget adherence and client satisfaction.

4. To provide recommendations to IT Companies to improve their software

development processes for large clients.

1.5 Research Questions

1. What are the common challenges faced by IT Companies in developing, testing and
delivering software for large fortune global 100 clients?

2. What strategies do IT Companies employ to overcome these challenges?

3. How do these strategies impact the success of the software projects in aspects of
delivery, tine, cost and client satisfaction?

4. What are the best practices that can be adopted by IT Companies to enhance their
software development process?

1.6 Scope of the Study

This study is focused on IT Industry, examining strategies used by IT Companies for

managing software development, testing and delivery projects for large fortune
global 100 clients. This research will further explore various of software development
lifecycle including requirement gathering, design, coding, testing and deployment. It
will also consider challenges unique to large scale IT Software Projects and how IT
Companies address them. This study will primarily focus on case studies from leading
IT Companies known for handling large high-profile clients and providing analysis of
their strategies and outcomes.

This study will focus on IT Companies that specialize in developing software solution
for large fortune global 100 clients. This research will delve into strategies employed
by these IT Companies in areas of requirement gathering, software development,
testing, delivery, communication, collaboration and risk management.

This study focuses on IT Industry, especially those companies that develop softwares
for large fortune global 100 clients. This study will explode aspects like project
management, quality assurance, stakeholder management and security of the
software being delivered.

16
This study examines various aspects of software development lifecycle including
project management, software development methodologies, software testing
practices and software delivery processes.

This study focuses on the IT Industry, specifically on companies that develop, test and
deliver software for large fortune global 100 clients. It examines various aspects of
software development lifecycle including project management, development
methodologies, software testing practices and software delivery processes.

This study focuses on strategies employed by IT Company to deliver software to its

large fortune global 100 client. The study will examine the software development
lifecycle, quality assurance practices, communication and collaboration strategies and
challenges faced by the IT Company.

1.7 Significance of the Study

The Significance of this study is contributing valuable insights into software

development practices by IT Companies working with large fortune global 100 clients.
By identifying effective strategies and best practices, this study can help other IT
Companies in improving their processes leading to better project outcomes and
higher client satisfaction. Also, the findings of this research can present industry
standards and guide future research in the field of software engineering in handling
large scale high profile high stakes projects.

The findings of this research will contribute to knowledge on software development

strategies for large fortune global 100 clients. By identifying strategies and best
practices, this study can provide valuable insights to IT Companies, their clients, and
stakeholders involved in this software development projects. This research will also
help in improving quality, efficiency and timelines of software delivery, enhancing the
value and impact of software solutions for large fortune global 100 organisations.

This study will contribute to existing body of knowledge by providing insights into
strategies employed by IT Companies when working with large clients. The findings of
this study will be beneficial for IT Companies, Large Corporations and researchers
who are interested in software development and project management.

The findings of this study will provide valuable insights for IT Companies, project
managers and software developers in the IT Companies. By understanding the
strategies and practices, companies can enhance their project outcomes, improve

17
client satisfaction and get a competitive advantage in the industry. This study also
contributes to academic literature by addressing identified gaps and providing
analysis of software development strategies.

This study will contribute to the existing literature on software delivery strategies
used by IT Companies when working with large global enterprises. The findings of
this study can be used by IT Companies to develop and implement effective strategies
for delivering software to large clients, thereby improving their overall performance
and their competitiveness.

1.8 Structure of the Study

The thesis is organised into following chapters -

Chapter 1 – Introduction
Chapter 2 – Literature Review.
Chapter 3 – Research Methodology
Chapter 4 – Analysis and Implementation
Chapter 5 – Results and Discussion
Chapter 6 – Conclusion and Recommendation.

18
 Chapter 2 – Literature Review

2.1 Introduction to Literature Review Chapter

This chapter presents comprehensive review of existing literature on software

development strategies, testing strategies and delivery strategies pertaining to large
fortune global 100 clients. The aim of this chapter is to establish a theoretical
framework for research and provide context for analysis.

This chapter provides review of existing literature related to strategies adopted by IT

Companies to develop test and delivery software for large fortune global 100 clients.
The aim of this chapter to identify gaps in the current research that this thesis seeks
to address.

This literature review chapter provides overview of existing body of knowledge

related to software development, testing and delivery strategies employed by IT
Companies for large fortune global 100 clients. This chapter examines relevant
theoretical frameworks, conceptual models and empirical studies to identify best
practices, challenges and gaps in the current literature.

The literature review provides overview of existing research and theories related to
strategies employed by IT Companies to develop, test and deliver software. This
chapter aims to identify gaps in current knowledge and establish theoretical
foundation for the research.

2.2 Introduction to Software Development Life Cycle for Large Client

Software development lifecycle (SDLC) is a well-established framework used by IT

Companies to design, develop, test and deliver software solutions to their Clients.
Studies by (Soares, E. et al., 2022) laid groundwork for SDLC Methodologies with
introduction of waterfall model, which is regarded widely as the first SDLC Model.
Over time, agile and iterative approaches for SDLC have emerged. Agile
methodologies (William, P. et al., 2021), Devops Strategies (Marek, K. et al., 2021)
and hybrid frameworks have been developed to offer flexibility, speed and
continuous delivery to large enterprises.

Software development strategies are essential frameworks that guide the process
from conception to deployment. They include methodologies, tools and practices for
software development to provide high quality software that meets client’s stringent
requirements and the market demands (Bernsmed, K. et al., 2022). A robust software

19
development strategy aligns project goals with business objectives but also provides
effective resource allocation and risk management throughout the software
development lifecycle (SDLC).

A well-defined software development strategy is crucial for success of any IT Project,

especially when dealing with large fortune global 100 clients. It helps mitigate the
risks, enhance communication among stakeholders, and ensures the software
development team remains focused on project objectives (Beecham, S. et al., 2021).
Effective strategies contribute to higher customer satisfaction by delivering software
solutions that meet or exceed client’s expectations.

Figure 3 – Project Success Metrics and Client Satisfaction. (Sugali, K., 2021).

The choice of software development methodology is crucial in large projects.

Traditional methodologies like waterfall (Kovari, A. et al., 2023) have been replaced
by more flexible SDLC methodologies like agile (Bergenti, F. et al., 2020), scrum
(Islam, G. et al., 2020) and Devops (El Hafi, L. et al., 2022). In context of fortune global
100 clients, a hybrid approach that combines agile and waterfall is often adopted the
meet the demands of large organisations while maintaining flexibility in project
execution (Rahmaniar, W., 2024).

Moreover, adoption of Devops practices has become prevalent in recent years. The
CI/CD pipelines allow IT Companies to speed up delivery cycles while maintaining
quality standards (Rasheed, Z. et al., 2023). Case studies on fortune global 100
companies (Rahy, S. and Bass, J.M., 2022) highlight the value of Devops in reducing
time to market the software and improving the quality of the software.

20
Various software development methodologies have been employed by IT Companies
to deliver software solutions to large clients. Agile methodologies (Shi, W. et al.,
2023) have gained popularity due to flexibility and adaptability. Studies have shown
that agile methodologies improve project success rate (ElBatanony, A. and Succi, G.,
2021), customer satisfaction (Moe, N.B., 2021) and team productivity (Faruk, M.J.H.
et al., 2022). However traditional waterfall methodologies (Holgeid, K.K. et al., 2021)
are still widely used particularly in large scale projects.

Following the chosen SDLC methodology, the development team translates

requirements into functional code using appropriate programming languages and
frameworks. Continuous integration practices ensure frequent code mergers and
automated testing to identify bugs early on (Siddique, S. et al., 2023).

Several studies have exploded the implementation of software development

strategies in large enterprises (Van Hai, V. et al., 2022). Key Findings from these
studies include importance of adopting agile methodologies for flexibility, use of
automated testing frameworks to ensure quality and implementation of CI/CD
Pipeline for efficient delivery.

21
2.2.1 Software Development Strategies

Agile methodology -

Agile is a popular approach that emphasizes on iterative development, collaboration,

flexibility and customer feedback. It allows the software engineering teams to adapt
to changes quickly and deliver the software incrementally. Agile methodology focuses
on iterative development allowing flexibility and continuous feedback. Agile
methodology promotes collaboration and rapid adjustments to changing
requirements (Zahedi, M.H. et al., 2023). Traditional waterfall methodologies may not
be ideal for large complex projects with evolving requirements. Agile methodologies
like scrum or kanban offer greater flexibility, allowing continuous feedback and
adaptation throughout the development process. (Venkatesh, V. et al., 2020)

Figure 4 - Agile Scrum Framework. (Edison, H. et al., 2021).

Waterfall Model -

A traditional linear approach where each phase must be completed before the next
begins. It is less flexible but can be used in projects having well defined requirements.
Waterfall is a linear approach where each phase has to be completed before the next
phase begins. This method is less flexible and can be effective only for those projects
having well defined requirements (Gupta, V. et al., 2020).

22
Figure 5 – Waterfall Software Development Methodology. (Barraood, S.O. et al.,
2021).

Devops Model -

This strategy integrates development and operations to improve the collaboration

and productivity of team by automating workflows and continuously measuring
software application performance. Devops combines software development with IT
operations to shorten the development lifecycle and deliver high quality software
continuously (Rankovic, D. et al., 2021).

Figure 6 – Devops and Continuous Integration/Continuous Deployment. (Alyahya, S.,

2020).

23
Lean Development Model -

Emphasizes efficiency and value delivery, aiming to eliminate waste and improve the
processes.

Hybrid Approaches -

Combining elements of waterfall and agile can be beneficial. A high-level project plan
may be established upfront using waterfall principles while individual sprints in the
project can utilize agile methodology (Noorani, N.M. et al., 2022).

Figure 7 – Collaborative Agile-waterfall Hybrid Model. (Zorzetti, M. et al., 2022).

2.2.2 Challenges in Software Development

There are several challenges in the software development process -

Scope Creep – Uncontrolled changes or continuous growth in project scope can lead
to delays as well as increased costs. Establishing clear boundaries and managing
stakeholder expectations is essential (Dudhat, A. and Abbasi, M.A., 2021).

Communication Gap – Miscommunication among team members and stakeholders

can result in misunderstanding affecting project outcomes. Regular updates and
collaborative software tools can help bridge these gaps (Sathe, C.A. and Panse, C.,
2022).

24
Quality Assurance – Ensuring high quality software requires rigorous testing and
validation processes. Implementing continuous integration and continuous delivery
CI/CD practices can enhance quality control (Saeeda, H. et al., 2023).

Figure 8 – Quality Assurance Process Flow. (Pargaonkar, S., 2023).

2.3 Strategies for Requirement Gathering in Large IT Projects

For large projects, gathering and managing requirements is essential to ensure

alignment with client expectations. Fortune global 100 companies with complex
organisational structures, have complex requirements. (Nurwidyantoro, A. et al.,
2021) emphasizes the importance of structured approach to requirements
engineering. More recent studies by (Doyle, M. et al., 2020) advocate use of
advanced techniques like stakeholder analysis, surveys and use case modelling when
dealing with large multinational clients.

The literature also highlights challenges associated with requirement volatility. The
work of (Iftikhar, A. et al., 2021) shows that managing evolving requirements for large
clients demand adaptive frameworks like agile or scaled agile framework, to ensure
continuous engagement and feedback loops with stakeholders.

Requirement Gathering – This phase involves in-depth discussion with stake holders,
conducting workshops, and analysing existing systems to identify pain points, desired
functionalities and integration needs.

Documentation – Captured requirements should be well documented in a format

understandable to both technical and non-technical stake holders. Use cases, user
stories and system flow diagrams can help visualize and detail the software’s
functionality.

25
Joint Prioritization – Prioritization workshops with clients helps establish clear
expectations and ensure development focuses on most critical functionalities first.

2.4 Software Testing Strategies and Quality Assurance

Software testing plays an important role in ensuring software quality for large clients
with complex and mission critical systems. Literature on software testing
methodologies (Tuarob, S. et al., 2021) provides a broad spectrum of approaches
from unit testing, integration testing and system testing to user acceptance testing.
With Large clients, automation testing is also increasingly focused upon. The study by
(Trigo, A. et al., 2022) underlines the importance of automation testing in improving
efficiency and ensuring thorough test coverage in large and complex systems.

Figure 9 – Quality Assurance and Software Testing Pyramid. (Christanto, H.J. et al.,
2023).

Recent studies advocate use of test-driven development and behaviour driven

development as effective ways to incorporate testing at early stages in SDLC (Licorish,
S.A. et al., 2022). These methodologies combined with automation testing, helps
ensure that the software is robust and can scale with the demands of large
companies. Software tools like selenium, Junit and Jenkins are frequently cited in
case studies of large IT Projects (Rashid, N. et al., 2021).

A comprehensive testing strategy should be employed encompassing unit testing,

integration testing, system testing and user acceptance testing. Automated testing
tools should be utilized to streamline processes and ensure thorough testing.
Automated testing tools should be utilized to streamline the processes and ensure
thorough testing of software application. Security testing is critical to identify and
address vulnerabilities before deployment.

26
2.4.1 Software Testing Strategies

Automated testing – Automated tests are important for ensuring software quality
and efficiency. They help in executing repetitive tasks and identifying defects early in
the development cycle.

Figure 10 – Automation Testing Process. (Sugiantoro, B. et al., 2020)

Manual testing – despite rise of automation testing, manual testing remains

important for exploratory testing, usability testing and adhoc testing scenarios.

Test Driven Development (TDD) – Test driven development involves writing tests
before the actual code ensuring that the software meets its requirements from the
outset.

2.4.2 Challenges in Software Testing and Quality Assurance

Software testing and quality assurance are critical components of Software

development lifecycle. Common challenges in software testing phase includes
managing test environments, ensuring proper test coverage and automated testing
processes. Strategies to address these challenges involve using robust software
testing tools, adopting test driven development (TDD) and integrating QA Processes
into the development workflow.

27
2.5 Project Management and Delivery Strategies

Delivering software to a large fortune global 100 client requires rigorous project
management frameworks. Traditional Frameworks like Project management body of
knowledge (PMBOK) provides structured approach to manage large complex projects
(PMI, 2017). However agile project management techniques like scrum and kanban
have gained popularity in recent times due to their flexibility and ability to deliver
incremental value to the Clients (Moyo, S. and Mnkandla, E., 2020).

Delivery strategies like CI/CD, (Continuous integration and Continuous Deployment)

are frequently employed for large clients. Studies (Sarpiri, M.N. and Gandomani, T.J.,
2021) shows that these strategies minimize deployment risks and improve delivery
efficiency. Large clients often require high amount of customization and integration
and strict adherence to timelines and quality standards. Delivery frameworks like ITIL
(Information technology infrastructure library) are also employed for large enterprise
clients to ensure proper alignment and goals with Client service management
practices (Axelos, 2019).

Figure 11 – Delivery Process followed by an IT Company (Tuape, M. et al., 2021).

28
2.6 Communication and Project Management

Effective communication is necessary for managing expectations and ensuring project

success.
Regular meetings – Regular status meetings with client team keeps everyone
informed about progress of work and facilitates issue resolution.

Clear documentation – Maintaining clear and uptodate project documentation

promotes transparency and knowledge sharing.

Project management tools – utilizing project management tools helps track progress,
manage resources and identify potential roadblocks.

2.7 Challenges in delivering software to Large Fortune Global 100 Clients.

Large Clients present unique challenges in software development and software

testing process. This literature reveals several key factors that impact success of such
projects like -

Communication complexity – Large clients have complex internal structures making

communication a challenge. Studies by (Shameem, M. et al., 2023) emphasizes the
need for structured communication channels and more frequent stakeholder
meetings.

Figure 12 – Stakeholder Management and Communication Flow. (Kristanto, E.B. et

al.,2020)

29
Risk Management – According to (Chiang, H.Y. and Lin, B.M., 2020), the risk
associated with large projects can be significant. Risks such as scope creep, resource
constraints and technological challenges must be proactively managed.

Figure 13 – Risk management Process. (Prakash, M., 2024).

Customization and integration – Fortune global 100 clients require highly customized
solutions that integrate with their legacy systems (Sandeep, R.C. et al., 2022). This
literature highlights the need for robust integration strategies and challenges to
manage the system compatibility.

Scalability – ensuring that software can handle increased loads of users efficiently is
a major challenge.

Security – Protecting the software from vulnerabilities and ensuring data privacy is
essential.

Collaboration – Effective communication and collaboration among teams is essential

for successful software development and delivery.

2.8 Conclusion to Literature Review

The literature review has provided comprehensive overview of key strategies and
frameworks relevant to developing, testing and delivering software for large fortune
global 100 clients. These strategies range from adaptive development methodologies
like agile and Devops to robust software testing frameworks and project
management approaches. Challenges such as communication complexity, risk
management and system integration has been identified as crucial factors influencing
the success of large-scale IT projects. This review also highlights the evolving nature
of software delivery practices with increasing emphases on automation, continuous
integration and agile frameworks.
30
This review gives a strong foundation for subsequent research methodology, analysis
and providing background for strategies and challenges associated with delivering
large IT Projects.

This literature review has examined key strategies, methodologies and technologies
employed by IT Companies to develop test and deliver software to its large fortune
global 100 client. While extensive research exists on individual aspects of software
development and delivery, there is a need of more integrated studies that consider
challenges and requirements for fortune global 100 clients. This thesis aims to
address this gap by providing a comprehensive analysis of effective strategies that IT
companies can employ to meet the complex need of these large enterprises.

This literature review highlights various strategies and practices that IT companies
adopt to develop, test and deliver software. It identifies the challenges faced and
best practices that can be followed to overcome these challenges. This review sets
the stage for subsequent chapters which will delve into research methodology,
analysis and implementation of these strategies in real world context.

31
 Chapter 3 – Research Methodology

3.1 Introduction to Research Methodology

This research methodology chapter outlines the process used to collect and analyse
data for my thesis topic “Strategies of an IT Company to develop, test and deliver
software for its large fortune global 100 client”. This chapter provides a roadmap for
conducting research, justifying chosen methods and explaining how data will be
analysed to answer the research question.

This chapters outlines the research methodology that will be used to investigate the
strategies of an IT Company to develop test and deliver software for its large fortune
global 100 client. The research methodology covers the overall approach, data
collection methods, analysis techniques and reason for selecting specific
methodologies to achieve research objectives.

This study employs a quantitative research approach to investigate strategies used by

IT Company for developing, testing and delivering software for large fortune global
100 client. Data was collected using surveys with project managers, software
developers and software testers involved in software development process. Surveys
were conducted over 2 months and covered topics such as SDLC Model used,
software testing strategies employed, software delivery process followed and
challenges faced during the software development project.

According to research methodologies guidelines research paper (Snyder, H., 2019.),

Quantitative Research Methodology with Percentage Analysis for Primary Research
Collected Data is most appropriate research methodology for research for this thesis
“Strategies of an IT Company to develop, test and deliver software for its large
fortune global 100 client”.

In addition to surveys, project documentation including requirement specifications,

design documents, test plans and project reports were reviewed to gather further
insights into company’s software development and testing strategies.

This study uses a percentage analysis approach to explore strategies adopted by IT

Company to develop, test and deliver software for a large fortune global 100 client.
Data is collected through surveys and document analysis. The IT company’s software
development process, software testing technique and software delivery models will
be analyzed to identify the strategies used to meet client’s requirements. Our
research design involves quantitative analysis of project data.

32
The research methodology chapter outlines the research methodology employed to
investigate the strategies employed by IT Companies to develop, test and deliver
software for their large fortune global 100 clients. The methodology includes usage
of quantitative research technique designed to provide comprehensive
understanding of the subject matter.

This chapter outlines the research methodology employed to investigate the

strategies of IT Companies to develop, test and deliver software to their large fortune
global 100 clients. It describes the research design, data collection methods, data
analysis techniques and ethics considerations that guide this study.

3.2 Research Design

The research design is structured as a quantitative case study approach focusing on

specific IT Company’s strategies for developing, testing and delivering software for its
large fortune global 100 client. The rationale for using quantitative approach is to
explore in-depth insights into how these strategies are applicable in real-world
projects, highlighting unique challenges and best practices when working with these
large clients.

This case study method allows examination of complex phenomena in real-life

scenario enabling analysis of processes, decision making and challenges in delivering
software for large fortune global 100 clients. The case study will involve both primary
data through surveys with key stakeholders as well as secondary data from company
reports, project documentation and academic literature).

This research employs quantitative approach focusing on understanding key

strategies adopted by IT Company through in-depth analysis and exploring the
existing literature, case studies and expert surveys. This approach allows a
comprehensive understanding of complexities in software development for large
clients helping in strategy formulation and implementation for delivery of software to
this large fortune global 100 enterprise clients.

This study adopts a quantitative research design approach focusing on case study
approach to gain in-depth understanding of strategies used by IT company to develop
test and deliver software for its large fortune global 100 client. The case study
method also allows for a comprehensive analysis of the context and practices
involved in an IT Project.

33
This research will adopt a case study approach to examine specific IT Companies that
have successfully delivered software projects to large fortune global 100 clients. This
approach allows an in-depth exploration of strategies, processes and challenges
involved in these projects.

Multiple case studies will be conducted to enhance the generalizability of findings

and identify any patterns or variations in strategies employed by different IT
Companies to deliver software.

Quantitative approach will be used to ensure understanding of research problem.

The study will reply on quantitative data collected from surveys with key project
managers, software engineers, client representatives and quantitative analysis will be
performed to measure project’s success against pre-defined success metrics like on
time delivery, budget adherence and client satisfaction.

Quantitative data like project timelines, budgets, defect rates, and other key
performance indicators will be analysed to measure the effectiveness of the
strategies employed by IT Companies to deliver software to its large enterprise
clients.

3.3 Data Collection Methods

3.3.1 Primary Data Collection

Surveys – The primary method of data collection will be surveys with relevant
stakeholders including -

Project managers – to understand the strategic and operational decisions involved in

the project.

Software developers and software testers – to gain insights into software

development methodologies and software testing methodologies used.

Client representatives – To understand the Client’s expectations, requirements

management, how was communication handled between client and the IT Company.

Questions in the survey will focus on key areas of project management,

communication, software testing practices, software delivery and post-delivery
support. Survey will be administered to a broader sample of IT Professionals to
gather quantitative data on the prevalence of different strategies and practices in the

34
IT Industry. Online questionnaire surveys are distributed to employees involved in
software development process for large client projects to gather quantitative data on
their experiences and perceptions.

Sample Questions -

What key factors do you consider when developing strategies for software
development for large clients?

What software development methodologies does your company employ for large
clients?

How do you determine which methodology to use for a specific project?

What are the key components of your testing strategy for large-scale software
projects?

What tools and technologies do you use for software testing?

What are the main challenges you face during the software delivery phase?

Sampling technique -

According to Research Methodology Guidelines suggested by (Habib, M. et al., 2014),

Purposive sampling is best suited for this thesis and will be employed to select
participants who are directly involved in software development and delivery process,
ensuring data collected is highly relevant and insightful. A sample size of 75
participant is anticipated for in-depth surveys. Purposive sampling is used to select IT
Companies that have a proven track record of successfully delivering software
projects to large fortune global 100 clients. The selection criteria was based on
factors like company size, industry experience and complexity of projects the
companies have previously handled. A purposive sampling method was used to select
participants who have relevant experience and knowledge about the strategies
employed by IT Company to develop test and deliver software to their clients.
Purposive sampling was used to select participants with relevant experience,
expertise and direct involvement or experience with the project. This approach
ensured data collected is relevant and provided valuable insights into strategies
employed.

Sample Size – the sample size includes 75 participants, 75 survey respondents and

35
observation of numerous project teams.

3.3.2 Secondary Data Collection -

Secondary Data will be gathered from -

Company Reports – Internal project reports, relevant documents, performance

reviews will be analysed to understand success metrics of the project and challenges
faced during the project.

Project documentation – Documentations such as requirement specification

documents, test plans, and delivery schedules will be reviewed. Relevant documents
such as project plans, requirement specifications, test cases and post project
evaluations will be analysed to gather additional insights into strategies and practices
employed by IT Companies. Review Project documentation, minutes of meetings ,
reports to understand the processes and decisions made during the project.

Industry Case Studies – Existing literature and case studies on software development
for large clients will provide some additional context.

3.4 Data Analysis Methods

Quantitative Data Analysis -

Quantitative data ( eg – project timelines, budget adherence, defect rates) will be

analysed using basic statistical techniques to measure the success of software
development strategies.

For example -

On-time delivery – percentage of project milestones delivered on time.

Budget adherence – Comparison of actual project costs to the initial budget.

Quality metrices – analysis of defect rates, severity of issues found in software

testing and post release defects.

The results of this analysis will help quantify the effectiveness of strategies employed
in the project.

36
Percentage Analysis will be used to analyse the data in Analysis Chapter according to
research guidelines by (Snyder, H., 2019). Percentage Analysis is best suited for
conducting research for this thesis from data collected from primary research
method. Percentage of data which will be collected from the respondents will be
analysed in the Analysis and Implementation Chapter.

3.5 Research Validity and Reliability

3.5.1 Validity

Internal Validity – The credibility of research will be ensured through triangulation –

using multiple data sources (interviews, reports, project documentation) to confirm
the findings.

External Validity – While the research is based on case study approach, the findings
may be generalized to other IT companies working with large fortune global 100
clients especially those facing similar challenges in developing, testing and delivering
software to large enterprises.

3.5.2 Reliability

Reliability will be ensured by maintain consistency in data collection process through

use of surveys. A survey guide will be developed and followed to ensure similar
questions are asked to different participants. Also, all quantitative data will be
collected from verified project records to ensure accuracy.

3.6 Ethical Considerations

Ethical considerations will be integral part of research methodology. Participants will

be provided an informed consent form detailing the purpose of study, their role and
confidentiality of their responses. All data will be anonymous to project the identity
of participants and ensure compliance with ethical guidelines. Sensitive company
information if gathered will be treated with strict confidentiality and will not be
disclosed without explicit consent from the company. Ethical considerations were
important throughout the research process. Informed consent was obtained from all
the survey participants ensuring they understood the purpose of research and their
right to withdraw at any time. Confidentiality was maintained by anonymizing the
participant data and securely storing all the research materials.

37
Ethical Consideration -

Informed Consent – Participants will be informed about the purpose of research,

potential risks and benefits and their right to withdraw from the study at any time.
Participants are informed about the purpose of study and their consent is obtained
before the data collection process using survey questionnaire forms.

Confidentiality – The confidentiality of participant’s responses will be maintained

throughout the research process. Confidentiality of participants will be maintained by
anonymizing their responses and securely storing the data.

3.7 Limitations of the Research

The research will have several limitations that must be acknowledged -

Scope of Case study – The case study focuses on an IT company working for a large
fortune global 100 client which may limit the generalizability of the findings.

Sample size – The quantitative nature of research with relatively small sample size for
surveys may not capture all potential perspectives. The relatively small sample size
may limit the generalizability of the findings.

Time constraints – The data collection is limited by availability of key project

stakeholders, which may restrict depth of some surveys. The study is conducted
within a limited timeframe, which may affect the depth of the analysis.

3.8 Conclusion to Research Methodology

This chapter outlines the research methodology which describes quantitative analysis
of project data. The research is designed to ensure validity, reliability and ethical
rigor with an aim to provide meaningful insights into best practices and challenges
involved in large software development projects.

This chapter outlines the research methodology that will be used to investigate the
strategies employed by IT companies to develop, test and deliver software for large
fortune global 100 clients. The quantitative research technique will provide
comprehensive understanding of the subject matter.

This chapter has presented a comprehensive research methodology designed to

investigate the strategies employed by IT Companies to develop, test and deliver

38
software for their fortune global 100 clients. The quantitative approach combining
case studies and interviews will provide rich multi-faceted data to address the
research question. By adhering to rigorous data collection and analysis procedure
while maintaining ethical standards this study aims to contribute to valuable insights
to both academic understanding and industry practices in largescale IT Project
management.

This chapter outlines the research methodology employed to investigate the

strategies of an IT company to develop, test and deliver software for large fortune
global 100 client. The quantitative method approach ensures comprehensive
understanding of research topic.

This research methodology chapter has outlined the research methodology used to
investigate the strategies of an IT Company to develop, test and deliver software for a
large fortune global 100 client. The quantitative approach, data collection methods,
sampling techniques, data analysis procedures, ethical considerations and limitations
of the study has been discussed in details. The next chapter will present the analysis
and implementation of the research findings.

39
 Chapter 4 – Analysis and Implementation

4.1 Introduction to analysis and implementation

The analysis and implementation chapter provides detailed examination of strategies

used by IT Company to develop, test and deliver software for its fortune global 100
client. This chapter presents analysis of data collected, focusing on how the strategies
have been implemented in practice and its effectiveness. The findings will be
connected to research objectives offering insights into real word application of
methodologies discussed in previous chapters.

This chapter presents analysis of data collected through research methodology

outlined in chapter 3. The analysis focuses on identifying key strategies employed by
IT Companies to develop, test and deliver software to large fortune global 100 clients.

This chapter presents analysis of data collected through research methodology. It

also describes the implementation of strategies identified through this analysis. This
chapter is structured to address the research questions and research objectives
stated in the first chapter.

This chapter presents analysis and implementation of research findings, focusing on

strategies employed by IT Companies to develop, test and deliver software to large
fortune global 100 clients.

4.2 Analysis of Software Development Strategies

4.2.1 Agile and Hybrid methodologies

The case study revealed that a hybrid agile-waterfall methodology was used in
development phase of software. The IT company employed traditional waterfall
approach for early-stage activities like requirement gathering, architectural design
while adopting agile practices in development and testing phases.

Requirement stability – In early stages, requirements were well defined in details

common in large projects with fortune global 100 clients. This ensured that the
foundation of software was clear and well documented.

Agile sprints – once the foundational requirements were established, the project
shifted to agile sprints. Each sprint focused on delivering incremental features and
improvements allowing the project to remain flexible and responsive to changing

40
client needs.

Challenges – One of the challenges identified was managing transition between

waterfall and agile methodologies. While the initial documentation was very
comprehensive, changes during agile phases led to rework in earlier stages like
design stage.

Agile methodology mainly emphasizes iterative development allowing teams to adapt

to changes quickly and deliver incremental value.
key practices within agile include -

Sprints – short iterations that focus on delivering specific features

Daily stand-up meetings – regular meetings to discuss progress, challenges and next
steps.

User feedback – continuous engagement with stakeholders to refine requirements

and improve the product.

Agile’s flexibility makes it suitable for projects where requirements will evolve as
often with the case with large fortune global 100 clients who operate in changing
evolving markets.

The IT Company implements agile practices like daily standup meetings, sprint
planning and retrospectives to enhance flexibility and responsiveness. Agile practices
are employed to manage development process, with regular iterations and
continuous feedback.

4.2.2 Devops Practices

Devops was another critical component of the implementation strategy. The IT

Company integrates continuous integration (CI) and continuous delivery (CD)
pipelines to streamline their development to delivery process.

Automation – Automation testing, build automations and deployment automation

ensured rapid delivery of code changes. It reduced manual efforts and minimized
errors. Implementation of automation testing framework ensured code quality and
reduced time spent on manual testing.

41
CI/CD Pipelines – The use of CI/CD Pipelines allowed the team to deploy new
updates to the client quickly improving the overall time to market. Automating the
integration and deployment process enhanced efficiency and reduced errors.

Impact - These practices significantly improved delivery timeline with project

meeting 90% of its sprint deadlines. The adoption of Devops also enhanced
collaboration between development and operations team which was particularly
important given the large scale of the project. The integration of development and
operations team through Devops Practices improved collaboration and accelerated
the delivery process.

4.2.3 Waterfall Methodology

The waterfall methodology follows linear and sequential approach where each phase
has to be completed before moving to the next. This model is beneficial for projects
with well-defined requirements and minimal expected changes to the requirements.

This phase includes -

Requirement gathering – Detailed documentation of client needs.

Design – Creating architectural design specifications.

Implementation – Actual coding based on design documents.

testing – Verifying the software meets the specified requirements.

Maintenance – ongoing support and updates post deployment.

While waterfall model offers clarity and structure, it may be less adaptable to
changes, which can be a limitation in this fast-paced environments.

4.2.4 Lean Development

Lean development focuses on maximizing value while minimizing waste. This

approach encourages teams to streamline processes and eliminate non value adding
activities.

Key principles of Lean development include -

42
Value stream mapping – Identifying and optimising the flow of information and
materials.

Continuous improvement – Regularly assessing processes and implementing

improvements.

Empowered teams – Encouraging team members to take ownership of their work

and make decisions.

4.2.5 Development Phase – Tools, Framework and Practices Used

The development phase involves use of various tools and frameworks to streamline
the processes. Key tools include -

Version Control System – For managing source code changes and collaboration. Eg-
Git. Utilizing version control systems to manage code changes and facilitate
collaboration among developers.

Integrated development environments (IDEs) – for efficient coding and debugging.

Project Management Tools – For tracking progress and managing tasks (eg – Jira,
TFS).

4.3 Analysis of Software Testing Strategies

4.3.1 Automated Testing -

The project utilized a test automation framework for both functional and
nonfunctional testing. Automated testing was conducted using tools like selenium for
UI Testing and Junit for Unit Testing.

Functional automated testing – the automated tests ensured that all functionalities
worked as expected across multiple environments. A test-driven development (TDD)
approach was applied in early stages to ensure code quality.

Nonfunctional Automated Testing – Performance and security testing were

automated using tools like Jmeter for load testing and OWASP ZAP for security testing
respectively.

Automation testing tools were used to execute repetitive tests, ensuring consistency

43
and efficiency.

4.3.2 Manual Testing and User Accepting Testing (UAT)

Despite heavy usage of automation testing, manual testing was also critical especially
for user acceptance testing. Manual testers simulated real world user scenarios to
ensure the software met client expectations.

Challenges – A Key challenge was ensuring the manual testing kept pace with rapid
iterations brought by agile and Devops. Manual testing cycle were carefully planned
to avoid bottlenecks, with certain UAT phases running in parallel with ongoing
software development.

Manual testing was conducted by QA Teams to identify edge cases and usability
issues.

4.3.3 More Testing Strategies

a. Continuous Testing - Continuous testing was implemented to provide immediate

feedback on code changes, reducing the risk of defects. Continuous testing was also
integrated into CI/CD pipeline to catch issues early and ensure quick feedback.

a. Unit testing – developers perform unit tests on individual components of modules

to ensure they function as expected.

b. Integration testing – the company conducted integration testing to verify that

different components of software work together seamlessly.

c. End to End testing – the company performed end to end testing to simulate real
world scenarios and ensure that the software met client’s requirements.

d. Performance Testing – the company conducted performance tests to ensure that

the software handled the expected load and respond within acceptable timeframes.

44
4.3.4 Defect Management

A comprehensive defect process was stablished using Jira to track, prioritize and
resolve defects.

Analysis of defect rates – defect rates were higher in the earlier sprints, as the
project team were still adapting to hybrid methodology. However, defect rates
decreased over time, as the teams became more proficient with automated testing
and better aligned with Client’s Expectations.

Figure 14 – Software Testing Lifecycle (Mendoza, M.D. et al., 2020)

4.4 Software Delivery Strategies

4.4.1 Basic Delivery Strategies

Continuous Integration/ Continuous Delivery (CI/CD) Pipeline – CI/CD Pipelines are

established to automate the integration and deployment processes enabling faster
and more reliable releases. CI/CD pipelines automate the build, test and deployment
processes to ensure rapid and reliable delivery.

Microservices architecture – the adoption of microservices architecture allows for

independent development, testing and deployment of software components
enhancing scalability and maintainability.

Containerization - Used to create consistent deployment environments and reduce

compatibility issues. Eg – Docker.

45
Post Deployment Support – Includes monitoring, logging and incident management
to ensure software’s smooth operations.

4.4.2 Stakeholder Communication and Collaboration

Communication with fortune global 100 client was facilitated through regular
meetings, sprint reviews and project dashboards that provided real time project
updates.

Key strategies – The company implemented daily standups, bi weekly sprint reviews,
and monthly committee meetings to engage stakeholders at all levels.

Success Factors – These practices ensured that the client was regularly informed and
engaged which reduced misunderstandings and helped the team to align with
software development process with client’s changing requirements.

4.4.3 Delivery and Deployment

The delivery phase utilized phased delivery strategy. The project was broken into
small deliverables that were provided to client in phases each representing a
functional subset of overall project.

Staged releases – the software was delivered in three stages -

Stage 1 – Core functionality.

Stage 2 – additional features based on client’s feedback.

Stage 3 – final deployment and integration with legacy system.

Challenges – One of the challenges was integration of newly developed software with
client’s existing legacy systems. This required a detailed analysis and careful
coordination between IT company and client’s internal teams.

4.5 Analysis of Key Metrics

The project was measured against several key performance metrices including on
time delivery, budget adherence, defect rates and client satisfaction.

46
4.5.1 On time Delivery

The analysis revealed that 90% of sprint deadlines were met, and overall project was
delivered on time.

the use of agile methodology allowed teams to remain flexible and making
adjustments without significantly impacting the overall delivery timeline.

4.5.2 Budget Adherence

The project stayed within 5% of the initial budget, largely due to effective resource
management and use of automation tools, which reduced the need of additional
manual labour in software testing and software deployment phases.

4.5.3 Defect Rates

The initial sprints saw higher defect rates particularly in integration phase where
discrepancies between client requirements and implementation were identified.

By the final phase of the project, defect rates dropped by 60% indicating success of
testing strategies and continuous feedback loops.

4.5.4 Client Satisfaction

Client satisfaction was measured through surveys and feedback meetings.

The client rated the overall satisfaction to 8.5/10 indicating high approval of
software’s performance, quality and project team’s responsiveness to changes.

4.6 Challenges Faced and Lessons Learned

Throughout the analysis, several challenges were identified in software development

process for large clients like -

1. Requirement changes – The large client frequently changed requirements,

necessitating flexibility in the project plan of the project.

2. Integration issues – Integration with legacy system was more challenging than
anticipated resulting in delays during specific phases.

47
3. Scope creep – Uncontrolled changes in the project scope can lead to delays and
increased costs. To mitigate this, clear boundaries and change management
processes were established.

4. Communication gaps – Miscommunication among stakeholders can hinder project

progress. Regular updates and collaborative tools can enhance communication and
alignment. The company uses various communication channels like email, instant
messaging, video conferencing to keep stakeholders informed and engaged
throughout the project.

5. Quality Assurance – Ensuring High quality software requires rigorous testing and
validation. Implementing CI/CD Practices and automated testing significantly
improved quality control. Ensuring the software meets the client’s quality standards
and expectations. The company implemented rigorous quality assurance processes
like code reviews, test planning, defect tracking to ensure that the software met the
client’s quality standards.

6. Stake holder management – managing the expectations and requirements of

multiple stakeholders including client, end users and internal teams.

7. Risk Mitigation - identify and mitigating potential risks such as technical issues,
resource constraints and requirement changes. The company conducted regular risk
assessment and developed contingency plans to mitigate potential risks.

Figure 15 – Risk Assessment Matrix. (Dąbrowski, J. et al., 2022).

48
4.7 Data Analysis and Data Presentation

Quantitative Analysis -

The data collected from surveys, case studies and project documents are analyzed for
quantitative analysis and percentage analysis.

Data Presentation of Survey Results -

Percentage Analysis - A told of 75 Respondents Responded to my Survey. All The 75

Respondents were employees of IT Companies in India and were based out of IT
Companies in India. The majority of respondents reported that agile practices
significantly improve project outcomes. Additionally, majority indicated that
automated testing reduces time required for testing.

Figure 16 – Gender of Survey Respondents -

Out of 75 respondents of my survey from IT Companies who responded to my survey,

52 % of them were males and 48% of them were females.

49
Figure 17 – Experience in IT Industry.

Out of 75 respondents, 25.3% of them had more than 10 years of work experience
and 25.3% of them had 1 to 3 years of work experience working in IT Company.

Figure 18 – Size of IT Company.

Out of total of 75 respondents, 64% of them worked with large IT Organisations
having 250+ employees in their company. 21.3 % of them worked with medium sized
organisation and 14.7% of the employees worked with small companies.

50
Figure 19 – Number of Fortune global 100 Clients, the IT Companies Serve.

Majority (56%) of the IT Companies the survey respondents work with served more
than 20 Fortune Global 100 Clients.

Figure 20 – Key factors while developing strategies for software development for
large clients.

Out of 75 respondents, maximum number of respondents (73.3%) considered budget

constraints to be a key factor while developing software for large clients. 64 %
believed technology advancement is key factor while developing strategies for
software development for large clients.

51
Figure 21 – Software development methodology employed by the IT Company.

57.3% of the IT Companies employ kanban software development methodology to

develop software for large clients. 53.3% used scrum as their software development
methodology. This agile methodology played a dominant role in software
development methodology in development of software in these IT Companies.

Figure 22 – Factor for determining methodology to be used for the project.

29.3 % of the 75 respondents said that software development methodology is chosen

based on client preference and other 29.3% of 75 respondents said that software
development methodology is based on team expertise.

52
Figure 23 – Key Components in testing strategies for software projects.

46.7% of the 75 respondents said that performance testing is important for their
software project and 46.7% of the respondents said that User acceptance testing is
important component of their software project.

Figure 24 – Tools used for software testing.

62.7% of the 75 respondents said that they use load runner automation testing tool
for performance testing of their software. 57.3% said they used QTP/UFT and 56%
said they used TestNG Automation testing tool for software testing.

53
Figure 25 – Challenges faced in software delivery.

82.7% of the 75 respondents of the IT Companies said that managing dependencies

was a major challenge in software delivery while 78.7% of the respondents said that
ensuring quality was the major challenge they faced in delivery of software to the
client.

Figure 26 – Strategies to ensure smooth transition from development to production.

Out of a total of 75 respondents, majority 30.7% of the respondents said that

detailed deployment plan was the main strategy employed to ensure a smooth
transition of the software from development environment to the production
environment.

54
Figure 27 – Managing Project Timelines for timely delivery of software.

A majority (30.7%) of the 75 respondents said that regular progress meeting was
used to manage project timelines to ensure timely delivery of projects. 28.7% of the
respondents said that agile sprints was used to manage project timelines to ensure
timely delivery of the software project.

4.8. Conclusion to Analysis and Implementation phase

The analysis and implementation of software development strategies for a large

fortune global 100 client highlights the importance of selecting appropriate
methodologies through planning and effective execution. By understanding unique
challenges and leveraging best practices, IT Companies can enhance their ability to
deliver high quality software solutions that meet client expectations and drive
business success. The findings from this chapter will inform the results and discussion
in the subsequent chapter providing insights into effectiveness of strategies
employed.

The analysis and implementation chapter analyses and implements the research
findings, providing valuable insights into software development, testing and delivery
strategies for large fortune global 100 clients. The proposed implementation
framework and case studies demonstrate practical applications of the research.

The analysis of developing, testing and delivery strategies used by IT company reveals
that combination of agile methodologies, automation testing and Devops practices
led to successful execution of project. Key success factors include use of hybrid
methodologies, effective stake holder management and continuous integration.
Despite the challenges of changing requirements and legacy system integration, the

55
project met its objectives of on time delivery, budget adherence and client
satisfaction.

This chapter provided a comprehensive analysis of project’s implementation

demonstrating how theory and strategy were applied in a real-world context. The
findings will inform the results and discussion presented in the next chapter.

This chapter has presented analysis of data collected and implementation of the
strategies identified in literature review. The findings demonstrate the effectiveness
of agile practices, automated testing and CI/CD pipelines in developing, testing and
delivering software for large fortune global 100 client. The next chapter will discuss
the results and provide recommendations based on the analysis.

56
 Chapter 5 – Results and Discussions

5.1 Introduction to Results and Discussions

This chapter focuses on presenting the key findings and outcomes of the research on
the strategies of an IT company to develop, test and deliver software for a large
fortune global 100 client. The findings will be discussed in context of research
objectives, offering insights into effectiveness of strategies and highlighting areas of
success and challenges that arose during this process.

The results of this study will provide an in-depth understanding of how the IT
company managed the complexities of software development, software testing and
delivery of software to its large fortune global 100 client. The data collected from
surveys, project documentations and metrics were analysed to assess the success of
implemented strategies and their alignment to the client’s requirements. This
chapter also discusses implications of the findings, the challenges encountered and
how these results can inform best practices in similar projects.

This chapter presents findings of research, drawing on the analysis conducted in the
chapter 4. The results are discussed in relation to existing literature and the research
questions posed at the outset of this study.

This chapter presents a comprehensive discussion of the results obtained from

analysis conducted in chapter 4. It interprets these findings in context of research
question and objectives outlined in chapter 1 and relate them to existing literature
reviewed in chapter 2. This chapter aims to provide insights into effective strategies
for IT companies to develop test and deliver software to fortune global 100 clients.

This chapter presents results of the study, followed by a discussion of findings,

implications and contributions to existing body of knowledge.

5.2 Quantitative Results

Survey Findings – The survey results indicated that 75% of the respondents believe
agile practices significantly improve the project outcomes. Additionally, 80% of the
respondents reported that automated testing reduces time required for testing.

The high percentage of respondents who believe in the effectiveness of agile

practices and automated testing supports the quantitative findings. This indicates a
strong consensus among participants regarding benefits of these strategies.

57
5.3 Key Findings

The Aim and Objectives of this thesis according to Section 1.4 mentioned in chapter
1 is as follows -

The aim of this study is to analyse and identify the strategies that IT Companies use
to develop, test and deliver software for Large Fortune Global 100 Clients.

Objectives of this study includes -

1. To examine the common challenges faced during software development lifecycle

for large clients.

2. To identify the best strategies and practices that contribute to successful delivery
of IT Software projects.

3. To evaluate the impact of these strategies on project outcomes including timelines,

budget adherence and client satisfaction.

4. To provide recommendations to IT Companies to improve their software

development processes for large clients.

The Key Findings from this research fulfilling and satisfying the Objectives of this
Study after this research is conducted is as follows -

5.3.1 Strategy Effectiveness in Software Development.

The study revealed that use of hybrid agile-waterfall methodology was a key factor
for project’s success. The structured approach of waterfall model during initial stages
combined with flexibility of agile model in later stages allowed for a clear well
documented foundation enabling the team to respond to changing requirements.

Finding 1 – The project team achieved high degree of flexibility and adaptability
which was essential in meeting the evolving need of the client. The hybrid approach
resulted in improvement in time-to-market without sacrificing on the quality of the
software.

Finding 2 – The team faced challenges in transitioning between the 2 methodologies,

particularly during design and test phases. This resulted in rework during agile phases
which delayed certain sprints.

58
Finding 3 – Stakeholder engagement was critical in bridging the gap between
methodologies. Regular feedback from client during sprint review helped to align the
development process with the client’s expectations.

Discussion – These findings fulfilled the objectives of this thesis mentioned in

Chapter 1 Introduction. The hybrid agile-waterfall strategy proved effective in
balancing structure with flexibility. However, it is crucial to better manage the
transition point between the 2 methodologies to prevent delays. The success of the
strategy also depended on strong communication and feedback loops established
with the client supported by previous literature (Gupta, V. et al., 2020).

5.3.2 Strategy effectiveness in software testing.

The testing strategy adopted by IT Company was highly effective in ensuring that the
software met both functional and non-functional requirements. The combination of
automation testing for functional validation and manual testing for user acceptance
testing (UAT) provided comprehensive coverage.

Finding 1 – Automation testing was responsible for reducing manual errors and
increasing software testing efficiency. The test-driven development (TDD) approach
ensured that the code quality remained high throughout the software development
process and use of automated testing tools like selenium and Junit reduced defects
by 40% in early stages.

Finding 2 – Despite the reliance on automation, manual testing remained essential

especially during the User acceptance testing (UAT). The manual testers played a key
role in identifying issues that automation testing tools could not detect especially in
user experience testing and testing of business logics.

Finding 3 – the defect rates in early sprints were high but decreased significantly as
the project progressed. By the final phases, the defect rates were reduced by 60%
indicating that iterative testing approach was successful.

Discussion – These findings fulfilled the objectives of this thesis mentioned in

Chapter 1 Introduction. The blend of automation testing and manual testing allowed
for a robust validation process, ensuring high quality software. While automation
testing reduced number of defects and increased efficiency, manual testing during
UAT was critical in identifying more different issues supported by previous literature
(Garousi, V. et al.,2020). The TDD approach helped ensure that testing was crucial in
the development cycle although initial high defect rates suggested the need for

59
better planning in early sprints.

5.3.3 Efficiency of Devops and Continuous Integration/Continuous Delivery (CI/CD).

The adoption of Devops practices including CI/CD Pipelines played an important role
in streamlining the software delivery process.

Finding 1 – The implementation of CI/CD pipelines enabled faster and more reliable
deployments, with the team able to deploy updates at end of each sprint. This
significantly improved delivery speed and reduced risks associated with large scale
releases.

Finding 2 – Automation of deployment processes was critical in ensuring that

deployments were consistent and error free. The use of automation reduces the time
spent on deployment by 50%, enabling the team to focus more on software
development and software testing.

Finding 3 – One of the key challenges was integration with the legacy system within
the client’s IT Infrastructure. This required significant customization in the CI/CD
Pipeline and introduced delays in deployment.

Discussion – These findings fulfilled the objectives of this thesis mentioned in

Chapter 1 Introduction. The use of Devops practices and CI/CD pipeline significantly
improved the project’s delivery efficiency and allowed for quicker response times to
changes supported by previous literature (Edison, H. et al.,2021). However,
integrating these modern practices with client’s legacy systems presented challenges,
indicating the need for better planning in environment with diverse IT landscapes.

5.4 Summary of Key Findings

The research identified several critical strategies that IT companies utilize when
working with large fortune global 100 clients enterprises. These strategies cover all
aspects of software development, testing and delivery process.

The Key findings include -

Adoption of Agile methodologies – A Significant number of IT Companies use agile

methodologies to enhance flexibility and responsiveness to their Client needs. Agile
practices like iterative development, regular feedback loops and cross functional
team were highlighted as essential for meeting the requirements of the large

60
enterprises fortune global 100 clients.

Emphasis on Automation – Automating testing and automation deployment

processes were frequently used as a means to increase efficiency and reduce time to
market. Tools for continuous integration and continuous deployment were noted for
their role in streamlining the workflows.

Focus on Quality Assurance - The importance of rigorous software testing and quality
assurance processes was considered. Companies emphasize the need of
comprehensive software testing strategies like unit testing, integration testing and
user acceptance testing (UAT) to ensure delivery of a high-quality software.

Stakeholder Engagement – Effective communication and engagement with

stakeholders were identified as important components for successful project
execution. Regular updates and collaborative tools were used to maintain alignment
and manage the expectations.

Risk management practices – Companies employed various risk management

strategies including thorough requirement analysis and feasibility study, to anticipate
potential risks and challenges and mitigate the risks throughout the project lifecycle.

5.5 Discussion of Findings

The findings of this study align with previous research on effectiveness of hybrid
methodology in large scale software development projects. The success of the
strategies highlights the importance of flexibility, communication and use of modern
practices like Devops and automation.

Alignment with Literature – The project’s success aligns with best practices in
software development, particularly benefits of combining agile methodology with
waterfall methodology in complex projects. The result also emphasizes the use of
continuous integration and continuous testing to develop and maintain a high-quality
software. The findings of this research align with existing literature on software
development strategies. The emphasis on agile methodologies reflects a broad
industry trend towards flexibility and adaptability in software development. Studies
have shown that agile practices enhance collaboration and improve client satisfaction
by allowing continuous feedback and iterative improvements.

The focus on automation also aligns with the current best practices in the industry.
Automation not only accelerates the development process but also minimizes human

61
error enhancing software quality. This is consistent with findings from other research
that advocate for integration of automation testing and CI/CD as important
components of modern software development.

Practical Implication – The findings suggest that IT companies working with large
fortune global 100 clients can benefit by adopting a hybrid approach with robust
testing and delivery frameworks. However more better planning for legacy system
integration, agile stakeholder management are crucial for optimising project
outcomes.

Unique Insights – While the findings support the existing literature, they also provide
unique insights in application of these strategies for large clients. For example, the
study revealed that successful stakeholder engagement not only involves
communication but also involves active collaboration and creating solution as a team.
This understanding emphasizes the need for IT Companies to have strong relationship
with Clients, which can lead to better alignment of project goals and project
outcomes.

Moreover the research highlights that while agile methodologies are widely adopted
their implementation can vary based on organisational culture and client
expectations. This suggests that IT companies must tailor their agile methodology to
fit the specific requirement for each client engagement which may not be extensive
covered in the existing literature available.

5.6 Interpretation of Key Metrices

The success of the project was evaluated based on key performance indicators (KPIs)
including on time delivery, budget adherence, defect rate and client satisfaction.

Ontime Delivery -

The project met 90% of the sprint deadlines with only minor delays caused by need
for rework during the agile iterations. This was a significant achievement given the
complexity of the project and scale of the client.

Interpretation – The use of agile methodology allowed the team to remain flexible
and combination of Devops practices ensured deadlines were met consistently. The
delays that occurred were mainly due to the challenges with integration with legacy
system which could have been mitigated with more upfront planning.

62
Budget Adherence -

The project was delivered within 5% of the initial budget, thanks to the careful
resource management and use of automation in both software testing and software
deployment.

Interpretation – The use of automation tools and Devops practices reduced the need
of extensive manual testing, which helped the project be within the budget. The
slight budget overrun was due to integration challenges which required additional
special resources.

Defect Rates -

Defect rates were initially high but decreased by 60% over the course of project
particularly after adoption of automation testing and TDD Practices.

Interpretation – The initial high defect rates were likely due to complexity of project
and need for better coordination between development and testing teams. However,
the study reduction in defects suggest that the testing strategies were effective in
improving the quality of software over time.

Client Satisfaction -

Client satisfaction was measured as 8.5/10 indicating a high level of approval for
project’s outcome. The client expressed satisfaction with software’s performance, the
team’s responsiveness to changes and quality of stakeholder engagement.

Interpretation – The client’s high satisfaction rating reflects success of strategies

employed in the project. The flexibility offered agile methodology and regular
communication with stakeholders were key factors in maintaining client satisfaction
even in times of challenges.

63
5.7 Challenges and Mitigation in the Project

The project faced several challenges during development, testing and delivery phase
of the software but most of the challenges were successfully mitigated.

1. Requirement Changes and Scope Creep -

Challenge – One of the major challenges was dealing with frequent requirement
changes from the client, which is a common issue when dealing with large enterprise
clients and large fortune global 100 clients. These changes often led to scope creep,
which impacted the project’s timelines.

Mitigation – The use of agile methodologies helped to mitigate this challenge by

breaking down the project into smaller, manageable sprints. Regular feedback loops
with the client allowed the team to adjust the requirements in real time without
causing any significant delays.

2. Communication and Coordination with Client -

Challenge – Coordinating with a large fortune global 100 client with complex
hierarchies and decision-making processes was another challenge. Delays in decision
making often impacted the pace of software development.

Mitigation – To address this, the project team implemented clear communication

channels and conducted regular sprint reviews, which kept the client engaged and
reduced delays in approvals. Dedication liaison from both IT Company and the client
was arranged to streamline the communication.

3. Integration with Legacy System -

Challenge – The integration of new software with client’s existing legacy system was
more difficult than anticipated. These systems often lack proper documentation
which increases the complexity of the integration process.

Mitigation – The IT Company brought a specialized team to work on the legacy

system integration which included experienced software developers and system
architects familiar with such environments. The team worked closely with client’s
internal IT Staff to ensure smooth integration.

5.8 Implications for Practice

64
The results of this research and findings of this study has several practical
implications for IT Companies with Large Clients.

Adoption of Agile Practices – IT companies should adopt agile methodologies to

enhance flexibility and responsiveness. Regular training and workshops can help the
teams effectively implement the agile methodology.

Investment in Automation Testing – Investing in automation testing tools and

frameworks can improve software quality and reduce software testing time. IT
Companies should prioritize the integration of automation testing to their software
development process.

Enhancing Collaboration and Communication – Implementing Collaborative Tools

and establishing clear communication channels can bring better coordination among
the team members of the IT Company. Regular meetings and feedback sessions can
enhance this collaboration.

Enhancing Training and Development – companies should invest in training their

teams on agile methodologies and automation testing tools to ensure they are
equipped to meet the requirements and demands of large-scale projects effectively.

Strengthening Stakeholder Relationships – Developing structured approach for

stakeholder engagement can lead to improved project outcomes. Companies should
consider implementing regular feedback sessions and collaborative workshops to
have a more inclusive software development process.

Adopting a holistic approach to Quality Assurance – A comprehensive quality

assurance strategy that integrates manual testing and automation testing processes
can ensure high quality software. Companies should prioritize in establishing a
culture of high quality throughout the software development lifecycle.

5.9 Policy Implication governing software development on broader domain of IT -

The Findings of this Study offers insights for revision of policies governing software
development practices and IT Practices particularly for fortune global 100 large
clients. The implications are -

1. Standardization of development frameworks – There is a need to standardize the

software development frameworks to streamline project execution across teams in

65
the IT Company. Existing policies can be update to mandate use of universally
accepted methodologies like agile and Devops for large projects. Governments or
regulatory bodies could introduce certifications or compliance measures to ensure
adoption of these frameworks for efficiency, security and quality control.

2. Enhanced Data Protection Policies – Given the sensitivity of data handled by

Fortune Global 100 Companies, this study recommends strengthening data
protection policies. This study suggests enhancing regulations surrounding data
security, privacy and cross border data transfer, under regulations like GDPR and
HIPAA which large scale companies must comply with. Client data should be securely
handled at every phase of software development.

3. Incorporation of sustainability – IT Sector’s growing carbon footprint is a major

concern. This study aims at promoting sustainable development practices like energy
efficient coding, optimizing resource usage and encourage cloud infrastructure to
sustain renewable energy. Policy frameworks can mandate sustainability audits for
software projects ensuring IT Companies actively contribute to reduce environmental
impact.

5.10 Conclusion to Results and Discussion

The analysis of project’s results shows that the strategies used by IT Company were
largely successful in meeting the client’s needs. The combination of hybrid
development methodology, automation testing and Devops practices led to improved
efficiency, quality and client satisfaction. Challenges such as scope creep and legacy
system integration were managed effectively and these areas present opportunities
for improvement in future projects.

This chapter has presented a comprehensive discussion of research findings,

interpreting them in context of existing literature and challenges faced by IT
Companies with fortune global 100 clients. The results highlight the complexity of
managing large scale IT projects and importance of tailored strategies for developing,
testing and delivery of software and client management. While limitations exist, this
study contributes valuable insights to both academic understanding and industry
practice in the field of IT project management for large enterprises.

This chapter presents results of study and discuses findings, implications and
contributions to existing body of knowledge on software development and software
testing. The study provides valuable insights into software development, testing and
delivery strategies for large fortune global 100 clients.

66
 Chapter 6 – Conclusion and Recommendations

This chapter provides a comprehensive summary of key findings from research on

strategies used by IT Company for developing, testing and delivering software to its
large fortune global 100 client. It offers recommendation based on analysis,
highlighting practical insights for future projects and organisations and companies
dealing with similar challenges.

This chapter provides a comprehensive conclusion to research on strategies

employed by IT Companies to develop, test and deliver software to large fortune
global 100 clients. It synthesizes the key findings, addresses the research questions
and discusses implication of study and offers recommendations to both IT Companies
as well as their large enterprise fortune global 100 clients.

This chapter summarizes the key findings of study, provides conclusions and offers
recommendations for IT Companies developing softwares for large fortune global 100
clients.

This chapter summarizes the key findings of research, discusses their implications and
provides recommendations to IT Companies. It highlights the contributions of study
and suggests areas for future research.

The purpose of this thesis was to examine and evaluate strategies used by an IT
Company to develop test and deliver software for its large fortune global 100 client.
This study explored the effectiveness of various software development
methodologies, software testing practices and software delivery frameworks that
contributed to successful completion of the project. Through careful analysis of
project’s outcomes, several key conclusions can be drawn -

Overall this study provides valuable insights into strategies employed by IT

Companies to develop, test and deliver software for large clients. The findings can be
used by other IT Companies to benchmark their own strategies and identify areas for
improvement. This study also highlights the importance of effectiveness of software
development and software testing strategies to ensure success of IT Projects and
meeting the needs of clients in today’s rapidly evolving digital landscape.

This study concludes that IT companies need to adopt flexible and iterative
development methodologies to meet the changing requirements of clients. The
hybrid approach combining agile and waterfall methodologies is effective in ensuring
timely delivery and quality software. IT Companies should also adopt continuous

67
testing and iterative development approaches to meet the client’s requirements. This
study recommends IT Companies to adopt flexible and iterative development
methodologies to meet changing requirements of Clients.

Conclusion and Study Objective Met -

6.1.1 Hybrid Methodologies

The use of a hybrid agile-waterfall model was pivotal to ensure the project was
delivered successfully. The initial stages of the waterfall approach provided a
structured foundation for requirement gathering and planning while agile
methodology allowed flexibility in response to changing client requirements during
the development phase and testing phase of the project.

Conclusion – The hybrid approach allowed better alignment with client’s needs and
requirements and provided the team with flexibility and structure required to
maintain quality and timeline adherence. However careful planning is required when
transitioning between the 2 methodologies to avoid rework and delays.

6.1.2 Automation and Manual Testing Synergy

Software testing played a crucial role in ensuring the quality of software. The
combination of automation testing using tools like selenium and Junit with manual
testing (especially user acceptance testing) was highly effective in identifying both
functional and usability issues.

Conclusion – Automation testing significantly reduced the manual workload and

improved the early defect detection rate in the project. Manual Testing on the other
hand was crucial in refining the user experience and catching complex business logic
issues. Together they provided comprehensive test coverage that improve the overall
quality of the software.

6.1.3 Devops and CI/CD Implementation

The Devops practices including use of CI/CD Pipelines allowed continuous integration
and delivery throughout the project. These practices contributed to faster and more
reliable software releases with minimized risk associated with large scale software
deployments.

Conclusion – The use of CI/CD pipelines significantly enhanced the delivery efficiency

68
by automation testing and deployment processes. Despite challenges in integrating
with legacy systems, Devops practices helped streamline the software delivery
process, allowing the project to meet most of its deadlines.

6.1.4 Stakeholder Engagement and Communication

Frequent and clear communication with stakeholders was a key success factor. The
project team engaged with client regularly through sprint reviews, feedback loops,
and dedicated liaisons ensuring that nay requirement changes or concerns from the
Client was addressed promptly.

Conclusion – Effective stakeholder communication and engagement were crucial in

managing the requirements changes, reducing misunderstandings, and ensuring that
the project is aligned with the Client’s Expectations. This helped mitigate the scope
creep and maintaining a clear focus throughout the entire project.

6.1.5 Challenges and Lessons Learned

The project faced several challenges including frequent requirement changes,

integration with legacy systems and managing the transition between agile
methodology and waterfall methodology. However, these challenges were mitigated
through careful planning, resource allocation and communication.

Conclusion – Challenges such as scope creep and legacy system integration need to
be anticipated and proactively managed to minimize the impact on project timelines
and costs. Agile frameworks and Devops practices offer flexibility but their successful
implementation requires careful alignment with Client’s infrastructure and system.

6.2 Summary of Findings

The researched aimed at investigating the strategies employed by an IT Company to

develop, test and deliver software for its large fortune global 100 client. The key
findings are summarized as follows -

Agile Practices – Agile methodologies such as scrum and kanban significantly

enhanced flexibility, responsiveness and client satisfaction.

Automation testing – Automation testing and Test-Driven Development (TDD) are

essential for ensuring software quality and efficiency.

69
Collaboration and Communication – Effective Collaboration and Communication
among team members is important for successful software development.

Continuous Integration / Continuous Deployment (CI/CD) – CI/CD pipeline

streamline the integration and deployment processes enabling faster and more
reliable releases.

Microservices Architecture – The adoption of microservices architecture allowed for

independent development testing and deployment of the software components
enhancing scalability and maintainability of the software being delivered to the
client.

6.3 Recommendations

Based on Findings and Conclusions from this study, following recommendations are
suggested for organisations undertaking similar large scale software development
projects for fortune global 100 clients -

6.3.1 Optimize Hybrid Methodology Transitions

While hybrid methodologies provide a balanced approach, transition between

waterfall methodology and agile methodology needs to be more seamless.
Organisation should invest time in developing well defined transition plans between
these 2 methodologies to reduce rework and minimize delays.

Recommendation – Define clear handoff points between waterfall phase and agile
phase. Use sprint retrospectives to continuously improve the transition between
these stages and ensure all team members are adequately trained in hybrid
methodologies.

6.3.2 Increase early investment in software testing automation

Automation testing proved to be an important component in success of the project

reducing defects and improving efficiency. Investing in automation testing tools and
frameworks early in the project lifecycle can help prevent defects from accumulating
in later stages.

Recommendation – IT Companies should integrate test-driven development (TDD)

and automation testing as early as possible in the software development process.
This not only improves code quality but also allows faster iterations and shorter

70
feedback loops.

6.3.3 Strengthen the CI/CD and Devops Practices

The successful implementation of Devops and CI/CD practices improves speed and
reliability of deployments. To capitalize this approach, companies should ensure that
their CI/CD pipelines are flexible to integrate with both modern as well as legacy
systems.

Recommendation – Invest in building robust CI/CD pipelines that can work in

complex environment including in legacy systems. This may require dedicated teams
to handle the legacy integration to modern system and specialised tools that can
facilitate smoother deployment processes.

6.3.4 Improve Stakeholder Management

Stakeholder engagement is key to managing client expectations especially in large

projects. IT Companies should develop a structured stakeholder management plan
that includes clear communication channels and transparent feedback systems.

Recommendation – Assign dedicated client liaisons and conduct regular sprint review
to ensure alignment between project team and stakeholders. Establish formal
communication protocols to avoid delays in decision making and approvals.

6.3.5 Anticipate and Mitigate Legacy System Integration Issues

One of the major challenges in this project was to integrate new software with
client’s legacy system. Legacy systems often introduced complexity and risks to
project timelines so it is important to plan for these challenges upfront.

Recommendation – Conduct a thorough system assessment at start of project to

identify any potential challenges with the legacy system integration. Allocate
additional resources, team and time for integration phase and testing phase when
working with legacy infrastructure.

6.3.6 Proactively Manage Project Scope Creep

Scope creep driven by frequent client requirement changes can derail the project
timelines and inflate the cost of the project. Proactive scope management practices
such as regular scope reviews and client feedbacks are essential to control the

71
changes.

Recommendation – Implement strict scope management practices including use of

change control boards and formal documentation for any scope changes. Incorporate
agile flexibility model to handle small incremental changes while ensuring large
changes in the project are evaluated against project timelines and project budgets.

6.4 Future Research Directions

This study has provided insights into strategies used by IT Companies in large scale
software development projects. However future research could further explode the
following areas to deepen the understand the best practices and challenges -

Comparative Studies on Hybrid Methodologies – Conduct Studies comparing the

effectiveness of different hybrid methodologies (Agile v/s waterfall) in various
industry sectors.

Impact of AI and machine learning on software testing – investigate how emerging

technologies like AI driven automation testing can further enhance testing efficiency
and quality in large projects.

Long term effects of Devops on software maintenance – Examine how use of CI/CD
pipelines and Devops practices impact the long term maintainability and scalability of
software systems.

6.5 Contributions of this Study to the broader research theme -

This study makes several contributions to field of software development -

Theoretical Contribution – This study provides a comprehensive overview of

strategies employed by IT Companies to develop, test and deliver software. It adds to
the existing literature by identifying key practices and their impact on Project
outcomes.

Practical Contribution – This study offers practical insights and recommendations for
IT Companies to improve their software development process. The findings can help
IT Companies adopt best practices and enhance their project outcomes.

72
6.6 Final Thoughts

This thesis has demonstrated that a well-planned and executed strategy involving
hybrid methodologies, automated testing and Devops practices can lead to a
successful software delivery for large fortune global 100 clients. The
recommendations provided offer actionable insights that can be used by IT
Companies to improve their project outcomes especially when dealing with large
clients with complex client requirements and legacy systems.

By adopting these best practices and continuously refining their development and
testing processes, IT Companies can position themselves for greater success in this
highly competitive landscape of large scale software development.

This research has provided valuable insights into strategies employed by IT

Companies to develop test and deliver software to fortune global 100 clients. The
findings highlight the importance of adaptable methodologies, robust testing
practices, efficient delivery mechanisms and efficient client management. While
challenges remain, the recommendations provided offers a roadmap for IT
Companies as well as their large clients to enhance their collaborative efforts and
achieve greater success in the large-scale software projects.

As the technology landscape continuous to evolve, ongoing research and adaptation

of strategies will be important. The future of IT Project management for large
enterprises lies in the ability to balance innovation with reliability, speed with quality
and flexibility with governance. By embracing the insights from this study and
continuing to refine their approaches, IT Companies and their Large Fortune Global
100 Clients can position themselves for success in this increasing digital and
competitive marketplace.

In Conclusion, this research underscores the importance of adopting effective

software development strategies tailored to meet the unique needs of large fortune
global 100 clients. By focusing on agile methodologies, automation testing,
stakeholder engagement, quality assurance and risk management, IT Companies can
enhance their capabilities to deliver high quality software solutions. The insights
gained from this study not only contributes to existing body of knowledge but also
provides practical guidance for IT Companies aiming to excel in this competitive
landscape.

73
 References

1. Books -

Pressman, R.S., 2019. Software Engineering: A Practitioner’s Approach. 9th ed. New
York: McGraw-Hill.

Sommerville, I., 2016. Software Engineering. 10th ed. Boston: Pearson.

2. Journal Articles:

Ahmad, I., Borman, R.I., Fakhrurozi, J. and Caksana, G.G., 2020. Software
development dengan Extreme Programming (XP) pada aplikasi deteksi kemiripan
judul skripsi berbasis Android. Jurnal Inovtek Polbeng Seri Informatika, 5(2), pp.297-
307.
Alami, A., Krancher, O. and Paasivaara, M., 2022. The journey to technical excellence
in agile software development. Information and Software Technology, 150, p.106959.
Alazzawi, A. and Rahmatullah, B., 2023. A comprehensive review of software
development life cycle methodologies: Pros, cons, and future directions. Iraqi Journal
For Computer Science and Mathematics, 4(4), pp.173-190.
Al-Saqqa, S., Sawalha, S. and AbdelNabi, H., 2020. Agile software development:
Methodologies and trends. International Journal of Interactive Mobile Technologies,
14(11).
Alyahya, S., 2020. Crowdsourced software testing: A systematic literature review.
Information and Software Technology, 127, p.106363.
Arvanitou, E.M., Ampatzoglou, A., Chatzigeorgiou, A. and Carver, J.C., 2021. Software
engineering practices for scientific software development: A systematic mapping
study. Journal of Systems and Software, 172, p.110848.
Barraood, S.O., Mohd, H. and Baharom, F., 2021. A comparison study of software
testing activities in agile methods. In Knowledge Management International
Conference (KMICe) (Vol. 2021). Kedah, Malaysia: University Utara Malaysia.
Beecham, S., Clear, T., Lal, R. and Noll, J., 2021. Do scaling agile frameworks address
global software development risks? An empirical study. Journal of Systems and
Software, 171, p.110823.
Bergenti, F., Caire, G., Monica, S. and Poggi, A., 2020. The first twenty years of agent-
based software development with JADE. Autonomous Agents and Multi-Agent
Systems, 34, pp.1-19.
74
Bernsmed, K., Cruzes, D.S., Jaatun, M.G. and Iovan, M., 2022. Adopting threat
modelling in agile software development projects. Journal of Systems and Software,
183, p.111090.
Bianchi, M., Marzi, G. and Guerini, M., 2020. Agile, Stage-Gate and their combination:
Exploring how they relate to performance in software development. Journal of
business research, 110, pp.538-553.
Bjarnason, E., Gislason Bern, B. and Svedberg, L., 2022. Inter-team communication in
large-scale co-located software engineering: a case study. Empirical Software
Engineering, 27(2), p.36.
Bugayenko, Y., Bakare, A., Cheverda, A., Farina, M., Kruglov, A., Plaksin, Y., Pedrycz, W.
and Succi, G., 2023. Prioritizing tasks in software development: A systematic
literature review. Plos one, 18(4), p.e0283838.
Chiang, H.Y. and Lin, B.M., 2020. A decision model for human resource allocation in
project management of software development. IEEE Access, 8, pp.38073-38081.
Christanto, H.J. and Singgalen, Y.A., 2023. Analysis and design of student guidance
information system through software development life cycle (sdlc) and waterfall
model. Journal of Information Systems and Informatics, 5(1), pp.259-270.
Dąbrowski, J., Letier, E., Perini, A. and Susi, A., 2022. Analysing app reviews for
software engineering: a systematic literature review. Empirical Software Engineering,
27(2), p.43.
Daun, M., Brings, J., Obe, P.A. and Stenkova, V., 2021. Reliability of self-rated
experience and confidence as predictors for students’ performance in software
engineering: Results from multiple controlled experiments on model comprehension
with graduate and undergraduate students. Empirical Software Engineering, 26(4),
p.80.
Decan, A., Mens, T., Mazrae, P.R. and Golzadeh, M., 2022, October. On the use of
github actions in software development repositories. In 2022 IEEE International
Conference on Software Maintenance and Evolution (ICSME) (pp. 235-245). IEEE.
De Silva, D. and Alahakoon, D., 2022. An artificial intelligence life cycle: From
conception to production. Patterns, 3(6).
Doyle, M., Gloster, A., O'Toole, C., Mangan, J., Murphy, D., Dunwoody, R., Emam, M.,
Erkal, J., Flanaghan, J., Fontanesi, G. and Okosun, F., 2020. Flight software
development for the EIRSAT-1 mission. arXiv preprint arXiv:2008.09074.

75
Dudhat, A. and Abbasi, M.A., 2021. Discussion of Agile Software Development
Methodology and its Relevance to Software Engineering. ADI Journal on Recent
Innovation, 3(1), pp.105-114.
Edison, H., Wang, X. and Conboy, K., 2021. Comparing methods for large-scale agile
software development: A systematic literature review. IEEE Transactions on Software
Engineering, 48(8), pp.2709-2731.
ElBatanony, A. and Succi, G., 2021, October. Towards the no-code era: a vision and
plan for the future of software development. In Proceedings of the 1st ACM SIGPLAN
International Workshop on Beyond Code: No Code (pp. 29-35).
El Hafi, L., Garcia Ricardez, G.A., von Drigalski, F., Inoue, Y., Yamamoto, M. and
Yamamoto, T., 2022. Software development environment for collaborative research
workflow in robotic system integration. Advanced Robotics, 36(11), pp.533-547.
Faruk, M.J.H., Subramanian, S., Shahriar, H., Valero, M., Li, X. and Tasnim, M., 2022,
May. Software engineering process and methodology in blockchain-oriented software
development: A systematic study. In 2022 IEEE/ACIS 20th International Conference on
Software Engineering Research, Management and Applications (SERA) (pp. 120-127).
IEEE.
Fitriyanto, G.A., Suarna, N. and Nurdiawan, O., 2023. Sistem Informasi Surat Masuk
Dan Surat Keluar Pada Kantor Balai Besar Wilayah Sungai Menggunakan Metode
Sistem Development Life Cycle. Jurnal Informatika dan Teknologi Informasi, 2(2),
pp.215-219.
Frluckaj, H., Dabbish, L., Widder, D.G., Qiu, H.S. and Herbsleb, J.D., 2022. Gender and
participation in open source software development. Proceedings of the ACM on
Human-Computer Interaction, 6(CSCW2), pp.1-31.
Garousi, V., Rainer, A., Lauvås Jr, P. and Arcuri, A., 2020. Software-testing education: A
systematic literature mapping. Journal of Systems and Software, 165, p.110570.
Goyal, R. and Mistry, P., 2020. Standard Process for Establishment of ECU
Virtualization as Integral Part of Automotive Software Development Life-Cycle (No.
2020-01-5007). SAE Technical Paper.
Gupta, V., Fernandez-Crehuet, J.M. and Hanne, T., 2020. Freelancers in the software
development process: A systematic mapping study. Processes, 8(10), p.1215.
Habib, M., Maryam, H. and Pathik, B.B., 2014. Research methodology-contemporary
practices: Guidelines for academic researchers. Cambridge Scholars Publishing.
Hasanah, N. and Indriawan, M.N., 2021, March. Rancangan Aplikasi Batam Travel
Menggunakan Metode Software Development Life Cycle (SDLC). In CoMBInES-

76
Conference on Management, Business, Innovation, Education and Social Sciences
(Vol. 1, No. 1, pp. 925-938).
Holgeid, K.K., Jørgensen, M., Sjøberg, D.I. and Krogstie, J., 2021. Benefits
management in software development: A systematic review of empirical studies. IET
Software, 15(1), pp.1-24.
Hutchinson, B., Smart, A., Hanna, A., Denton, E., Greer, C., Kjartansson, O., Barnes, P.
and Mitchell, M., 2021, March. Towards accountability for machine learning datasets:
Practices from software engineering and infrastructure. In Proceedings of the 2021
ACM Conference on Fairness, Accountability, and Transparency (pp. 560-575).
Islam, G. and Storer, T., 2020. A case study of agile software development for safety-
Critical systems projects. Reliability Engineering & System Safety, 200, p.106954.
Kovari, A. and Katona, J., 2023. Effect of software development course on
programming self-efficacy. Education and Information Technologies, 28(9), pp.10937-
10963.
Kuhrmann, M., Tell, P., Hebig, R., Klünder, J., Münch, J., Linssen, O., Pfahl, D., Felderer,
M., Prause, C.R., MacDonell, S.G. and Nakatumba-Nabende, J., 2021. What makes
agile software development agile?. IEEE transactions on software engineering, 48(9),
pp.3523-3539.
Kyeremeh, K., 2021. Overview of system development life cycle models. Journal of
Management and Science, 11(1), pp.12-22.
Marek, K., Wińska, E. and Dąbrowski, W., 2021, January. The state of agile software
development teams during the covid-19 pandemic. In International Conference on
Lean and Agile Software Development (pp. 24-39). Cham: Springer International
Publishing.
Moe, N.B., Šmite, D., Paasivaara, M. and Lassenius, C., 2021. Finding the sweet spot
for organizational control and team autonomy in large-scale agile software
development. Empirical Software Engineering, 26(5), p.101.
Morita, H. and Ahmed, W., 2024. Evolutionary Algorithms in Software Development
Lifecycle Models: an Analytical Perspective (No. 12890). EasyChair.
Moyo, S. and Mnkandla, E., 2020. A novel lightweight solo software development
methodology with optimum security practices. IEEE Access, 8, pp.33735-33747.
Olszewska, J.I., Houghtaling, M., Goncalves, P.J., Fabiano, N., Haidegger, T., Carbonera,
J.L., Patterson, W.R., Ragavan, S.V., Fiorini, S.R. and Prestes, E., 2020. Robotic standard
development life cycle in action. Journal of Intelligent & Robotic Systems, 98, pp.119-
131.

77
Persson, J.S., Bruun, A., Lárusdóttir, M.K. and Nielsen, P.A., 2022. Agile software
development and UX design: A case study of integration by mutual adjustment.
Information and Software Technology, 152, p.107059.
Qian, C., Cong, X., Yang, C., Chen, W., Su, Y., Xu, J., Liu, Z. and Sun, M., 2023.
Communicative agents for software development. arXiv preprint arXiv:2307.07924, 6.
Rahmaniar, W., 2024. Chatgpt for software development: Opportunities and
challenges. IT Professional, 26(3), pp.80-86.
Rahy, S. and Bass, J.M., 2022. Managing non‐functional requirements in agile
software development. IET software, 16(1), pp.60-72.
Rasheed, Z., Waseem, M., Kemell, K.K., Xiaofeng, W., Duc, A.N., Systä, K. and
Abrahamsson, P., 2023. Autonomous agents in software development: A vision paper.
arXiv preprint arXiv:2311.18440.
Sandeep, R.C., Sánchez-Gordón, M., Colomo-Palacios, R. and Kristiansen, M., 2022,
January. Effort estimation in agile software development: a exploratory study of
practitioners’ perspective. In International Conference on Lean and Agile Software
Development (pp. 136-149). Cham: Springer International Publishing.
Sarpiri, M.N. and Gandomani, T.J., 2021. A case study of using the hybrid model of
scrum and six sigma in software development. International Journal of Electrical &
Computer Engineering (2088-8708), 11(6).
Shameem, M., Nadeem, M. and Zamani, A.T., 2023. Genetic algorithm based
probabilistic model for agile project success in global software development. Applied
Soft Computing, 135, p.109998.
Shastri, Y., Hoda, R. and Amor, R., 2021. The role of the project manager in agile
software development projects. Journal of Systems and Software, 173, p.110871.
Shi, W., Moses, H., Yu, Q., Malachowsky, S. and Krutz, D.E., 2023. All: Supporting
experiential accessibility education and inclusive software development. ACM
Transactions on Software Engineering and Methodology, 33(2), pp.1-30.
Shrikanth, N.C., Majumder, S. and Menzies, T., 2021, May. Early life cycle software
defect prediction. why? how?. In 2021 IEEE/ACM 43rd International Conference on
Software Engineering (ICSE) (pp. 448-459). IEEE.
Siddique, S., Naveed, M., Ali, A., Keshta, I., Satti, M.I., Irshad, A., Alomari, Z., Edo, O.C.
and Diekola, O.A., 2023. An effective framework to improve the managerial activities
in global software development. Nonlinear Engineering, 12(1), p.20220312.
Smart, J.F. and Molak, J., 2023. BDD in Action: Behavior-driven development for the
whole software lifecycle. Simon and Schuster.

78
Snyder, H., 2019. Literature review as a research methodology: An overview and
guidelines. Journal of business research, 104, pp.333-339.
Soares, E., Sizilio, G., Santos, J., Da Costa, D.A. and Kulesza, U., 2022. The effects of
continuous integration on software development: a systematic literature review.
Empirical Software Engineering, 27(3), p.78.
Sreekanth, N., Rama Devi, J., Shukla, K.A., Mohanty, D.K., Srinivas, A., Rao, G.N., Alam,
A. and Gupta, A., 2023. Evaluation of estimation in software development using deep
learning-modified neural network. Applied Nanoscience, 13(3), pp.2405-2417.
Strode, D., Dingsøyr, T. and Lindsjorn, Y., 2022. A teamwork effectiveness model for
agile software development. Empirical Software Engineering, 27(2), p.56.
Tam, C., da Costa Moura, E.J., Oliveira, T. and Varajão, J., 2020. The factors influencing
the success of on-going agile software development projects. International Journal of
Project Management, 38(3), pp.165-176.
Van Hai, V., Nhung, H.L.T.K., Prokopova, Z., Silhavy, R. and Silhavy, P., 2022. Toward
improving the efficiency of software development effort estimation via clustering
analysis. IEEE Access, 10, pp.83249-83264.
Venkatesh, V., Thong, J.Y., Chan, F.K., Hoehle, H. and Spohrer, K., 2020. How agile
software development methods reduce work exhaustion: Insights on role perceptions
and organizational skills. Information Systems Journal, 30(4), pp.733-761.
Vishnyakov, A., Kuts, D., Logunova, V., Parygina, D., Kobrin, E., Savidov, G. and
Fedotov, A., 2022, December. Sydr-Fuzz: Continuous hybrid fuzzing and dynamic
analysis for security development lifecycle. In 2022 Ivannikov Ispras Open Conference
(ISPRAS) (pp. 111-123). IEEE.
Weder, B., Barzen, J., Leymann, F. and Vietz, D., 2022. Quantum software
development lifecycle. In Quantum Software Engineering (pp. 61-83). Cham: Springer
International Publishing.
William, P., Kumar, P., Chhabra, G.S. and Vengatesan, K., 2021, November. Task
allocation in distributed agile software development using machine learning
approach. In 2021 International conference on disruptive technologies for multi-
disciplinary research and applications (CENTCON) (Vol. 1, pp. 168-172). IEEE.
Zahedi, M.H., Kashanaki, A.R. and Farahani, E., 2023. Risk management framework in
Agile software development methodology. International Journal of Electrical &
Computer Engineering (2088-8708), 13(4).

79
3. Conference Papers:

Agile Alliance. (2023). Agile Manifesto. Retrieved from https://agilemanifesto.org/

Albrecht, A.J., 2018. ‘Automated Testing and Its Impact on Software Quality,’ in:
Proceedings of the International Conference on Software Engineering. Florence, Italy:
ACM, pp. 182-191.

Poppendieck, M. and Poppendieck, T., 2016. ‘Lean Software Development: An Agile

Toolkit,’ in: Proceedings of the 2006 Agile Conference. Washington, DC: IEEE, pp. 37-
44.

4. Reports:

Forrester, 2019. The State of Agile Testing: 2019 Trends and Insights. Cambridge:
Forrester Research.

Gartner, 2020. Market Guide for DevOps Platforms. Stamford: Gartner Research.

5. Websites:

Agile Alliance, 2023. ‘What is Agile?’ [online] Available at:

https://www.agilealliance.org/agile101/

Atlassian, 2024. ‘The Ultimate Guide to DevOps.’ [online] Available at:

https://www.atlassian.com/devops

Gartner. (2023). DevOps Trends 2023. Retrieved from

https://www.atlassian.com/gartner/magic-quadrant-devops

6. Standards and Guidelines:

IEEE, 2017. IEEE Std 829-2008: IEEE Standard for Software and System Test
Documentation. New York: IEEE.

ISO, 2018. ISO/IEC 12207:2017: Systems and Software Engineering – Software Life
Cycle Processes. Geneva: International Organization for Standardization.

80
7. Technical Magazines:
McKinsey & Company, 2021. ‘The Next Generation of Software Testing: Trends and
Technologies.’ McKinsey Quarterly. [online] Available at:
https://www.mckinsey.com/business-functions/mckinsey-digital/our-insights/the-
next-generation-of-software-testing [Accessed 5 September 2024].

TechCrunch, 2020. ‘DevOps Tools and Trends in 2020.’ TechCrunch. [online] Available
at: https://techcrunch.com/2020/12/15/devops-tools-trends/ [Accessed 5
September 2024].

81
 Appendix –

Questionnaire Survey Form used to Collect Data -

General Information -

Name:

Position:

Company:

Q1 - Experience in the IT industry:

Less than 1 year
1-3 years
4-6 years
7-10 years
More than 10 years
Company Overview -
Q2 - What is the name of your IT company?
(Open-ended text field)
Q3 - What is the size of your IT company?
( ) Small (1-50 employees)
( ) Medium (51-250 employees)
( ) Large (250+ employees)
Q4 - How many Fortune Global 100 clients does your company serve?
1-5
6-10
11-20
More than 20
Strategy Development -

82
Q5 - What key factors do you consider when developing strategies for software
development for large clients? (Select all that apply)
Client requirements
Market trends
Technology advancements
Budget constraints
Timeline
Regulatory compliance
Other: _________
Software Development -
Q6 - What software development methodologies does your company employ for
large clients? (Select all that apply)
Agile
Waterfall
DevOps
Scrum
Kanban
Lean
Hybrid
Other: _________
Q7 - How do you determine which methodology to use for a specific project?
Based on client preference
Based on project requirements
Based on team expertise
Based on industry best practices
Other: _________
Testing Strategies -
Q8 - What are the key components of your testing strategy for large-scale software
projects? (Select all that apply)

83
Unit testing
Integration testing
System testing
Acceptance testing
Performance testing
Security testing
Automated testing
Manual testing
Other: _________
Q9 - What tools and technologies do you use for software testing? (Select all that
apply)
Selenium
JUnit
TestNG
LoadRunner
QTP/UFT
Appium
JIRA
Other: _________
Delivery and Deployment -
Q10 - What are the main challenges you face during the software delivery phase?
(Select all that apply)
Meeting deadlines
Coordinating with client teams
Managing dependencies
Ensuring quality
Handling last-minute changes
Other: _________

84
Q11 - What strategies do you use to ensure a smooth transition from development
to production?
Detailed deployment plans
Rollback procedures
Pilot releases
Training and support for client teams
Other: _________

Project Management -
Q12 - How do you manage project timelines and ensure timely delivery of software
projects?
Agile sprints
Gantt charts
Milestone tracking
Regular progress meetings
Other: _________

85