Agile Methodology for TAMUT University Info System Report

This report focuses on the application of the Agile Methodology for the redesign of the university information system at TAMUT. The report highlights the suitability of Agile Methodology for managing processes like registration, library, and mail systems. It explains the reasons behind choosing Agile, emphasizing its benefits such as reduced risks, rapid development, improved quality, and enhanced customer experience. The report also discusses the irrelevance of other methodologies in this context. The Agile methodology is chosen because it allows for constant improvement and improvisation to maintain a top position within the market. Each individual within the development process plays a major role in the proper running of the information system. The report references several sources to support its arguments, providing a comprehensive analysis of Agile methodology's advantages in the context of university information system redesign.

Running head: UNIVERSITY INFORMATION SYSTEM
UNIVERSITY INFORMATION SYSTEM
Name of the Student:
Name of the University:
Author Note:

1UNIVERSITY INFORMATION SYSTEM
Table of Contents
Usage of Methodology...............................................................................................................2
Reasons for Methodology and irrelevance of other Methodologies..........................................2
References..................................................................................................................................5

2UNIVERSITY INFORMATION SYSTEM
Usage of Methodology
Aimed at the redesigning of TAMUT’s university information system for the
management of all the processes including the likes of registration, library, mail system and
blackboard the most suitable methodology which shall be proposed and followed is
commonly referred to as the Agile Methodology (Duka, 2013). Agile Methodology refers to
that specific type of process related to project management which generally is utilized within
the procedure of development related to software in which the demands as well as that of the
solutions are evolved with the help of collaboration related to teams which are self-
organizing and cross functional in respect to their customers.
The software industry refers to a high competitive market due to a reason that the
software is a domain, which is continuously on an upgrade. This refers to the fact that the
developers need a constant improvement and improvisation for their products to maintain the
top position within the market.
For the information system of the TAMUT University, there exists the application
running of a number of processes such as that of registration, library, blackboard, mail
system, and so on. For all of these processes to be monitored properly as well as the smooth
running of the application, each and every requirement of the university regarding all of the
processes included within the information system of the university, the best method to be
adopted is the Agile methodology (Kaleel & Harishankar, 2013). This methodology is chosen
for a reason that, every acting individual present within the development process plays a
major role relating to the fact that every single person within the university be it the
administration or the students has majorly equal roles to play in the proper running of the
information system.

3UNIVERSITY INFORMATION SYSTEM
Reasons for Methodology and irrelevance of other Methodologies
The Agile methodology is chosen for the redesigning of the information system for
the TAMUT University because of some of the reasons which are mentioned below,
i) Lesser Risks- With the changing population and the market within the university,
it might be proven to be a risky launch for the new development of the
information system (Matharu et al., 2015). At times, development with other
methodologies consume a lot more time, that by the time the information system
is properly implement into the system, the requirements which are met by the
present version become obsolete.
ii) Rapid development- when it comes to the development of project with the help of
the Agile model, the entire project is divided into smaller modules. These sub-
projects are dealt with an easier approach with the help of Agile development
method which does not take place when some other methodology is used and
hence is utilized in the development of the information system in this case.
iii) Improved quality- a lot different from the other methodologies in which the entire
system is put to test at the end of the entire development process, hence errors
related to the system come out all together which again consumes a lot of time to
fix and redevelop (Nishijima & Dos Santos, 2013). While in the Agile model, the
entire system is tested by parts in each of the phase which makes it easier for the
developer to fix the issues and present an error free system at the end.
iv) Improved customer experience- the agile model develops the information system
taking into consideration the recommendations from the users (Patwardhan,
2016). Hence, the information system which is developed is satisfying to the
customers since it consists of all the necessities which are placed by the customer
beforehand.

4UNIVERSITY INFORMATION SYSTEM
v) Less amount of development cost- since, within the Agile model, every single step
is analyzed and well planned, the calculation of the cost becomes easier and
therefore the chances of exceeding the budget is decreased (Špundak, 2014).
vi) Earlier Market Reach- each of the sub-project has a specific deadline to be
submitted by the developers for a better and faster delivery of the information
system to the university.

5UNIVERSITY INFORMATION SYSTEM
References
Duka, D. (2013, May). Adoption of agile methodology in software development. In 2013
36th International Convention on Information and Communication Technology,
Electronics and Microelectronics (MIPRO) (pp. 426-430). IEEE.
Kaleel, S. B., & Harishankar, S. (2013). Applying agile methodology in mobile software
engineering: Android application development and its challenges. Computer Science
Technical Reports, 1-11.
Matharu, G. S., Mishra, A., Singh, H., & Upadhyay, P. (2015). Empirical study of agile
software development methodologies: A comparative analysis. ACM SIGSOFT
Software Engineering Notes, 40(1), 1-6.
Nishijima, R. T., & Dos Santos, J. G. (2013). The challenge of implementing scrum agile
methodology in a traditional development environment. International Journal of
Computers & Technology, 5(2), 98-108.
Patwardhan, A., Kidd, J., Urena, T., & Rajgopalan, A. (2016). Embracing Agile methodology
during DevOps Developer Internship Program. arXiv preprint arXiv:1607.01893.
Špundak, M. (2014). Mixed agile/traditional project management methodology–reality or
illusion?. Procedia-Social and Behavioral Sciences, 119, 939-948.