2022 IEEE 3rd Global Conference for Advancement in Technology (GCAT)
Bangalore, India. Oct 7-9, 2022
Scaled Agile Framework Implementation in
Organizations’, its Shortcomings and an AI Based
Solution to Track Team’s Performance
Upasana Ameta
Computer Science Engineering Computer Science Engineering
Geetanjali Institute of technical Studies Geetanjali Institute of technical Studies
Udaipur, India
ametaupasana@gmail.com mayank999_udaipur@yahoo.com
Abstract—The beginning of the 21st century was the
Software Enlargement Period, where software development
methods were designed to create and deliver software to
market under limited resources, time, and budget. The
traditional Software Development Life Cycle (SDLC) created
2022 IEEE 3rd Global Conference for Advancement in Technology (GCAT) | 978-1-6654-6855-8/22/$31.00 ©2022 IEEE | DOI: 10.1109/GCAT55367.2022.9971968
models like Waterfall Model, RAD model, etc. But this
approach required extensive documentation, lacked customer
involvement, and could not develop responsive software. Agile
Software Development Methodology was created in 2001,
which was flexible enough to adapt to changing requirements
at later stages and encouraged better customer involvement.
Scaled Agile Framework (SAFe) based on Agile Methodology
follows repetition and increment approach to develop reliable,
high quality, responsive and timely delivering software. This
paper involves the description of Agile methodology and SAFe,
problems in SAFe, and its solution by creating a machine
learning model.
Keywords—agile methodology, sprint, agile release train,
story points, release
I. INTRODUCTION
In today’s era, software and information technology have
become a large part of people’s lives. With newly emerging
technologies and changing business markets, enterprises are
bound to develop high-quality, quick-delivering, responsive
software. Software development method like Waterfall
Model was created to organize the software development
process efficiently [7]. However, this traditional approach
possessed a lot of documentation, lacked customer
involvement, and could not develop responsive software [5].
Once the requirements were finalized, they could not be
changed at later stages.
Agile methodology was developed that allowed
developers to inculcate requirement changes at later
development phases according to user demands. It increased
customer involvement, constantly delivered working
software, and welcomed late changing requirements [1].
Several frameworks were created to apply Agile
methodology to develop large-scale projects like Scaled
Agile Framework (SAFe), Disciplined Agile Delivery
(DAD), and Large Scale Scrum (LeSS). SAFe provides
structured guidance about roles, responsibilities, planning,
and management of the development process. It encourages
alignment, coordination, and cooperation between multiple
agile teams [7].
This framework has a rigorous planning process, and
even after that, there are times when dedicated features are
not completed within a given deadline. It may happen due to
insufficient time, dependencies, unknown risks, etc. A
978-1-6654-6855-8/22/$31.00 ©2022 IEEE
Authorized licensed use limited to: Universitas Indonesia. Downloaded on October 25,2023 at 17:07:37 UTC from IEEE Xplore. Restrictions apply.
Mayank Patel Ajay Kumar Sharma
Computer Science Engineering
Geetanjali Institute of technical Studies
Udaipur, India Udaipur, India
profsharmaak@gmail.com
machine learning model can be developed to predict the
probability of feature completion in the given timeline at an
early stage of the development process.
II. AGILE SOFTWARE DEVELOPMENT
Agile Software Development is a short-term
methodology based on the principle of agility, i.e., flexibly
responding to changes and adapting them in an uncertain
environment [1]. Companies can rapidly deliver reliable and
cost-friendly software using this development process.
The Agile method overcomes ‘rigid to adapt changes’
problem of traditional approaches. It allows to include
changes in technology or customer requirements at later
stages of software development. It breaks the project and
develops the software in small iterations, following the
iterative and incremental approach [2]. Agile practices
improved coordination between teams, project planning,
software responsiveness, delivery time, and success rate [5].
Lately, Agile Frameworks like Scrum, Kanban, XP, etc.,
have been scaled to support the development of large
projects for big enterprises. It was challenging to introduce
Agile at large scales, so several frameworks were developed,
namely Large Scale Scrum (LeSS), Disciplined Agile
Delivery (DAD), Scaled Agile Framework (SAFe), etc.
SAFe is the most popularly employed framework by
organizations to build high quality software and compete in
the growing market.
III. SCALED AGILE FRAMEWORK (SAFE)
The Scaled Agile Framework is a template used to extend
agile practices for software development on a larger scale by
creating a systematic roadmap for the process. It promotes
alignment to enhance coordination and cooperation between
multiple agile teams distributed globally. SAFe uses
workflow patterns that help large organizations to build
complex projects efficiently [4].
This framework follows the concept of lean product
development and applies systematic thinking to overcome
challenges faced during development.
SAFe is a customizable and sustainable framework,
suitable for a small organization with less than 100 people
and a large enterprise with more than a thousand people as
well [1]. Scaled Agile Framework uses Scrum, Extreme
Programming (XP), Kanban, etc., agile practices for software
development.
1
A. Scaled Agile Framework Values
1) Alignment: Multiple teams work concurrently on a
single project to achieve a common goal. Teams must be
aligned to understand common business states and goals and
work together to achieve them.
2) Built-in-Quality: Quality assurance methods are
applied to each iteration module for validating product
quality to improve customer satisfaction and reduce delays.
3) Transparency: SAFe promotes transparency between
team members, project managers, and customers to create an
open and trustworthy environment [8].
4) Program Execution: This framework focuses on
delivering working software continuously at regular
intervals rather than creating extensive documentation.
B. Scaled Agile Framework Principles
x Take an economic view
x Apply systems thinking
x Assume variability; preserve options
x Build incrementally with fast, integrated learning
cycles
x Base milestones on objective evaluation of working
systems
x Visualize and limit work in progress (WIP), reduce
batch sizes, and manage queue lengths
x Apply cadence, synchronize with cross-domain
planning
x Unlock the intrinsic motivation of knowledge
workers
x Decentralize decision-making
x Organize around value
IV. SCALED AGILE FRAMEWORK LEVELS
There are four main levels in the Scaled Agile
Framework-
A. Program and Team Level
These are the lowest levels of SAFe. The Team level
comprises agile teams with 5-12 members, and the Program
level combines several Agile Release Trains.
1) Agile Release Train (ART): ART is a collection of
self-organized, cross-functional agile teams. SAFe suggests
that there should be 50-125 people in an ART. It aggregates
agile teams to acquire the desired goal in each iteration,
called Program Increment.
2) Program Increment (PI): An iteration of process
execution in ART is called Program Increment. Each
increment lasts 8 to 12 weeks and has several iterations
called Sprints [1]. Each increment has several events like
planning, developing, and validating a complete system
increment.
3) Roles in ART: There are several important roles in an
ART:
a) Product Owner: The Product Owner is responsible
for communication between the product manager and
2
Authorized licensed use limited to: Universitas Indonesia. Downloaded on October 25,2023 at 17:07:37 UTC from IEEE Xplore. Restrictions apply.
stakeholders. PO is responsible for maintaining and
prioritizing the tasks in a product backlog [2]. A Product
Backlog is a list of actual customer requirements in the
project. The items in the product backlog are called features,
which are further divided into tasks called user stories.
b) Scrum Master: Scrum Master coaches the team,
maintains coordination between them, solves issues faced by
team members, and ensures that teams follow the roadmap
[6].
c) Dev Team: Dev team comprises professionals like
coders and testers who are responsible for planning,
executing, testing, and performing quality assurance
activities for the user stories.
Some other roles in ART:
a) Release Train Engineer (RTE): RTE leads all the
ARTs and facilitates large-scale meetings for multiple agile
teams in ART. RTE is responsible for the coordinating and
removing barriers across a large number of teams in ART
[4].
b) Product Management: For large projects, the
product backlog is maintained by Product Management.
They communicate with the customer, understand their
requirements, convert them into user stories, prioritize these
stories and assign them to teams in ART.
c) DevOps: The main purpose of DevOps is to create a
deployment pipeline, facilitate automation and integration,
and optimize the value stream for continuous delivery [2].
There are some more roles in ART like System
Architect Engineer, System Team, Shared Services, etc.
B. Portfolio Level
This level has the highest involvement in SAFe. It
defines the entire strategy of an organization, decides the
budget, allots funds, and synchronizes the governance
activities [1]. Strategy is described using Strategic Themes,
which link the portfolio level with different business
strategies.
The Program Portfolio Management (PPM) links the
portfolio to the organization, develops portfolio roadmap
and vision, and minimizes the cost [6].
C. Value Stream Level
Value Stream is an optional level in Scaled Agile
Framework developed for large independent enterprises that
build complex software and have many ARTs.
Synchronization between ARTs and suppliers happens at
this level. Planning meetings and Solution Demo Meetings
are organized at this level [8].
V. SAFE WORKFLOW
The Scaled Agile Framework follows several steps to
accomplish software development:
A. Program Increment (PI) Event
PI Planning is an event to regulate the ART teams to
acquire a common goal. It is a 2-days event where all team
members of ART participate and plan the development
process [1].
1) Day-1: Business leaders illustrate the requirements and
market needs, followed by the presentation of the
architectural view. Then the teams prepare a draft plan and 5) Inspect and Adapt (I&A): Inspect & Adapt Event can
present it to the business owner and management, who then be seen as an escalated retrospective in which all team
review it and provide feedback [4]. members and stakeholders of ART are present. It comprises
three parts:
Now, the team plans for an iteration using a visual board
called the Program Board. Teams mark features that will be a) PI System Demo: It is a more formal activity of
executed in the next sprint. Features are further broken into about an hour where all the features developed by ART
independent user stories. The size of user stories is during the PI are presented to a comparatively broader
estimated as a story point, and then they are prioritized by audience.
the PO according to the customer requirement and team b) Quantitative and Qualitative Measurement: Agile
capacity [5]. The agile team members also determine the teams review qualitative and quantitative metrics and record
risks and dependencies. All these steps are repeated for each data patterns. RTE collects this information and analyses the
sprint. possible problems [6].
2) Day-2: The Program Manager highlights the changes in c) Retrospective and Problem Solving Workshop: A
scope and resources. Teams update the plan according to the small retrospective is organized to discuss further issues,
provided feedback, define risks and dependencies and and then RTE facilitates Problem Solving Workshop to
finalize the plan. Finally, teams present the final features, tackle these issues.
dependencies, and milestones on the Program Board.
B. Iteration Planning and Development
An iteration may last up to two weeks, where teams
execute the designated features according to the plan.
1) Sprint Planning: A Sprint Planning Meeting is
organized by Scrum Master, where teams discuss the
purpose of user stories and check off the user stories that are
ready for implementation. User stories are assigned to team
members, and the complexity of user stories is determined
using story points [4]. Team members also discuss their
holiday plans to keep the holiday track and avoid delays.
2) Product Backlog Preparation and Refinement: The
Product Owner communicates with the customers, Fig. 1 SAFe Workflow
understands their requirements, converts requirements into
VI. PROBLEM STATEMENT AND PURPOSE
features, and places them into the product backlog [5].
A Backlog Refinement process is carried out by the SAFe is a better framework than other development
teams where they filter the user stories which are ready for strategies as it follows an iteration and increment approach.
execution in the next iteration. The user stories having the It is a convenient methodology in today’s world, where
highest priority from the Product Backlog are placed into technology, business, and the market are constantly
Sprint Backlog for the upcoming iteration. User stories are changing. SAFe welcomes late changing requirements of
refined based on story points, the number of team members, customers and incorporates these changes flexibly in the
and allotted time [6]. When multiple teams in ART perform project [6].
this practice, several risks, challenges, and dependencies are However, applying SAFe for developing complex
encountered at the early stages. projects in large enterprises can be challenging. Sometimes,
3) Daily Stand-Up: A Stand-Up meeting of 15 minutes teams cannot deliver solutions on the given deadline, even
is daily organized by the Scrum Master during the entire after going through such a rigorous planning process.
sprint. Team members discuss the tasks they completed
yesterday, tasks they will do today, and the challenges they
are encountering. Scrum Master reviews the status of the
project and the work and progress of individual team
members to increase transparency [3].
4) Sprint Review and Retrospective: A working model
of the final product is displayed to the PO and customer in
Sprint Review Meeting called the System Demo [2].
Customers review the prototype, check progress and give
feedback about changes to be incorporated into the final
product. This preserve teams from heading in the wrong
direction [3].
Fig. 2 Problem Scenario
A Retrospective meeting is held at the end of an
iteration, where all project members discuss problems Several challenges may occur during the development
encountered, things that went well in this sprint, and actions process:
to be taken for future improvements.
1) Insufficient Time: The timeline has to be drawn very
carefully, as extra time is needed to incorporate the

3
Authorized licensed use limited to: Universitas Indonesia. Downloaded on October 25,2023 at 17:07:37 UTC from IEEE Xplore. Restrictions apply.
continuously changing requirements of the customers. An
inadequate amount of time may cause the inability of teams
to stick to the estimated timeline and poor product quality.
2) Unresolved Dependencies: Multiple ARTs are cross-
functionally dependent on data and information. There could
be some unresolved dependencies between data points [2].
If one team in ART misses the deadline, it eventually
hampers the work of other agile teams and may lead to
project failure.
3) Pandemic: During such unprecedented times like
Covid-19, on-time product delivery is the biggest concern of
enterprises and customers.
4) Other: There may be other factors like lack of
teamwork, over commitment, team members leaving the
project, lack of team motivation, and disappointed
stakeholders [4].
Even after spending 8-10 days per year in the rigorous
planning process for Sprints and PI, teams are not able to
complete the designated features from the Product Backlog.
It may result in missed deadlines, loss of money and
reputation of the enterprise, and unsatisfied customers.
Organizations can overcome this challenge if there exists
a mechanism to predict the on-time delivery of solutions
beforehand. It could help teams to understand the timeline
and increase team size and working hours if needed to
complete the work on time.
There could be a proposed solution to this problem:
One possible solution to this problem could be building
such a model using a machine learning algorithm that will
use past experiences and data of agile teams to predict the
on-time delivery of value to customers.
VII. MACHINE LEARNING
Machine Learning is a branch of Artificial
Intelligence (AI) associated with the study and development
of algorithms for certain data predictions. Machines carry
out learning work, and algorithms enhance their behavior
automatically using experiences and constantly exploring
new information [12].
Machine Learning algorithms build models by taking
sample inputs and making predictions or decisions without
pursuing any static program instructions. These algorithms
can be used for applications like medicine, speech
recognition, email filtering, etc.
A. Types Of Machine Learning Techniques
1) Supervised Learning: This learning builds a
mathematical model using both input and output data sets.
The input data set is broken into training and testing data
sets [11]. Some Supervised Machine Learning algorithms
are Decision Tree, Linear regression, Logistic Regression,
Support Vector Machine, etc. This algorithm can be used in
face verification, recommendation systems, etc.
2) Unsupervised Learning: This algorithm only takes
the input data set, and the output set is not given to it.
Unsupervised learning uses input sets to find patterns in data
by grouping and clustering data points. Some Unsupervised
Machine Learning algorithms are K-Means Clustering, K-
Nearest Neighbor, Hierarchical Clustering, etc. [12]. This
algorithm can be used in data visualization, image
segmentation, etc.
4
Authorized licensed use limited to: Universitas Indonesia. Downloaded on October 25,2023 at 17:07:37 UTC from IEEE Xplore. Restrictions apply.
3) Semi-Supervised learning: This algorithm is a
combination of supervised and unsupervised learning as it
works on both labeled and unlabeled data. Since the labeled
data is less than the data to be predicted, this algorithm falls
between learning with supervision and without supervision
[13]. Some Semi-Supervised Machine Learning algorithms
are Generative Models, Self-Training, Transductive SVM,
etc. This algorithm can be used in image and speech
analysis, internet content classification, etc.
4) Reinforcement Learning: This algorithm makes the
decision and takes actions to maximize the number of
positive outcomes. There is no prior knowledge about the
action to be taken until a situation is given [11]. Some
Reinforcement Machine Learning algorithms are Q-
Learning, State Action Reward State (SARSA), Deep Q
Neural Network (DQN), etc. this algorithm can be used in
robotics, game theory, operation research, etc.
B. Supervised Machine Learning
This learning has a function that matches an input to an
output based on sample input-output pairs. The input data
set is partitioned into labelled training data set and a testing
data set to derive a function [11]. It is a task-driven
approach.
1) Types of Supervised Machine Learning: Following
are the types as described below:
a) Classification: Data is classified into different
categories which are illustrated on input data set based on
their specific features. E.g., Spam Filtering.
b) Regression: It fits the data and predicts other data
features based on some available features. E.g., Weather
Forecast, Market Trends etc.
Fig. 3 Types of Supervised Machine Learning
2) Examples of Supervised Machine Learning:
a) Face Detection: Differentiate human faces from
other objects.
b) Spam Detetction: Anomalies recognition for spam
detection.
c) Predictive Ananlysis: Predict certain results based
on output variable.
d) Customer Delivery: Prediction of customer
purchasing based on purchase history.
3) Workflow of Supervised Machine Learning

Fig. 4 Supervised Machine learning Workflow
4) Classification of Supervised Machine Learning
a) Decision Tree: Decision trees are used for
classification purposes. Each tree has a node that represents
an attribute and branches that represent values that the node
can assume [11].
b) Linear Regression: This algorithm makes
predictions by concluding relationships between one
dependent and many independent variables. For one
dependent and one independent variable, it is simple linear
regression. In the case of multiple independent variables, it
is multiple linear regression.
c) Naïve Bayes: This algorithm creates a Bayesian
Network based on the probability of occurring events [11].
It is used for text classification and clustering.
d) Support Vector Machine (SVM): This algorithm
minimizes classification error by drawing margins between
classes, and the distance between margin and classes is
maximum [12].
e) Logistic Regression: It is a probability-based
statistic model that can be used to solve both classification
and regression problems but is mostly used in classification
[13]. It calculates probabilities using mathematical logistic
functions.
VIII. IMPLEMENTATION
The proposed solution is implemented by building a
model using a logistic regression algorithm in Machine
Learning that will take features like User Story Name, Story
State, Story Points, Parent Feature Id, Team Id, Sprint Id,
release Id as input and then calculate the mean probability of
completion of features in the particular data set requested by
the user.
Following is the workflow of the implementation process:
5
Authorized licensed use limited to: Universitas Indonesia. Downloaded on October 25,2023 at 17:07:37 UTC from IEEE Xplore. Restrictions apply.
Fig. 5 Implementation Workflow
A. Read Data
The model is reading data from an excel sheet for now.
However, in real-world implementation, data could be
extracted from several databases like Mongo DB,
PostgreSQL, etc., requiring the data must be in tabular form.
The data set includes attributes such as User Story Name,
Story State, Status, Story Points, Parent Feature Id, Team Id,
Sprint Id, Release Id, and Date. Story State is the only
dependent feature or target variable whose value (Done/Not
Done) depends on the rest of the features.
B. Pipeline
Several steps are followed in the pipeline:
1) Data Cleaning: Data cleaning techniques are applied to
the raw data set to drop unnecessary columns, remove
NULL values, and index resetting [13].
2) Feature Engineering: Feature Engineering is done to
handle missing values, binning numerical values, extracting
parts of a date, etc. [11]. The model adds another column to
the data set for calculating the number of days between the
different Story States for each user story i.e., Open to
Implementing and Implementing to Done. Now, a new
feature is added to the data called Days.
3) Data Preparation: The purpose of this step is to drop
irrelevant attributes, duplicate checking, and get the
numerical form of data [12]. The categorical values of
features in the data set are converted into numerical form by
creating vector arrays. N-1 dimensional vector is created for
a feature having N distinct values. Now, this data is
converted into tabular form and is ready to be used in the
model.
The obtained data set is further bifurcated into training
data and testing data. The training data set contains data till
today’s date, and the testing data set contains future data.
80% of the training data set is used for training, and the
remaining 20% is for validation.
Stratification is done on the Story State feature to obtain
samples from data that best represent the data values.
4) Scaling: This model uses a Robust Scaler to convert the
actual distribution of data into normal distribution form.
Scaling is done on outliner data points for all independent
features. Training data fits into the scaler, and
transformation occurs on training validation and testing data
[11].
 Fig. 6 Robust Scaler Mathematical Formula

5) Modelling: The next step is the model initiation by
using a machine learning algorithm. Since the data is in
linearly separable form, logistic regression would be the
best approach to build the model. Logistic regression is best
suited for predicting the probability of a binary event
occurring. Since the Story State feature has two possible
outcomes, Done or Not Done, this can be said to be a binary
classification. Probability in Binary Logistic regression
ranges between 0 and 1. In the case of Story State, the
model assigns the Done state to be 1 and the Not Done state
0.
Logistic Function is called a sigmoid function, which will
take the story states and map the values between 0 and 1.
1 / (1 + e^-value) (1)
Where, e is base of natural logarithm
Logistic Regression equation is as follows:
y = e^(b0 + b1*x) / (1 + e^(b0 + b1*x)) (2)
Where, y=predicted output
b0=bias or intercept term
b1=coefficient for single input variable (x)
Logistic Regression Probability Prediction is as follows:
P(Story State=Done|Not Done) (3)
P(X) = P(Y=1|X) (4)
p(X) = e^(b0 + b1*X) / (1 + e^(b0 + b1*X)) (5)
Training data is fit into the model so that it learns and
improves itself over time.
6) Scores: The confusion matrix is used to calculate the
model performance for a set of testing data.
Accuracy, error, precision, recall, and f1_score is calculated;
to fully evaluate the model's effectiveness.
Accuracy=68.31, Error=31.69, Precision=63.57,
Recall=99.44 and f1_score=77.56
7) Pre Processing: Binary values are again mapped into
categorical values for Story State. Column added for storing
the number of days during feature engineering is dropped,
and the index is reset.
C. Prediction
Now, the model is ready to be accessed by users. User is
requested to enter Team id, Sprint Id, and Release Id for
which they want the probability. The model will calculate
the mean of all Parent Feature Ids of that particular data
piece, and the percentage probability of feature completion
is calculated and returned to the user.
Fig. 7 depicts the implementation model that can be used
to calculate the feature completion probability by user:
Fig. 7 Model Dashboard
Fig. 8 Model Prediction Result
IX. CONCLUSION AND FUTURE SCOPE
This machine learning model will predict the mean
percentage probability of whether the features of a particular
sprint in a release will be completed in the remaining time
or not. It will help teams to predict on-time product delivery
at an early stage; so that appropriate quality features can be
developed within the deadline. If organizations have this
sort of mechanism, teams can increase their velocity, size,
and working hours to finish the work on time.
The expected benefits of this model could be:
x Faster and Smarter Investment decision-making
(driven by machine learning model predictions)
x Maximize ROI (Return on Investment) with a
reduction in Project Delivery delays
x Increase team productivity, efficiency, and moral
x Supports Lean-Agile Mindset
x Cost Avoidance (cost assumptions and average time
period of delayed features)
In the future, this model can be integrated with software
like Rally and Jira used by companies employing the Scaled
Agile Framework. Data sets of teams, sprints, and releases
could be directly extracted from the Rally database and fed
into this model to predict the probability of completion of
given features in a particular sprint of a release.
REFERENCES
[1] Bc. Martin Kalenda, “Scaling Agile Software Development in Large
Organizations,” Brno, Spring, 2017.
[2] Lou Hinterberg, Fredrik Hoffman, “Exploring the Scaled Agile
Framework in a Virtual Team Setting,” Department of Informatics,
Lund School of Economics and Management, Lund University, 2018.

6
Authorized licensed use limited to: Universitas Indonesia. Downloaded on October 25,2023 at 17:07:37 UTC from IEEE Xplore. Restrictions apply.
[3] Nichamon Chantachaimongkol, Puangpetch Sincharoenpanich,
“Critical factors for implementing the Scrum Software Development
Methodology,” 2013.
[4] Priya Mishra, “Quality Deployment and Use of the Scaled Agile
Framework® - Managing teamwork and Software Quality in the
Banking Sector,” University of Tampere, 2018.
[5] Terryboy Simplicio Pereira, “Scrum and XP agile Practices used by
Project Managers contribution towards Software Project Success,”
Dublin Business School, 2019.
[6] Ameta, U., Patel, M., Sharma, A.K., “Scrum Framework Based on
Agile Methodology in Software Development and Management,” In:
Mathur, R., Gupta, C.P., Katewa, V., Jat, D.S., Yadav, N. (eds)
Emerging Trends in Data Driven Computing and Communications.
Studies in Autonomic, Data-driven and Industrial Computing,
Springer, Singapore, 2021.
[7] Sen, S., Patel, M., Sharma, A.K., “Software Development Life Cycle
Performance Analysis,” In: Mathur, R., Gupta, C.P., Katewa, V., Jat,
D.S., Yadav, N. (eds) Emerging Trends in Data Driven Computing
and Communications. Studies in Autonomic, Data-driven and
Industrial Computing. Springer, Singapore, 2021.
[8] Astha Singhal, Divya Gupta, “Scrum: An Agile Method,” IJETMAS,
2014.
[9] Peter Maher, “Weaving Agile Software Development Techniques into
a Traditional Computer Science Curriculum,” Proc. of 6th IEEE
7
Authorized licensed use limited to: Universitas Indonesia. Downloaded on October 25,2023 at 17:07:37 UTC from IEEE Xplore. Restrictions apply.
International Conference on Information Technology: New
Generation, 2009.
[10] Abheeshta Putta, Maria Paasivaara, and Casper Lassenius, “Benefits
and Challenges of Adopting the Scaled Agile Framework (SAFe):
Preliminary Results from a Multivocal Literature Review,” Aalto
University, Dept. of Computer Science, Espoo, Finland.
[11] Subhas C Misra, Uma Kumar, Vinod Kumar, Gerald Grant, “The
Organizational Changes Required and the Challenges Involved in
Adopting Agile Methodologies in Traditional Software Development
Organizations,” pp. 25-28, IEEE 2006.
[12] Ayon Dey, “Machine Learning Algorithms: A Review,” Ayon Dey /
(IJCSIT) International Journal of Computer Science and Information
Technologies, Vol. 7 (3), 2016.
[13] Özer ÇELİK, “A Research on Machine Learning Methods and Its
Applications,” Journal of Educational Technology and Online
Learning, September 2018.
[14] Iqbal H. Sarker, “Machine Learning: Algorithms, Real-World
Applications and Research Directions,” Springer, 2021.
[15] F. Khan, R. Kothari, M. Patel and N. Banoth, "Enhancing Non-
Fungible Tokens for the Evolution of Blockchain Technology," 2022
International Conference on Sustainable Computing and Data
Communication Systems (ICSCDS), 2022.