logo

Agile Methodologies and Agile Systems Discussion 2022

Combining Component Based Development Technique with Agile Software Development Model for better quality and reusability

11 Pages2500 Words8 Views
   

Added on  2022-10-10

About This Document

Topic is : Strategic use of Agile methodologies and agile systems Word count is 1500 words Report in 1500 words Refered articles should be peer reviewed articles..

Agile Methodologies and Agile Systems Discussion 2022

Combining Component Based Development Technique with Agile Software Development Model for better quality and reusability

   Added on 2022-10-10

ShareRelated Documents
Running head: AGILE METHODOLOGIES AND AGILE SYSTEMS 1
Agile Methodologies and Agile Systems
[Student name]
[Institution]
Author Note
Agile Methodologies and Agile Systems Discussion 2022_1
AGILE METHODOLOGIES AND AGILE SYSTEMS 2
Table of Contents
Introduction.................................................................................................................................................3
Topic Illustration.........................................................................................................................................3
Topic Influence............................................................................................................................................5
Critique of an IT Plan- for a Bank that used SCRUM Agile........................................................................6
IT Strategy Implications..............................................................................................................................8
IT Plan.........................................................................................................................................................9
Agile Methodologies and Agile Systems Discussion 2022_2
AGILE METHODOLOGIES AND AGILE SYSTEMS 3
Agile Methodologies and Agile Systems
Introduction
The past two decades has seen the discovery and use of new and innovative models for
software development, such as the waterfall model, stage wise models, the transform, spiral, and
evolutionary models. Among the most innovative models is the Agile software development
method ; it is currently used widely because it has features that enable rapid software
development and flexibility, as well as the ability to result in very high quality software. Agile
systems is relevant to IT management with respect to software development because it enables
better quality software development as it anticipates and incorporates evolving user
requirements. The evolution of solutions and requirements guarantees fast and high quality
software development through the collaborative efforts of cross functional self-organizing
development teams (Kansal & Gupta, 2012). As such, Agile is considered among the major
aspects that help in giving organizations a competitive advantage and is far superior to the linear
system of development, given IT management has become a critical component of organization
competitiveness (Idzikowski & Perechuda, 2018). This paper discusses the agile software
development method in the context of IT management in organizations and its implications and
value on IT strategies.
Topic Illustration
In the modern software development era, the use of traditional software development
methodologies such as the waterfall and in general, linear development methods give project
developers numerous problems and challenges not least of which is resource (cost, people, time)
wastage and the now familiar perception that most software projects, especially large scale ones
fail. Hence, software developers have adapted the new agile methodology where priority is given
Agile Methodologies and Agile Systems Discussion 2022_3
AGILE METHODOLOGIES AND AGILE SYSTEMS 4
to the customer and the use needs at all stages and involves iterative software development to
ensure fast software development with as few problems as possible (Kotaiah & Khalil, 2017). In
the software life-cycle, among the most difficult and challenging phases is the maintenance
phase. It is a tedious, complex, and resource consuming phase because of the changing IT
environment, such as changing operating environments and rapidly advancing technologies. A
lot of expenses are used in the maintenance phase because of the difficulties in achieving the
desired software quality, especially when traditional methods are used during development.
The waterfall model was used to overcome this problem; However, its sequential nature
resulted in drawbacks that include developing requirements upfront that invariably increases
costs when new requirements pop up during development and especially, maintenance. The
waterfall model resulted in 70% of software being unable to meet their objectives and
maintenance is particularly costly because moving to the previous stage, due to the sequential
nature of the model, is difficult (Tarwani & Chug, 2016). Introducing agile into non-agile
projects also have their challenges including lack of fit and failure to meet project objectives
(Bose & Thakur, 2013). Because of these challenges, the agile methodology was developed and
adopted, due to its many advantages because of its flexible nature, customer and user focus,
iterative nature and high quality end product (software). Methodologies of software development
are constantly evolving as new demands arise and technologies change. The modern business
environment has created organizations that constantly seek to adapt their policies, strategies, and
structures to meet changing needs and remain relevant and these organizations require
information systems that meet these needs.
Linear OO (object oriented) approaches have been used, but these have their challenges
and the result has been the development of agile methodologies such as XP and scrum. While
Agile Methodologies and Agile Systems Discussion 2022_4

End of preview

Want to access all the pages? Upload your documents or become a member.

Related Documents
Project Management Methodologies: Waterfall vs Agile
|6
|1067
|297

Agile PM vs Waterfall PM: A Comparative Study
|15
|712
|448

Project Management Methodologies: Waterfall vs Agile
|6
|970
|268

THE AGILE MANAGEMENT
|19
|4365
|27

Project Management Methodologies
|9
|1681
|92

Project Management Methodologies: A Comparison between Waterfall and Agile Methodology
|6
|1048
|211