International Journal of Advanced Engineering, Management and

Science (IJAEMS)
Peer-Reviewed Journal
ISSN: 2454-1311 | Vol-10, Issue-7; Nov-Dec, 2024
Journal Home Page: https://ijaems.com/
DOI: https://dx.doi.org/10.22161/ijaems.107.16

Agile Development Methodology: Impact on Project Cost

and Time
Kashif Nawaz

[email protected]

Received: 14 Nov 2024; Received in revised form: 12 Dec 2024; Accepted: 19 Dec 2024; Available online: 27 Dec 2024

Abstract— The study investigates the impact of cost and time based on chosen development methodology
specifically agile software development. Agile software development is being used widely in maximum IT
companies. The sole purpose of this research is to study the impact of cost and time on software projects
which were developed using agile frameworks. The concept of the study uses quantitative descriptive
approach in which all respondents were given a survey of closed-ended questions to determine the impact of
cost and time on software projects using agile software development. The gathered information was
statistically analyzed using Statistical Package for the Social Sciences (SPSS) tool. Validity test was verified
by panel of experts, and reliability was checked by Cronbach’s alpha of internal consistency. A number of
analyses were performed on the data including normality testing, correlations and regression analysis.
Keywords— Agile Software Development, Impact of Cost, Time impact, Software development cost and
time impact.

I. INTRODUCTION in software development cycle, cost estimation must be

Agile software development has played an important role completed before the development cycle begins and
in almost every business area since the internet dawn. As deadlines or estimated completion time must be defined
the consumer's desire for immediacy and convenience before the development starts. Both factors help you
grows, companies are increasingly being asked to integrate correctly estimate each project and get the right price and
and develop their web-based services into their products. delivery time. The vibrant and dynamic nature of ASD
As a result, more resources are devoted to developing makes starting product development using agile
profitable software that meets consumer demands. methodologies a daunting task. Therefore, such a
Businesses want to maximize profits, so they need efficient development model requires accurate cost estimates to
resource allocation to keep costs down. This is achieved by match deadlines and estimates while maintaining the
adopting a process model that maximizes the conversion of highest software quality. This report provides a systematic
resources into quality goods. Agile software development impact of ASD's on project cost and time and helps an agile
is a new paradigm aimed at reducing risk and cost of user to understand the impact of these factors while
production. It is based on iterative development and choosing ASD for his project.
constant feedback from all stakeholders throughout the
development cycle. Moving from a typical waterfall II. BACKGROUND
process model to an agile process model reduces lead times
A process model is required to set the timeline for software
and increases team morale and productivity, reducing the
project deliverables and to ensure that all members of the
risks associated with large software programmer
development team, from managers to engineers to end
development. My research shows that companies across a
users, understand workflow expectations. Organizations
wide range of industries can benefit from incorporating
are beginning to realize the inherent limitations of the long-
some degree of agility into their development processes. In
used waterfall approach. A linear schedule for developing
recent years, the size and functionality of software have
requirements, implementing all features, and testing does
increased significantly. Cost and time are the major factors

www.ijaems.com Page | 128

Nawaz International Journal of Advanced Engineering, Management and Science, 10(7) -2024

not adapt well to changing customer requirements, putting technically difficult to accomplish in practice. And,
the project at significant risk. My research examines the without a doubt, there will be 'unknowns' with the project
impact of agile approaches on these risks and costs. Agile that will only be discovered when they occur. Furthermore,
uses an iterative development methodology, where whether you're a consumer, a developer, or a user, no two
features are developed in 2–4-week increments. As a people are same. We arrive with our own set of
result, all three major components of software information, experiences, values, expectations, risk
development are repeated during the development cycle. aversion, and adaptability. Senior engineers are
Small features are generated every few weeks and can be accustomed to writing high-quality software; but, building
easily modified, allowing for changing user requirements. amazing software solutions may be a much more
The result is lower risk than the waterfall approach and challenging task for all parties involved.
lower capital costs for software projects in agile This study aims to examine the impact of the cost and time
frameworks. Because this method is highly adaptable and on project delivery using agile process model.
responsive to continuous input, the product almost
PROBLEM STATEMENT
perfectly matches consumer expectations, resulting in
greater satisfaction and demand, as well as higher Agile methodology is being used extensively in various
profitability. However, only good implementation of agile organizations, but most of them face problem that how
approaches, or a good degree of agility, can lead to such long and how much cost it will take to deliver the project,
low software development costs. My research examines this study was aimed to explore the critical factors that
the pros and cons of using agile models to assess cost and impact project time and cost using the agile methodology.
time impacts on software projects. We begin by examining SCOPE OF WORK
the broad expert consensus on the limitations of both
In order to find out the factors that impact project time and
traditional and agile methodologies and the benefits of
cost using agile methodology. The study is limited to
agile process models. Then, we explore the main areas of
software projects and in terms of methodology it is limited
cost, quality and customer satisfaction that are impacted
to agile software development. We picked 30 samples from
when moving from a traditional method to an agile one.
IT industry of Islamabad and hence this study is covering
The term agile methodology refers to processes that are only companies working in Islamabad. Companies
developed and tested throughout the software development selected for research also work for international clients and
lifecycle of a project. In contrast to the waterfall approach, have more than 100 employees.
the agile style of software testing runs both the
SIGNIFICANCE OF THE STUDY
development and testing processes simultaneously. Agile
refers to a software development methodology that The critical factors identified in this research would be
emphasizes customer satisfaction, team productivity, helpful for the other companies working on agile
continuous planning, and incremental deliverables, rather methodology to keep them in mind while checking the
than aiming to deliver everything at once at the end. impact of cost and time using agile methodology for any
project. They will likely face less issues in execution of
Agile focuses on keeping processes lean and delivering a
project if they take care of the identified factors and
minimum viable product (MVP) that goes through multiple
conclusions drawn in this study.
iterations before being finalized. Feedback is continuously
captured and incorporated, resulting in a more dynamic RESEARCH OBJECTIVES
process where everyone is working towards a common Following are the main objectives this research:
goal.
• Evaluate if team capability has impact on cost
PURPOSE and time of project.
Determining how long and how much it will take to deliver • To evaluate customer feedback and requirements
a new software product is one of the most difficult tasks in gathering as a major impact on project cost and
software development. Should it be that challenging? The time.
answer is a little more complex and difficult. • To measure the impact of agile methodology on
Estimating software expenses is tough by nature, and cost.
humans are notoriously terrible at forecasting absolute • To measure the impact of agile methodology on
outcomes. There are no two projects alike; each has its own time.
set of goals and a unique set of parameters that define its RESEARCH QUESTIONS
existence. What appears to be a simple problem on the RQ1 Does team capability impact on cost and time of
surface is sometimes considerably more difficult or project?

www.ijaems.com Page | 129

Nawaz International Journal of Advanced Engineering, Management and Science, 10(7) -2024

RQ2 Are the customer feedback and requirements

gathering as a major impact on project cost and
time?
RQ3 Project deliverables with equal and defined
deadlines is more valuable to accomplish the
project on time and at defined cost?
RQ4 Execution of agile methodology has a direct
impact on project cost and time?
CLASSIFICATION

Table 1.1: Classification of Research

DATA ANALYSIS
DATA COLLECTION
Most data were received back from the respondents via
A few of the effective methods to gather data from a large online questionnaires as most IT staff prefer to use their
number of population and then apply different random screens and keep in the comfort of their work environment
sampling techniques upon it to extract out the desired so researcher also preferred this way to get the actual and
results. To test the research hypothesis and the research real results. Analytical study on collected data were
model, data is gathered through 3 IT companies of performed using the Statistical Package for the Social
Islamabad and 30 individuals participated in data Scientists (SPSS). A quantitative approach enables an
collection. Product owners, project managers, scrum investigator to investigate the relationship between
master, team leads and mangers with project costing variables. As there were a number of variables, both
knowledge and those who are responsible for project dependent and independent, in this study.
timelines have been consulted and their views has been
gathered through the questionnaires. This survey was
conducted on a voluntary basis with no undue pressure. All STEPS IN QUESTIONNAIRE DESIGN
the target respondents were given a standardized According to Dr. R. Venkitachalam’s “” and Linda Del
questionnaire as shown below: Greco, Walop W.Richard H McCarthy.
The steps in questionnaire design are as below:
Step 1: Background;
(a) Purpose and goal/objectives in Research
questions, hypothesis;
(b)Target audience / population sample.
Step 2: Conceptualization;
(a) Generate statements/ questions items i.e.
variables; Independent Variables (IV),
Dependent Variables (DV);

www.ijaems.com Page | 130

Nawaz International Journal of Advanced Engineering, Management and Science, 10(7) -2024

(b) Knowledge, attitude, perception, opinion, 1.1. LITERATURE REVIEW

facts, behavior - AGILE SOFTWARE DEVELOPMENT
Step 3: Format & Data Analysis; Agile refers to software development methodologies that
(a) Appropriate scales of measurement. emphasis incremental delivery, team communication,
(b) Data Analysis continuous planning, and continuous learning rather than
attempting to provide everything at once towards the end.
(c) Questionnaire format.
Agile promotes keeping processes lean and developing
Step 4: Validity; minimal viable products (MVPs) that go through several
(a) Panel of experts iterations before being complete. Feedback is continuously
collected and incorporated, resulting in a much more
(b) Readability tests
dynamic process in which everyone is working towards a
(c) IRB (Institutional Review Board) common objective.
(d) Field Test - SHORT HISTORY OF AGILE
(e) Revisions Readability Test. Agile software development is a methodology that was
Step 5: Reliability; first proposed in the early 1990s. It was created as an
alternative to the traditional waterfall model of software
(a) Pilot Test reliability.
development. In agile, software is developed in short
(b) Run Alpha, revisions, Re-Run Alpha. cycles, or sprints, and each sprint focuses on a specific set
(c) Instrument ready for mailing. of features. This allows for more flexibility and iteration
LIMITATIONS OF THE STUDY than the waterfall model. Agile has become increasingly
popular in recent years, and many organizations have
The study has also some limitations which are important to adopted it as their primary method of software
mention at this stage. First, the study focuses only on IT development.
market of Islamabad. Second, the study only emphasizes
on industry of Pakistan. Therefore, the dynamics of Agile
impact in global organizations are not the part of this study. - AGILE IS MINDSET
THEORETICAL FRAMEWORK Therefore, Agile is a mentality based on the ideals and
principles of the Agile Manifesto. These beliefs and
principles show how to produce and adapt to change, as
well as how to deal with uncertainty. The Agile Manifesto's
opening phrase encompasses the whole concept: "By doing
it and helping others do it, we are finding new ways of
building software." When faced with ambiguity, try
something you believe could work, obtain feedback, and
make adjustments as needed. When you're doing this, keep
the values and principles in mind. Allow your context to
inform the frameworks, methods, and approaches you
apply to engage with your team and provide value to your
Figure 1.1: Diagrammatic Depiction of Independent and
customers.
dependent Variables
- AGILE SOFTWARE DEVELOPMENT
MODEL
III. LITERATURE REVIEW Every project should be handled differently, according to
the Agile model, and current techniques should be
The purpose of this section is to examine the potential
adapted to best meet the project objectives. To provide
impacts that Agile software development can have on time
particular features for a release, tasks are split into time
and cost, with a specific focus on major contributions that
boxes (short time spans) in Agile.
are discussed in the available literature.
The process is iterative, with each iteration delivering a
functional software build. In terms of features, each build
is incremental; the final version contains all of the
features required by the customer.

www.ijaems.com Page | 131

Nawaz International Journal of Advanced Engineering, Management and Science, 10(7) -2024

Here illustration of the Agile Process Model: this method there are three categories, with their
responsibilities as follows:

Figure 2.1: Agile Software Development Model

Figure 2.2: Scrum Method

Because of its flexibility and adaptability, the Agile
thinking process began early in software development and
grew in popularity over time. Rational Unified Process a) Scrum Master: The Scrum Master is in charge of
(1994), Scrum (1995), Crystal Clear, Extreme organizing the team, sprint meetings, and removing
Programming (1996), Adaptive Software Development, roadblocks to progress.
Feature Driven Development, and Dynamic Systems b) Product Owner: The Product Owner is in charge of
Development Method (DSDM) are some of the most delivering functionality at each iteration and building
prominent agile techniques (1995). Following the the product backlog.
publication of the Agile Manifesto in 2001, these are now
referred to as Agile Methodologies. c) Scrum Meeting: A scrum meeting is a short, daily
meeting where team members discuss what they have
- AGILE SOFTWARE DEVELOPMENT accomplished since the last meeting and what they
PROCESS USE plan to do before the next one. This type of meeting
There are several common software development helps ensure that everyone is on the same page and that
methodologies, such as Scrum, Extreme Programming, tasks are being completed in a timely manner.
and Feature-Driven Development (FDD). The processes d) Product Backlog: It is an agile artifact that captures
involved in these methodologies are planning meetings, what needs to be delivered in order to achieve the
test-driven development, pair programming, stand up desired outcome. The product backlog items are
meetings and sprints. ordered by priority, with the most important items at
With Agile, people and the tasks their team does are the the top. As new items are added, they are placed in
focus of software development. An important aspect of the priority order based on their impact on the business.
Agile software development is the teams (self-organizing - PROCESS FLOW OF SCRUM
cross-functional) collaborating to finish a project. For
example, those development teams would create their own a) The team works on the set sprint backlog
plans to complete a task based on using best practices for b) The team checks for daily work
their context while they keep in mind their potential failure c) At the end of the sprint, the team provides product
and crisis management should they encounter an issue or functionality
problem. Those self-organizing teams should also work
d) The product backlog is a list where all
with other members who have different expertise as needs
information are included to achieve the final-
arise. Managers will still play a role in an agile
product
environment; however, managers aid in implementing
change within an agile project by creating a group that BENEFITS OF USING THE AGILE
possesses or acquires skill sets to tackle projects METHODOLOGY
successfully. Agile methodology is a set of practices and methods that
- SCRUM encourage collaboration and flexibility in the development
process. It has become popular in recent years because it
It's a technique used in agile software development. Scrum
helps to improve communication, speed up project
is named after the rugby strategy and believes it's more
completion, and reduce risks. Following are some of the
beneficial to work in small teams than large ones. Within
benefits of using agile methodology in your project.

www.ijaems.com Page | 132

Nawaz International Journal of Advanced Engineering, Management and Science, 10(7) -2024

ON TIME DELIVERY to respond quickly to changes in the marketplace and

Organizations that adopt agile methodology achieve a provide better service to their customers.
number of benefits, including on-time delivery. The Organizations that use the agile methodology often find
traditional waterfall development process often results in that they are able to improve their customer satisfaction
projects taking longer than necessary to complete. This is ratings. This is because agile methods help organizations
because the traditional process involves a long and detailed to become more responsive to customer needs, and this
planning phase followed by a long and detailed responsiveness can lead to improved satisfaction levels. In
development phase. During the planning phase, developers addition, agile methods help Organizations reduce the
are required to compile a detailed list of features and specs, amount of time needed to deliver products or services,
which can be difficult to change once the project has which can also lead to increased customer satisfaction.
begun. This can also lead to delays in the development Overall, the agile methodology is a useful way for
phase, as developers need time to incorporate all the organizations to improve their customer satisfaction
proposed changes into the project. ratings.
Agile methodology, on the other hand, focuses on BETTER CONTROL
completing projects quickly and efficiently. This is done
Agile methods allow for better control over project
by breaking projects down into small, manageable pieces
deadlines and product quality. By working incrementally
and building them until they are completed. This approach
and continuously testing, agile techniques help developers
allows for more flexibility in project planning and
to find and fix errors early, saving time and money.
development, which leads to quicker completion times. In
Furthermore, agile methods promote collaboration among
addition, agile methods often result in improved quality
team members, which leads to a better understanding of the
because they allow for more rapid feedback and iteration
project and an increased ability to meet deadlines. With
between stakeholders.
everyone working together in an open environment, the
SUPERIOR QUALITY PRODUCT project can move more quickly and efficiently. Overall,
Agile methodology is more than just a software agile techniques offer many advantages for both the
development methodology. It's a way of life, one that developers and the organization as a whole - making it a
stresses collaboration and communication, focus on popular choice for projects of all types.
customer needs and constant learning. The benefits of IMPROVED PROJECT PREDICTABILITY
embracing agile are clear: superior quality products that are
The agile methodology has been shown to be an effective
delivered on time and on budget. With an agile process in
tool for improving project predictability. This allows for
place, communication between team members is key. This
better planning and communication, which in turn leads to
allows for seamless integration of new features and updates
a more efficient and successful project. One of the key
into the product, resulting in a better user experience and
benefits of using the agile methodology is that it helps to
less rework. An agile process allows for quicker
overcome the "waterfall model" mentality. The waterfall
development times, leading to a faster time to market. This
model is a process where a project is planned and executed
can be essential in the ever-competitive world of
in a sequential manner, with each step requiring prior
technology.
completion of the previous step. However, this model can
By implementing an agile process, you can reduce costs be inefficient because it can lead to delays in project
associated with developing software. The streamlined milestones.
workflow will help keep your team organized and
By using the agile methodology, projects are able to move
coordinated, allowing for more accurate estimates and
faster and more efficiently through the stages of
fewer missteps. An agile process leads to higher quality
development. This allows for a more accurate prediction of
products by encouraging teams to work quickly and
when certain tasks will be completed and ultimately leads
efficiently without compromising on quality. By
to a more accurate end product.
minimizing errors from the start, you can ensure that your
final product is of the highest caliber. REDUCED RISKS
CUSTOMER SATISFACTION Agile methodologies help to reduce the risks associated
with project delivery. This is because they emphasize
The agile methodology is a process that helps
communication and collaboration between team members,
organizations to be more responsive to customers and
which helps to eliminate misunderstandings and potential
improve their overall customer satisfaction. By using the
conflict. Another benefit of agile methodology is that it
agile methodology, organizations can increase their ability
allows teams to adapt quickly to changes in the

www.ijaems.com Page | 133

Nawaz International Journal of Advanced Engineering, Management and Science, 10(7) -2024

environment. This means that they are able to respond study the impact of agile software development on project
more effectively to unforeseen challenges and problems. cost and time. This research carryout detailed analysis of
Overall, agile methods provide a number of advantages factors impacting cost and time using agile software
that can help organizations achieve their goals faster and development approach.
with fewer risks.
INCREASED FLEXIBILITY
Agile methodology has been shown to lead to increased
flexibility. This is because agile encourages the use of
short, iterative cycles that allow for changes to be made
quickly and easily. As a result, projects are able to move
faster and achieve their objectives more quickly.
Furthermore, because agile is incremental, it is less risky
and allows for corrections along the way. This
methodology also leads to a better understanding of the
problem and results in better solutions.
CONTINUOUS IMPROVEMENT
Agile methodologies are designed to help organizations
achieve continuous improvement. According to the
National Institute of Standards and Technology, "Each Figure 3.1: Work flow diagram of how the research work
iteration of the agile methodology focuses on delivering was proceeded.
working software frequently, with a focus on customer
satisfaction." This approach encourages teams to
continuously assess their work and make necessary PHASE 2: ANALYZE THE ORGANIZATION AND
changes in order to improve the quality and efficiency of COLLECT DATA
their work.
Depending on the research that has been made during the
initial phase, to investigate the impact of software cost and
IV. RESEARCH METHODOLOGY time using agile software development, a research topic
- INTRODUCTION was devised in consultation with supervisor and teachers.
The finalized research topic is "Agile software
In this section, we will be discussing the methodology that development: impact on project cost and time".
we will be using to conduct our research. The variables and
their operational description/definitions, research tool PHASE 3: DOCUMENT FINDING
applied to examine those variables, hypothetical On the basis of finalized research topic " Agile software
relationship and its graphical portrayal are also briefly development: impact on project cost and time ", Firstly the
illustrated in the section. Moreover, the method for data main hub of the knowledge, similar research papers
collection and the software utilized for the analysis of the selected for literature review, Secondly, internet resources
collected data are also briefly explained. were searched which came up with relevant articles and
- RESEARCH METHODOLOGY PROCESS the key words of "Agile software development cost and
FLOW time", "Agile software development", "research
methodology", "data analysis" etc. were retrieved and read
The research work has been carried out in different phases thoroughly. Section number 2 includes review of almost
to make it systematic and in a sequence such that desired all relevant literature.
results could be achieved.
PHASE 4: PURPOSE AND DOCUMENT CHANGE
PHASE 1: DEFINE GOAL AND CONDUCT
LITERATURE REVIEW Problem statement that is highlighted in the Introduction
section at section 1.3 was planned, reviewed and finalized
Section one i.e. Introduction amplifies upon defining goal with the help of supervisor and IT sector Executives.
for the research conducted in this research. Section two i.e.
Literature Review explains in detail the main theme of the - PHASE 5: ANALYZE IMPACT AND
research and research idea giving detail background DOCUMENT RESULTS
information. The cardinal purpose of the research is to On the basis of the project’s research area, targeted entities
and the problem statement a questionnaire is developed in

www.ijaems.com Page | 134

Nawaz International Journal of Advanced Engineering, Management and Science, 10(7) -2024

context of impact of cost and time using agile methodology H1: Feedback and requirements are the critical factor that
in development of software. impact on agile software development in terms of project
- PHASE 6: SURVEY CONDUCTANCE AND time
DATA COLLECTION. Hypothesis 3
Source of Primary Data H1: Equal frequency of sprint/iterations deliveries impact
The population of this study includes employees of agile software development in terms of project completion
Information Sector employees specially mangers, team on time.
leads, product owners, technical executives and Hypothesis 4
supervisors and those mangers from whom tome H1: Execution of agile development methodology by
management shares and give opinion of project cost and management has major impact on project cost and time.
time. The sample size was found out to be 30 numbers from
the Information Technology sector of Islamabad. The
respondents were selected through simple random V. RESEARCH APPROACH
sampling method in which every element has the same Basic classification of Research approach has been
probability for being selected for the sample (Kothari, categorized into two groups: Quantitative and Qualitative.
1990). Thirty questionnaires were distributed in above The research approach used in this study is quantitative.
mentioned respondents. This method is used to establish and employ statistical
models, hypotheses and theory relating to phenomena.
This method basically analyzes cause and effect, test
In total 35 plus survey forms were sent by using sample
hypotheses and make inference. The data comprises of
size techniques and 30 forms were received considered for
numerals and statistics which is collected using validated
study. The Survey forms received were recorded and data
and structured data-collection tool/instruments. These
retrieved was analyzed and discussed according to
results of quantitative research can be generalized in a way
standard procedures.
that they are made, applicable to other scenarios and
- PHASE 7: DATA ANALYSIS AND context through statistical and mathematical modeling.
DISCUSSION Data was collected from respondents through a structured
This phase incorporates the data collected through survey questionnaire.
questionnaire and the results which are the outcome of this - RESEARCH TYPE
survey to yield the inference from test and further
Research type depends upon the goals of the study. The
hypothesis validation. Different types of analysis such as
study of grace used for this study is Descriptive research as
descriptive analysis, data normality testing, correlations
describe the significance of a situation, state, or existence
analysis and regression analyses is used to produce the
of a specific phenomenon. Relational Research Problem --
findings. The entire analysis was done using the software
suggests a relationship of some sort between two or more
SPSS.
variables to be investigated. Moreover, this is also co-
- PHASE 8: FINDINGS, CONCLUSIONS relational type of research as the researcher only measures
AND RECOMMENDATIONS the variables and their relationship.
After data analysis and discussions, findings, conclusions - RESEARCH TOOL
of the research and recommendations regarding future
Questionnaire has been used as a research tool/instrument
research work were drawn and incorporated in section five
to conduct this research. The questionnaire has been
of this research.
developed after extensive literature review of research
Following hypotheses were formulated for this research work related to impact of time and cost for software
study: development using agile techniques and informal
Hypothesis 1 interviews / interactions with relevant personnel. The
H1: Team capability is an important factor for a successful researcher has developed the questionnaire himself and the
agile software development project. It can have a positive questionnaire has been tested for validity and reliability
or negative effect on time and cost. tests.

Hypothesis 2 - STEPS IN QUESTIONNAIRE DESIGN:

The Questionnaire has been developed following the steps
described in Section number 2 and finally passed through

www.ijaems.com Page | 135

Nawaz International Journal of Advanced Engineering, Management and Science, 10(7) -2024

stages of validity and reliability by pilot project study - NORMALITY TESTING

based on 25 Nos. of sample questionnaires. Usually Normality tests are carried out in order to analyze
- VALIDITY OF QUESTIONNAIRE whether the data is normally distributed or otherwise.
DEVELOPED There are two normality tests which have been used for this
The validity and relevance of questionnaire developed has research. These are skewness and kurtosis.
been verified by experts with vast experience from IT a. Skewness
sector including regulatory bodies. Skewness defines whether the data is skewed towards right
- RELIABILITY or left. Skewness range is usually considered between -1
The reliability of the research questionnaire has been and +1. It can be seen from table 4-2 that all the variables
verified through pilot study based on the sample size of 25 used in the research have value of skewness falling within
Nos. respondents from sample population. The Cronbach’s the range which shows that the distribution of our data is
alpha test has been performed on each variable. approximately symmetric.
b. Kurtosis

VI. ANALYSIS AND DISCUSSION Kurtosis explains the relative sharpness and the height of
the distribution as compared to a normal distribution curve.
- INTRODUCTION
It is usually considered that the range of kurtosis should
To achieve the research aims data is gathered directly from remain between -3 and +3. It is quite clear from table 4-2
primary source so it does not contain much missing values that the value of kurtosis for all the variables used in this
or outliers as data is gathered from respondents directly and research falls within the range which shows that the data is
all information regarding to questionnaire are given to normally distributed.
them. The analysis has been performed using statistical
c. Histograms
package of social sciences (SPSS). The data is measured
on five point Likert scale while relationship among them is The Histograms of these variables are attached as shown
studied using correlation and linearity is discussed by below.
regression analysis.
- DESIGN SELECTED
In this study, design selected is questionnaire-based survey
research. The data set is gathered on five point Likert scale
from strongly disagree to strongly agree. Data reliability
and validity is checked using Cronbach alpha.
- POPULATION
To examine the results, the population of Islamabad and
Rawalpindi is considered as target population so sample is
fetched from that particular regions of Pakistan. The
population of this study includes team leads, project
managers, technical officers and scrum masters of
Information Technology organization.
- SAMPLING DESIGN AND SIZE
It is difficult to analyze complete population and fetch
information from each and every unit of population so a
representative sample would be required. Thus, a
representative sample of 81 respondents is obtained using
simple random sampling technique.
DATA COLLECTION METHOD
The list of respondents compiled from professional circles
and LinkedIn members with relevant roles. The
questionnaire was circulated through web links by
researcher.

www.ijaems.com Page | 136

Nawaz International Journal of Advanced Engineering, Management and Science, 10(7) -2024

further linear relationship exists among other variables as

well or not.

The scatter plot among OTD and MS also indicated no

specific linear relationship among them. Although there
appeared only block of four values which presents only that
specific values.
CORRELATION ANALYSIS
The scatter plot indicated not specifically linear
relationship among two pairs of variables now we would
discuss relationship among all four pairs and examine the
CRONBACH’S ALPHA VALUE
relationship is significant or not. The significance of
Table 4.1: Cronbach’s Alpha Value relationship is discussed using p values for each pair of
pearson relationship.
Table 4.2: Correlations Matrix (Pearson)

The data is examined for reliability using Cronbach alpha

for all the variables separately and for all of them combined
as well. Thus, data appeared reliable.
SCATTER PLOTS
Now, we would apply exploratory data analysis techniques
and examine the relationship among variables. So, the
simplest technique for examining relationship is scatter
plot.

*. Correlation is significant at the 0.05 level (2-tailed).

**. Correlation is significant at the 0.01 level (2-tailed).

The relationship among all variables is almost positive

except Team Productivity and Management style as their
relationship is negative. Although we observe p-values for
The scatter plot indicates not specifically linear
all relationships is small so it seems significant relationship
relationship among TP and CS although we would examine

www.ijaems.com Page | 137

Nawaz International Journal of Advanced Engineering, Management and Science, 10(7) -2024

among all pairs of variables that is also observed from Table 4.4: ANOVA
astaric * signs above all values in SPSS output. Further, we
observe the relationships are almost moderate as they are
nearly equal to 0.5 and the value of relationship considered
nearly equal to .5 is moderate relationship. While
relationship among customer satisfaction and on time
delivery is 0.76 which is largest among all relationships
and its strongest. Further, all variables have significant
relationship with dependent variable as well.
REGRESSION ANALYSIS
As, we observe significant relationship among all pairs of
variables using correlation analysis so further linear
relationship is discussed using regression analysis and
explored how much increase in one variable causes
increase or decrease in predictor variable. Here, project
cost and time is considered as dependent variable and
remaining variables act as independent variables.
Table 4.3: Model Summary

a. Predictors: (Constant), TP
b. Predictors: (Constant), TP, CS
c. Predictors: (Constant), TP, CS, OTD Table 4.5: Model Summary
d. Predictors: (Constant), TP, CS, OTD, MS
e. Dependent: PCnT
Among these regression equations the second model has
highest R square. So, we would say that maximum
variation is explained by this model so, team productivity
and customer satisfaction are explaining maximum
variations as compared to all independent variables.

a. Predictors: (Constant), TP
b. Predictors: (Constant), TP, CS
c. Predictors: (Constant), TP, CS, OTD
d. Predictors: (Constant), TP, CS, OTD, MS
e. Dependent: PCnT
The ANOVA table for all models are indicating
significance due to smallest p values which seems
goodness of fit for all models.

www.ijaems.com Page | 138

Nawaz International Journal of Advanced Engineering, Management and Science, 10(7) -2024

a. Dependent: PCnT VIII. FINDINGS, CONCLUSIONS,

As shown in Table 4-5 model summary, the highest R RECOMMENDATIONS
square appeared for second model while ANOVA also - Introduction
indicated its significance of model so it is considered to be The preceding section deals with introducing evidence and
the best model while detailed analysis indicated customer interpreting results in order to address the study's research
satisfaction and team productivity have positive significant questions. The emphasis of this section is the review of
impact on project cost and time variable. Further the model research-based results, study-derived recommendations,
equation would be written as; and conclusion. The section further presents the study's
Regression Equation weaknesses and strengths. The aim of the analysis was to
PCnT = 3.789 + 0.012 TP +0.805 CS examine the impact of cost and time on software
development using agile methods.
- HYPORESEARCH TESTING
- Findings and Conclusion
The research requires to analyze which of independent
variable is significantly impacting on project time and cost. It is important to mention here that success is measure by
So, t test is examined for all the coefficients and p values the customer’s satisfaction, on time delivery, team
determines their probability of rejection. productivity and management style with the final product
and that is possible only in adopting agile software
Table 4:6: t-values and the equivalent p-values
development techniques and these techniques can lead to
project cost and time saving, the agile software
development creates agility in our software business
sector. The study provides insight on how to adopt and
retain agile software development in the existing software
industry within Pakistan. It also provides ways in which
the companies can adopt and sustain healthy use of agile
software development.
The main objective of the research was to analyses the
impact of agile methodology on project cost and time. In
addition to it, the results in section 4 of the case study
provide with some useful information. Keeping in view the
The table indicated that all variables have significant selected independent variables positively influence as
impact on project time and cost separately due to largest t found to have major impact of team productivity (TP),
statistics and smallest p-values. customer satisfaction (CS), on time delivery (OTD) and
Management style (MS) on Project cost and time that are
major findings by using Agile software development
VII. DISCUSSION OF RESULTS methodologies in software industry. The independent
The analysis indicated that independent variables team variables designed by summing the information of sample
productivity (TP), management style (MS), customer questions are team productivity, customer satisfaction, on
satisfaction (CS) and on time delivery (OTD) all are time delivery and management style. The average showed
impacting significantly on project cost and time (PCnT). maximum worth for customer satisfaction therefore it
Further, significant relationship exists among all of them would say that there are largest percentage of contributors
due to high correlation. Also, regression analysis is who are satisfied with techniques. The scatter plot indicates
performed to examine the linearity of model and the model not specifically linear relationship among TP and CS and
including team productivity (TP) and customer satisfaction also indicated no specific linear relationship among OTD
(CS) are expressing more variations as compared to others. and MS. The relationship among all variables is almost
Thus, they have more impact among all independent positive except Team Productivity and Management style
variables. as their relationship is negative. Significant relationship
among all pairs of variables using correlation analysis.
regression analysis is performed to examine the linearity of
model and the model including team productivity and
customer satisfaction are expressing more variations as
compared to others and analysis indicated customer

www.ijaems.com Page | 139

Nawaz International Journal of Advanced Engineering, Management and Science, 10(7) -2024

satisfaction and team productivity have positive significant by adding uncertainty as mediator variable in team
impact on project cost and time variable. productivity can help out to extract more significant
Moreover, the findings of the study can be used to strength results.
and extend the existing models of Agile Software
development impact of project cost and time putting into REFERENCES
practice in software industry. Academically, the study
[1] Ahmed, A., Ahmad, S., Ehsan, N., Mirza, E., & Sarwar, S.
provides opportunity and avenue for research students who
Z. (2010, June). Agile software development: Impact on
want to conduct research in this field. In this way, the study productivity and quality. In 2010 IEEE International
creates awareness among young researchers about the Conference on Management of Innovation &
Agile Software development impact on project cost and Technology (pp. 287-291). IEEE.
time. Agile software development is providing more [2] Cohn, M., & Ford, D. (2003). Introducing an agile process
opportunities for the software industry as it is focusing to an organization [software
more on the customer satisfaction / feedback and on time development]. Computer, 36(6), 74-78.
delivery.by focusing features on the needs it will save the [3] Coram, M., & Bohner, S. (2005, April). The impact of agile
methods on software project management. In 12th IEEE
project time and cost. Agile software developing is
International Conference and Workshops on the
prevailing techniques for the software development, not
Engineering of Computer-Based Systems (ECBS'05) (pp.
only providing benefits the team productivity, customer 363-370). IEEE.
satisfaction/ Feedback, on time delivery and management [4] Fergis, K. (2012). The Impact of an Agile Methodology on
style but also maximizes the profit of the company by Software Development Costs.
providing good quality of work, delivering the projects on [5] Jain, P., Sharma, A., & Ahuja, L. (2018, August). The
the time and fulfil the customer satisfaction. They can impact of agile software development process on the quality
develop new Agile Software development techniques and of software product. In 2018 7th International Conference
models for all types of projects. on Reliability, Infocom Technologies and Optimization
(Trends and Future Directions)(ICRITO) (pp. 812-815).
Limitation and Contribution IEEE.
As there is no agreed-upon way to measure the cost and [6] Kula, E., Greuter, E., Van Deursen, A., & Georgios, G.
time of agile software development. As a result, it is (2021). Factors Affecting On-Time Delivery in Large-Scale
Agile Software Development. IEEE Transactions on
difficult to compare the cost and time of different agile
Software Engineering.
software development approaches. The research is limited
[7] Livermore, J. A. (2007, March). Factors that impact
by its means of data collection. The data for the study has implementing an agile software development methodology.
been gathered only one time so, it has a limited insight. If In Proceedings 2007 IEEE SoutheastCon (pp. 82-86). IEEE.
data might be collected more than one time it can yield [8] Melo, C. D. O., Cruzes, D. S., Kon, F., & Conradi, R. (2013).
much accurate results. Major portion of the data has been Interpretative case studies on agile team productivity and
gathered from cities of Rawalpindi and Islamabad. The management. Information and Software Technology, 55(2),
study is limited in ways that only covers the two cities of 412-427.
Pakistan not the overall markets of the country. [9] Nasehi, A. (2013). A quantitative study on critical success
factors in agile software development projects; case study IT
In the study, the respondents are all from Pakistan. If a company.
comparative study were to be done, it should be carried out [10] Tam, C., da Costa Moura, E. J., Oliveira, T., & Varajão, J.
in other countries. (2020). The factors influencing the success of on-going agile
software development projects. International Journal of
- Future Work
Project Management, 38(3), 165-176.
The past research statistics and experimental studies are [11] Ramírez-Mora, S. L., & Oktaba, H. (2017, October).
analyzed to fetch out the most relevant conclusions to this Productivity in agile software development: a systematic
study. A systematic experimentation and investigation mapping study. In 2017 5th international conference in
work was carried out to prove the results of the previous software engineering research and innovation (CONISOFT)
studies and to form the factual evidence of this research. (pp. 44-53). IEEE.
[12] Wafa, Rubab, Muhammad Qasim Khan, Fazal Malik,
Some major past experimentation has been consulted to
Akmalbek Bobomirzaevich Abdusalomov, Young Im Cho,
define the over-all idea of the underlying study.
and Roman Odarchenko. (2022). "The Impact of Agile
In this study we have chosen 4 independent variables team Methodology on Project Success, with a Moderating Role of
productivity (TP), customer satisfaction (CS), on time Person’s Job Fit in the IT Industry of Pakistan" Applied
delivery (OTD) and Management style (MS). This research Sciences 12, no. 21: 10698.
work can be extended by adding mediator variables. Like https://doi.org/10.3390/app122110698

www.ijaems.com Page | 140

Nawaz International Journal of Advanced Engineering, Management and Science, 10(7) -2024

[13] Ghimire, Dipendra, and Stuart Charters. (2022). "The

Impact of Agile Development Practices on Project
Outcomes" Software 1, no. 3: 265-275.
https://doi.org/10.3390/software1030012
[14] Shariq Aziz Butt, Tuncay Ercan, Muhammad Binsawad,
Paola-Patricia Ariza-Colpas, Jorge Diaz-Martinez, Gabriel
Piñeres-Espitia, Emiro De-La-Hoz-Franco, Marlon Alberto
Pineres Melo, Roberto Morales Ortega, Juan-David De-La-
Hoz-Hernández. (2023). Prediction based cost estimation
technique in agile development, Advances in Engineering
Software, Volume 175, 103329, ISSN 0965-9978,
https://doi.org/10.1016/j.advengsoft.2022.103329.
[15] Rahul, N. , Nouidui, T. , Ulaya, P. and Kiwia, D. (2023) The
Impact of Agile Methods on the Software Projects
Implementation and Management. American Journal of
Industrial and Business Management, 13, 183-194. doi:
10.4236/ajibm.2023.134013.
[16] Mishra, A., Alzoubi, Y.I. (2023). Structured software
development versus agile software development: a
comparative analysis. Int J Syst Assur Eng Manag 14, 1504–
1522. https://doi.org/10.1007/s13198-023-01958-5

www.ijaems.com Page | 141