Innovation Agile Methodology towards DevOps

International Research Journal of Engineering and Technology (IRJET) e-ISSN: 2395-0056
Volume: 09 Issue: 04 | Apr 2022 www.irjet.net p-ISSN: 2395-0072
© 2022, IRJET | Impact Factor value: 7.529 | ISO 9001:2008 Certified Journal | Page 2773
Innovation Agile Methodology towards DevOps
Poojan S Patel
Department of Computer engineering, Sardar Vallabhbhai Patel Institute of Technology (SVIT),
Vasad, INDIA.
---------------------------------------------------------------------***---------------------------------------------------------------------
Abstract - Interest in the DevOps concept, which involves
collaborating across technology and IT activities, has grown
rapidly in recent years among software engineers, users, and
experts. Given its growing value, DevOps is also associated
with agile and continuous software development delivery
methodologies. The analysis of DevOps focuses on the roots,
acceptance, integration, and priorities of agile, lean, and
continuous software deliverymethodologies. Thedevelopment
of agile software based on lean principles encouraged the
DevOps concept. Agile software development is required for
successful DevOps implementation. DevOps is the automation
of the entire software development and delivery process. As
digitization continues, corporations are turning toward
DevOps, and corporations are deploying DevOps.
Key Words: DevOps, Software Engineering, Agile
Methodology, Collaborating, Automation
1. INTRODUCTION
It's hard to distinguish between DevOps and Agile
approaches. This is also due to the fact that many marketers
employ broad definitions for these terms, reducing their
actual meaning. Furthermore, it is not always marketing
ambiguity that causes idea ignorance and confusion. It also
contributes to the misconception that DevOps and Agile are
more concerned with ideals than with practical actions. A
software project requiresthecompletionofactivitiesinorder
to create additional value. Project management's principal
task would be in the planning, design, implementation, and
monitoring of these tasks. In terms of software and product
design, the business environment has grown more quicklyin
recent years. Project planning, review, improvement
management, and quality control are just a few of the issues
that separate successful from unsuccessful initiatives. To
address these difficulties, agile approaches are widely
adopted and applied around the world. Agile and DevOps
techniques are improving methodologies, and as a result,
their application development is handled in short space of
time (sprints) and other involving team members are
changed. The purpose of this research will be onasystematic
study of DevOps and agile technique approaches.
2. AN AGILE METHODOLOGY
Software developers are clear of the drawbacks of massive
processes like the Waterfall technique, and they are looking
for a technique to simplify and make software modification
more flexible. They've decided to provide end-user feedback
more options to guarantee they're on the proper pathway. In
the 1990s, hundreds of new lightweight ideas for software
development were evolved, including the well-knownScrum
and Kanban approaches. The Agile Software Development
Protocol, issued in 2001, defined many of these ideas and
placed them within the context of agile software
development. Theagiletechniquealsochallengestheconcept
of a "completedproduct,"whichwastheWaterfallapproach's
primary objective. Agile also enables adaptive planning,
continuous improvement, early andcontinuousdelivery,and
continuous improvementtohelpdeveloperstoadjustquickly
and flexibly to changes in customer demand, software, and
other external factors. Agile underlines the value of iterative
and incremental software development. This implies that
with each new software update,thecustomercantryoutnew
features or enhance existing ones. Software design can be
broken down into smaller chunks called "user stories" using
agile methodology.
3. THE MODERN DEVOPS
Agile was a solution to waterfall methods' approaches,
whereas DevOps was not a response to Agile. Both concepts
are not the same, because companies have started to notice
synergies and increased performance and efficiency when
they are employed together. IT operations (ITOps) and
Development Operations (DevOps) are two significant

domains that are necessary for organizations in the modern
time. DevOps is in service of designing and delivering new
products to end clients, although ITOP is in charge of making
suresafety, compliance,andavailability.DevOpsgoeshandin
hand with adaptability, thorough analysis, and interaction
with the implementation of new software, much as ITOps
delivers stability and safety for all client needs via the
network. Multiple connections between these two aspects
emerged as a result of the organization's developments. The
focus of Agile Teams is on automation design, automated
testing, and Continuous Delivery. These tools, as well as
metrics and monitoring systems,configurationmanagement,
virtualization, and cloud computing, are regularly used by
DevOps teams,accordingtodata.Forsoftwareengineerswho
had been dissatisfied by the restrictions of a waterfall
technique, Agile appeared to be a completely new concept.
Agile isn't perfect. Missed deadlines, completed pieces that
are incompatible witheachotherduetosegregatedsprintsor
groups, and additional additions dividing old features – due
to a lack of collaboration with DevOps and ITOps – are all
common drawbacks of Agile planning.
In this circumstance, DevOps fills in the gaps. Because
developers must work together, DevOps is a communication
strategy that works both within and beyond departments.
DevOps communicates with ITOps on a daily basis to keep
testing environments safe and efficient, so it makes sense to
take the help of other departments, such as marketing and
customer support, when deploying new applications.
DevOps can be called an enhancement of Agile methodology
when both theories are applied to effective business
requirements.Agilefocuses oncross-functional teams,which
are typically made up of Designers, testers, and
programmers are all needed
4. DEVOPS VS AGILE
After understanding the backdrop and conversation
dimensions, it's timeto look at the parallels between DevOps
and agile approaches. DevOps is a combination of cultures,
techniques, and instrumentsthat splitssilosintoteams.Agile
methodology is a software development approach that
accelerates the response loop between clients and software
engineers. Although DevOps and agile approaches had such
similarities, they are not identical, and some argue that
DevOps is preferable to agile methodology. To clear up the
confusion, it's crucial to really go down to a nuts and bolts.
DevOps establishes the basic organization behavior and
environment from a technology standpoint. In this light, the
balanced relationship is recognized. Because of thecontrasts
in both development and production circumstances, well-
informed stake holders and phases will be meaningless if the
underlying facilities collapse. Global corporate structures,
concurrent design, sector - wide management, and adaptive
development, for example, can affect future technological
innovation.
The difference between the two is defined by what happens
following software development. Software is developed,
tested, and deployed in both DevOps and Agile. However,
after these three stages, pure agility appears to come to an
end. DevOps, on the other hand, involves continuous
operations. As a result, software development and
monitoring are ongoing. Individuals build, test, and deliver
software in an agile environment. Technology is business,
and software is business, and DevOps is all importantforthe
function of engineers in DevOps. Agile is more associated
with lean and resource efficiency, while DevOps is more
associated with cost savings, and phrases like agile accounts
for projects and a market - ready product (MVP) are key.
DevOps brings IT to the mix, but Agile focusses on software
development and deployment. Both are significant
approaches for software development.
5. CHALLENGES AND APPROACH
Agile and devops cultural revolutions shift organizational
culture from traditional approaches to agile and devops
practices. Our research has identified a list of forty distinct
barriers between the traditionalcultureandtheagile-devops
culture. These are the lack of an agile vision, complexity,
legacy systems and legacy software development process,
design of large software system, a time to market pressure,
planning and risk management, performance, software
system cost estimation, quality assurance and measurement
in product development, individual roles within the team,
strict organization structurewith highnumberofhierarchies
and multiple departments for different types of expertise. A
Table -1: Sample Table format

list of opportunitiestoovercomethesebarrierswascompiled
and presented as best practices that would guide
organizations through their cultural transition from
traditional body shop operations to enterprise agile-devops
operations.
If you are planning to apply agile and DevOps, you can feel
free to consider thehow:It is important to remember that
the agile approach is not everything, especially in the case of
a large company. It may be difficult to apply Agile: Consider
what the challengesare of applying agile mentality to certain
parts of your business. Ask yourself how many peoplewillbe
involved in transforming intoan agile companyoradoptinga
DevOps culture? Will it have an impact on your customers?
Also ask whether this processcanhelpwithinnovation.Some
companiesalso request feedback fromtheircustomersabout
what they thinkaboutimplementingthesechanges.Overall,if
you follow our guide and look at many aspects of your
business, you may discover that some benefits will appear in
different areas.
Agile software developmenthas been aroundsince2001,but
most organizations do not still adopt this methodology
because they are unabletoovercomethechallengesinvolved.
When a DevOps approach iscombined with agile'smanifesto
and its principles, it leads to continuous improvement and
service delivery. The agile method uses quick incremental
growth to quickly satisfy customers, thereby increasing
product value. This method is based on interactions,
customer collaboration, and responding to change. On the
other hand, DevOps culture helps in solving problems that
can build solutions for the customer's experience as well as
increase IT efficiency.
Sample paragraph Define abbreviations and acronyms the
first time they are used in the text, even after they have been
defined in the abstract. Abbreviations such as IEEE, SI, MKS,
CGS, sc, dc, and rms do not have to be defined. Do not use
abbreviations in the title or heads unless they are
unavoidable.
After the text edit has been completed, the paper is ready for
the template. Duplicate the template file by using the SaveAs
command, andusethenamingconventionprescribedbyyour
conference for the name of your paper. In this newly created
file, highlight all of the contents and import your prepared
text file. You are now ready to style your paper.
6. CONCLUSIONS
Agile practices and DevOps culture are different, albeit
related. Both help teams work faster and more efficiently,
where the quality of work is deliveredandthecustomersare
satisfied. When effectively practiced, work-life balance and
productivity are enhanced [20]. Agile uses incremental and
iterative methods to deliver high-qualitysoftwareina timely
manner. DevOps is a collaboration-building framework for
the Technology and Operations team that allows consumers
to quickly, automatically deploy code and add code to
production. It helps speed up the delivery of products and
services across the organization. Withtheseinsightsinmind,
it is clear that both Agile and DevOps strive for a more
efficient way to bring value to end-users— but from various
angles. It can be defined as aligning development As the use
of agile techniques has become pervasive in software
development, it has also helped to promote innovative
thinking beyond agile development and cross-functional
(DevOps) as well as end-to-end processes that impact both
software companies and consumers. Several organizations
have effectively adopted agile techniques to accelerate the
development of applications. Thedaysofwaterfall strategies
are long gone. Agile has started to slowly expand into other
downstream areas, such as IT and operations, in the
technology organization. Teams, simplified processes,
improved feedback loops, and driven IT departments
become much faster with an innovation that has a profound
impact on the entire organization. To build on this
performance, DevOps and Continuous License (CD) have
been built to support and improve agility, reactivity,andfast
times for marketing over the entire life cycle of software
delivery.
REFERENCES
[1] Dingsøyr, T., Nerur, S., Balijepally, V., and Moe, N., 2012,
"A decade of agile methodologies: Towards explaining
agile software development", Journal of Systems and
Software, 85(6), pp. 1213-1221.
[2] Laanti, M., Salo, O., and Abrahamsson, P., 2011, "Agile
methods rapidly replacing traditional methodsatNokia:
A survey of opinions on agile transformation",
Information and Software Technology, 53(3), pp. 276-
290
[3] Pedrycz, W., 2006, "Quantitative logic-basedframework
for agile methodologies", Journal of Systems
Architecture, 52(11), pp. 700-707.
[4] Forsgren, N., and Humble, J., 2015, "DevOps: Profiles in
ITSM Performance and Contributing Factors", SSRN
Electronic Journal.
[5] Dzamashvili Fogelström, N., Gorschek, T., Svahnberg, M.,
and Olsson, P., 2010, "The impact of agile principles on
market-driven software product development", Journal
of Software Maintenance and Evolution: Research and
Practice, 22(1), pp. 53- 80.
[6] Drury, M., Conboy, K., and Power, K., 2012, "Obstacles to
decision making in Agile software development teams",
Journal of Systems and Software, 85(6), pp. 1239- 1254.
[7] Forsgren, N., and Humble, J., 2015, "DevOps: Profiles in
ITSM Performance and Contributing Factors", SSRN
Electronic Journal.

[8] Amorim, A., Mira da Silva, M., Pereira, R., and Gonçalves,
M., 2020, "Using agile methodologies for adopting
COBIT", Information Systems, p. 101496.
[9] Kamel, M., Bediwi, I., and Al-Rashoud, M., 2010, "Planned
Methodologies vs. Agile Methodologies under the
Pressure of Dynamic Market", Journal of King Abdulaziz
University-Engineering Sciences, 21(1), pp. 19-35.
[10] Spinellis, D., 2016, "Being a DevOps Developer", IEEE
Software, 33(3), pp. 4-5.
[11] Saiedian, H., and Dale, R., 2000, "Requirements
engineering: making the connection between the
software developer and customer", Information and
Software Technology, 42(6), pp. 419- 428.
[12] Saeeda, H., Arif, F., Mehmood Minhas, N., and Humayun,
M., 2015, "Agile Scalability for Large Scale Projects:
Lessons Learned", Journal of Software, 10(7), pp. 893-
903.
[13] Wettinger, J., Breitenbücher, U., Falkenthal, M., and
Leymann, F., 2016, "Collaborative gathering and
continuous delivery of DevOps solutions through
repositories", Computer Science - Research and
Development, 32(3-4), pp. 281-290.
[14] Sidky, A., Arthur, J., and Bohner, S., 2007, "A disciplined
approach to adopting agile practices: the agile adoption
framework", Innovations in Systems and Software
Engineering, 3(3), pp. 203-216.
[15] Petersen, K., and Wohlin, C., 2009, "A comparison of
issues and advantages in agile and incremental
development between state of the art and an industrial
case", Journal of Systems and Software, 82(9), pp. 1479-
1490.
[16] Tan, C., and Teo, H., 2007, "Training future software
developers to acquire agile development skills",
Communications of the ACM, 50(12), p. 97.
[17] Ståhl, D., and Bosch, J., 2014, "Modeling continuous
integration practice differences in industry software
development", Journal of Systems and Software, 87, pp.
48-59.
[18] Turley, R. T., and Bieman, J. M.,1994), “Identifying
essential competencies of software engineers,” In ACM
Conference on computer science, 271–278.
[19] Ambler, S., and Lines, M., 2012, Disciplinedagiledelivery,
IBM Press, Upper Saddle River, N.J.
[20] Hill, P., 2011, Practical software project estimation,
McGraw-Hill, New York.
[21] uttermann, M., 1 ,“Dev psfordevelopers,”Ber eley,
CA: Apress.
[22] Gregory, J., and Crispin, L., 15, “More agile testing,
"Addison-Wesley, Upper Saddle River, N.J. [23] Novak,I.,
1 , “Beginning Windows 8 application development,”
Wiley, Indianapolis, IN.
[23] Rico, D., Sayani, H., Sone, S., & Safari, an O'Reilly Media
Company, 9, “The Business Value of Agile Software
Methods,” J. Ross Publishing.
[24] Conboy, K., Coyle, S., Wang, X., and Pikkarainen, M., 2011,
"People over Process: Key Challenges in Agile
Development", IEEE Software, 28(4), pp. 48-57.

Innovation Agile Methodology towards DevOps

More Related Content

Similar to Innovation Agile Methodology towards DevOps (20)

More from IRJET Journal (20)

Recently uploaded (20)

Innovation Agile Methodology towards DevOps